[Imports] Designated Wilderness area import

[Apollinaris Schoell]

On Fri, Jul 2, 2010 at 11:01 AM, Erik G. Burrows <erik at erikburrows.com>wrote:

>
> These areas are made publicly available through several US government
> agencies, including the US Forest Service, Bureau of Land Management,
> National Park Service, etc. The "National Atlas" site makes all of the
> Wilderness Areas available for download as a single shapefile:
>
> http://www.nationalatlas.gov/mld/wildrnp.html
>
> (There is also a ton of other great information available for download at
> this site.)
>
> some data is very low resolution and shouldn't be imported if there is a
chance to get highres data from other sources


>
>
> I think there will need to be a substantial amount of manual work done to
> ensure no data duplication occurs, and some cleanup of enclosing boundary
> areas, so the process I'm planning on using is fairly manual:
>
> yes, this is a lot of manual work and can't be fully automated.


> 1. Convert the National Atlas shapefile into KML using ogr2ogr.*
>  *The intermediate step through KML format is necessary because gpsbabel
> below needs 3-D coordinates on input, but this shapefile is 2-D. The KML
> file allows for manual (perl script) addition of a zero-value
> z-coordinate.
>
> 2. Convert the KML file into OSM format using gpsbabel.
>
> 3. Use JOSM to add each area to the OSM database manually by copying areas
> from the shapefile-derived layer to the downloaded OSM layer for that
> region.
>
> Some metadata is lost in this process, such as the area state, state FIPS
> code, managing agency, unique ID and URL to wilderness.net. In order to
> restore this data, I plan to either create a patch for gpsbabel to tunnel
> this metadata through, or create a perl script to copy this data from the
> KML file to the OSM file.
>
>
I recommend shp2osm which can do all this in one shot.
there is a perl version, the Java version from Ian Dees and also a beta of
ogr2osm.
all can convert in one step and preserve the attributes.
I have used mainly the Java version because it has a flexible interface for
attribute translation.
ogr2osm is nice when you have touching areas and need to convert to advanced
multipolygons with relations.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20100702/9ca7ecd2/attachment.html>