[Talk-ca] [Imports] Shp2OSM : various questions
acrosscanadatrails at gmail.com
Tue Nov 17 19:06:10 GMT 2009
Hi Frank, cc: imports@ talk-ca@
I havent looked at that polyshp2osm.py script (at all) it might be worth
exploring, as it could help out with the inner/outer/relations and dealing
with the large amount of shps in an area.
Like i mentioned the other day,. perhaps just the wooded area file could be
done with a separate process than the rest of the canvec data? And the
Rivers/waterbody file could also be done with a separate process so then 80
of the 90 features can be dealt with, during 1 script routeen.
Hi Ian, does the shp-to-osm java program now handle that 'non-connecting
intersecting ways' bug? ... it effects the features of railways &
powerlines & rivers, as well as the canvec version of the roadnetwork. If
not, then perhaps the shp2osm script needs to be used to deal with it.
Anyway, its now Frank thats the one in charge of it, but i just wanted to
point that out.
On Tue, Nov 17, 2009 at 10:56 AM, Emilie Laffray
<emilie.laffray at gmail.com>wrote:
> Lennard wrote:
> > Emilie Laffray wrote:
> > [polyshp2osm.py]
> >> Yup hence the reason why I modified it to be more current (not in SVN)
> >> for the Corine import.
> > Did you get it to use shared nodes for touching polygons for CLC? Or is
> > node merging something you consider to be done after the initial import?
> > Perhaps we better take this thread to [imports]?
> The node merging step was done with a Java program, just after the
> generation of the OSM file. The shapefile that we were getting were
> shapefiles built out of the database that we sorted. I really need to
> finish the write up about the Corine Import.
> Emilie Laffray
> Talk-ca mailing list
> Talk-ca at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Talk-ca