Thanks!, I've been working in these issues (for a living) for a long time...
Your first mistake is to assume gps coordinate means bird location, but it is just phone location.
Not making that mistake at all...
The distance between a bird and a phone location can be variable, but certainly is not 0 (it can be 0 one in a million observations), and often can be on the hundreds of meters range. I don;t really see how your suggestion would improve anything... but I keep my eyes open just in case you write it.
Of course, in open habitats, the observer may be a long way away from the bird, in forest closer. But there are ways to correct for this. Information about exactly where the bird was recorded (yes I'm well aware that it's where the bird was recorded, not [exactly] where the bird was—that's obvious !) is still useful for several reasons:
- A checklist may cover many kms
- A checklist may cover many different habitat types
The most common case for the latter is probably changes in elevation. As we know, many species are altitude-restricted but you would not know this if all you have is the entire trip checklist. In contrast, it would be obvious if you knew exactly where the bird was recorded.
From personal experience, I would say that I tend to record certain species in more or less exactly the same part of my local park each time I see them. This isn't clear from my checklists...
To fully correct for differences in apparency etc would require a rigorous protocol, and probably extra measurements along the route like line of sight. Nonetheless, you can do a lot these days with remotely sensed data—e.g. you can tell something about how open the habitat was where the sighting was made and in this way estimate the likely maximum distance to the observer.
Your argument could serve well to diminish the utility of gls for bird conservation. Who en earth care on a bird location / migration path when there are errors on the 100s of Km?
Sorry I don't understand this at all.
I just want to remember to general public and readers that different needs mean different methods,
We agree. The point is that ebird throws away information which it could easily capture and which would be useful. Even with the corpus of ebird data as it stands, you would treat it differently depending on exactly what you're trying to estimate.