our db is geolocation enbabled...I did not look deeply into his data but at first glance he is not geolo enabled as when I drilled into his data there were no lat/Lon's...mapping seems approximate and based on city.
Zipcodes aren't that big, compared to the coverage areas of most repeaters. I imagine that it's close enough.
I know several repeater owners that try to keep the lat/lon of their machines semi-private and often list a spot on the adjacent hill just for some ambiguity. Our coordination body does not disclose coordinates. My point being, keeping the finer-grained lat/lons reported of various repeaters is likely to be approximate :)
We have been working over the last couple of weeks to fix inconsistencies in the data. We have an algorithm worked out to fix the PL's. Our data is sourced from dozens of places....once Dan pointed out the inconsistencies with the PL's our new mode is to validate on import. We have to retroactively fix what's wrong though. Work in progress.
The ones I pointed out are still broken in the database, by the way. Are those going to get fixed?
Creating and maintaining RFinder and The Worldwide Repeater Directory is not a hobby.
Hmm, is this the name of the database itself? Maybe I should change what chirp calls it (from current RFinder)?
Thanks for the info!