To be thorough, I think we would have to break it up. For example, we list a Canal/Ditch (33600) as waterway=canal, but the OSM tag is only for use on ways, while the NHD applies it to areas. At the same time, the NHD point info gives dams as points, but the OSM waterway=dam is only for lines and areas.
Ian Dees wrote: > > > On Mon, Apr 20, 2009 at 10:07 AM, Theodore Book <tb...@libero.it > <mailto:tb...@libero.it>> wrote: > > The problem with the table, though, is that the NHD fcodes apply to > point, line, and area data, while the OSM tags might be specific to only > one or two of those types. That requires a little bit of flexibility in > actually preparing the scripts. > > > All 3 of the shp-to-osm convertors can handle applying different OSM > tags based on the type of geometry in the shapefile. > > Are you saying the we need to split up the FCode table on the Wiki page > based on feature type (polygon, line, point)? > > > ------------------------------------------------------------------------ > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-us _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
