I just wanted the opportunity to voice some thoughts I have been having over the last day or two about the doubles rule. Please let's try not to get into slagging the rules off or pointing to examples of inconsistencies - this is not the aim of this thread. It is just to discuss issues.
One aspect of my understanding of the NOA
_Double rule is that you can have a photo rejected if it looks very similar to a previous photo already accepted on to the database that you have taken yourself. I had a nice morning out at the weekend in some (all too rare) beautiful soft sunlight at Manchester, and I headed off to my favourite vantage point. After editing some of my favourites I realised that a few I had put in the queue looked uncomfortably similar to photos of those same planes that I have previously submitted and had accepted. Hence I have pulled them.
Of course, we all have different tastes and perspectives: for me the lighting of a photo is key. I would argue that, for all those examples, the photos I have had to pull from the queue for fear of a 'double' rejection were quite definitely superior to those that are already in the database - particularly in terms of clarity and the overall quality of the light. Far superior in fact, and of much more interest to viewers.
Now I recognise that you can't necessarily 'trade' new shots for old, and because part of the role of the database is 'historical', it would be unhelpful to lose shots already present. Seeing how things develop is interesting - be it locations; the state planes are in; editing quality etc etc. That didn't stop me wishing there was the facility to swap one of these new shots for one already present, as it is so much better. But for someone like me, who doesn't really travel around to many venues, but enjoys working to improve the quality and interest of my A.net 'portfolio', this rule is preventing me being able to put forward shots that otherwise I would be confident would be good additions.
There is, of course, a similar discussion that could be had about 'common' issues, as the database builds further.
I would very much like to see A.net retain its premier position for aviation photography. My concern is that there are occasions when the past - i.e. what is already on the database - might prevent otherwise excellent photos from getting the airing they deserve. The 'double' and 'common' rules seem to me to be the way this may happen.
This is not a criticism of these rules per se, but just an opportunity to consider how the database is going to develop in the future, and how these rules will affect the way things go. I would be very interested to hear what others think on this issue.
As a final point, I pulled the shots in question because they were taken from pretty much the same place and the plane was at pretty much the same location on the tarmac. However, it looked very different due, primarily, to the vastly different lighting conditions. I am assuming the double is relevant because of the orientation of the shot - but am I wrong? Could it be argued that, because the lighting is so different, even though the photos look very similar from the point of view of location/focal length etc, the lighting makes them potentially 'different'?
Apologies - wordy as ever, but I wanted to try to get my point over clearly. All the best.