Hi, Can you give an example of a situation when you'd need to use multiple source fields for 1 osm tag?
Also, if your creating intersecting ways, double check to see that the nodes are infact connected. (shp-to-osm doesnt connect the ways. (thats why im not dealing with roads, and leaving it to the shp2osm script to handle) but it seems all other features are fine though. On 10/20/09, Dan Homerick <[email protected]> wrote: > On Mon, Oct 19, 2009 at 7:43 PM, Dan Homerick <[email protected]> wrote: >> [Sent to the OSM Imports list and to polyshp2osm.py author] >> ... >> I'd almost prefer to modify the polyshp2osm.py to accept non-closed >> ways, since I know Python already (but not Perl) and it doesn't seem >> like a very big change is required. Would anyone be interested in >> doing a code-review + commit to the repository if I do modify it? >> >> Cheers, >> - Dan > > I ended up using "shp-to-osm" to do the import instead. It doesn't > have quite as much flexibility, in that you can't use several fields > in the source data to generate one OSM tag, but it was very easy to > get up and running since it includes all of it's dependencies. > > Found at: > http://redmine.yellowbkpk.com/projects/show/geo > > - Dan > > _______________________________________________ > Imports mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/imports > -- Twitter: @Acrosscanada Blog: http://Acrosscanadatrails.blogspot.com Facebook: http://www.facebook.com/sam.vekemans OpenStreetMap IRC: http://irc.openstreetmap.org @Acrosscanadatrails _______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
