[Imports] Import US County data
niceman at att.net
Thu Jan 6 22:28:38 GMT 2011
FYI - I have an import for Murray County, Oklahoma, US nearly ready - at step 11 and will probably happen within the next week -
Wiki page: http://wiki.openstreetmap.org/wiki/Oklahoma/Import/Murray
Peruse the proposed dataset in JOSM at:
**** Please Do not try to upload - the upload will fail in the current data state, and result in a messy possible partial upload ****
For a quick summary, here is an overlay of the 2 datasets, with some of the proposed data selected in red to stand out against the street in the aerial imagery. http://greenvilleopenmap.info/StreetCompare.jpg
The aerial imagery for this region is likely to be within 2M of actual, as confirmed by downloading GPS traces taken on I35. The county GIS data centerline accuracy appears to be very good and much better than the original TIGER data.
o Data is public domain, per the contact in the county's GIS department
o An analysis shows that the only edits in the county have been to the Interstate (Relation / Dual Carriageway / Align/ Exits / ref), the Turnpike, and US Highways (relations / refs).
1. The data itself will have no source= attribute, just as the dataset roads5.osm currently exists. The attribution will be on the changeset itself with the source= pointing to
the OSM wiki import page entry.
2. There is no attempt to maintain a link back to the original county GIS shapefile dataset elements - future edits will be smaller in scope, and will likely come from diff files, TIGER, or local mappers via aerial imagery or GPS traces.
3. The address data from the county's dataset will not be imported because I have no way to verify its accuracy level. It would probably be better than TIGER's anonymized address interpolations ranges, but would only be address ranges on a street, and may not correspond 100% to physical address locations.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Imports