On Tue, Mar 31, 2009 at 9:15 AM, Adam Schreiber <[email protected]> wrote:
> I made sure there weren't overlapping state borders as well. Without > checking, I think I tagged our southern border with Mexico at the > country level. I can't remember if I did the same for our northern > border. It's pretty sad that the county border import didn't line up > with the state borders. I suppose one could go in where they cared > and fix the bordering counties to share the state borders. > > A faster way of doing this might be if the person that did the county > borders saved their .osm files from that import, then the saved .osm > files from the state lines could be overlayed and fixes made. Okay, but is there a definitive list of where the corners of the US counties are located? We know the GeoBase data represents the best accuracy as to placement of the border. This data represents provincial borders. We can also tag it as a national border as well. If one were to simply chop the US county off where the current incorrect county border crosses the GeoBase boundary, or extends the county border to meet the GeoBase boundary, we're not increasing the accuracy of the information presented. All we would be doing is making it look pretty while yet again introducing errors to the map data. The IBC has a nice list of lat/long for each of the monuments that define the border. I have received written permission from the IBC to be able to use the monument data without breach of copyright for double checking the GeoBase borders. I'm fairly sure that the GeoBase data is using the IBC monument locations, and the IBC data is probably only going to be used for quality assurance checks, but I got permission from the IBC just to make sure the CC by SA license wouldn't be breached if I did make any changes. James VE6SRV _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
