I live in North Eastern Utah and started updating the the map in my area, there are a lot of major updates of just the roads that will likely take a month or so to get through.
One thing I noticed is the complete absense of BIA Indian lands on OSM. This become a legal issue for users of OSM on their GPS due to access restrictions. If you are caught on the Tribal land you will be arrested unless you can prove map error. Not having a map or GPS will result in at least a hefty fine. With total absense of these boundries on OSM, it is completely unusable in this part of the country by hikers, mountain bikers, campers, hunters, etc.
NationalAtlas.gov has shape files for BIA administered lands across the entire United States. How can I go about getting these into OSM format?
Discussion
Comentari de bmispelon lo 29 d’agost 2009 a 20:02
Hi,
The first thing is to make sure that you are allowed to import such data. From a quick browsing, it looks like the data is public domain (http://nationalatlas.gov/policies.html#copyright ), so that should be ok.
You can probably find a lot of useful infos in the wiki: osm.wiki/Import
There you'll find other examples of import as well as general guidelines to follow when importing large sets of data.
For the technical aspect of things, I can't really help you but I'm pretty sure you'll find all the help you need eventually.
Comentari de Baloo Uriza lo 29 d’agost 2009 a 20:23
I wouldn't say completely useless unless nobody's worked the TIGER tracks over yet (ie, tracks are listed as residential roads lacking reference with the reference in the name instead, rather than as a possibly unnamed track with a ref=NFDXXXX). Your giveaway is the change in these tracks from ref=NFDXXXX to ref=BIAXXXX).