[Imports] polyshp2osm.py

2009-10-19 Thread Dan Homerick
[Sent to the OSM Imports list and to polyshp2osm.py author] A couple of questions about polyshp2osm.py: Should I be concerned by the "" if I'm only working with nodes and ways? Where do I find the changes that occurred between ver 0.5 and ver 0.6 of the API? As far as I can tell, and as the name

Re: [Imports] polyshp2osm.py

2009-10-20 Thread Emilie Laffray
Dan Homerick wrote: > [Sent to the OSM Imports list and to polyshp2osm.py author] > > A couple of questions about polyshp2osm.py: > > Should I be concerned by the "" if I'm only working > with nodes and ways? Where do I find the changes that occurred between > ver 0.5 and ver 0.6 of the API? > > As

Re: [Imports] polyshp2osm.py

2009-10-20 Thread Dan Homerick
On Mon, Oct 19, 2009 at 7:43 PM, Dan Homerick 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

Re: [Imports] polyshp2osm.py

2009-10-20 Thread Sam Vekemans
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 th

Re: [Imports] polyshp2osm.py

2009-10-20 Thread Ian Dees
On Tue, Oct 20, 2009 at 5:45 PM, Sam Vekemans wrote: > 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

Re: [Imports] polyshp2osm.py

2009-10-20 Thread Dan Homerick
On Tue, Oct 20, 2009 at 3:45 PM, Sam Vekemans wrote: > Hi, > Can you give an example of a situation when you'd need to use multiple > source fields for 1 osm tag? Sure. To give a little context, the import I just did is for waterways. The source data has a boolean field NAMED that indicates wheth

Re: [Imports] polyshp2osm.py

2009-10-20 Thread Sam Vekemans
On Tue, Oct 20, 2009 at 4:07 PM, Ian Dees wrote: > On Tue, Oct 20, 2009 at 5:45 PM, Sam Vekemans < > acrosscanadatra...@gmail.com> wrote: > >> 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 wa

Re: [Imports] polyshp2osm.py

2009-10-20 Thread Sam Vekemans
On Tue, Oct 20, 2009 at 4:42 PM, Dan Homerick wrote: > On Tue, Oct 20, 2009 at 3:45 PM, Sam Vekemans > wrote: > > Hi, > > Can you give an example of a situation when you'd need to use multiple > > source fields for 1 osm tag? > > Sure. To give a little context, the import I just did is for > wat

Re: [Imports] polyshp2osm.py

2009-10-20 Thread andrzej zaborowski
2009/10/21 Sam Vekemans : > to: imports@ list >     There ought to be a way that shp files can be 1st 'sliced'.. > Ie.  (Geographically cut into an arbitrary grid (regardless of the shape of > the polygon) 4, 16, 256 or whatever size)  so then each square can be dealt > with independently. > y

Re: [Imports] polyshp2osm.py

2009-10-20 Thread andrzej zaborowski
2009/10/21 Dan Homerick : > Also, my first attempt at > uploading failed, because JOSM added a modified='true' attribute[1] to > the ways when I did the merges. I used a text editor's find/replace to > remove those, and the second attempt went smoothly. If that was action="modify", that shouldn't