converting a KMZ to OSM and getting errors in JOSM

We’ve got a bunch of KML files that we’d like to convert to OSM. We have found a way to do the conversion, but it’s nasty… our map guys says “I do all of my editing in ArcGIS then convert the shp to GPX using DNRgarmin then convert to an osm in gps babel” .

When I bring the resulting sample OSM file into JOSM and vaildate it I get 40 Warnings.

  • Nodes at same position (10)
  • Way end node near other way (30)

here are the files:

http://www.alsocreative.com/mapcrap/AOGDkmz.kmz
http://www.alsocreative.com/mapcrap/AOGDOSM.osm

here are screenshots of the errors in JOSM with the file loaded:

http://www.alsocreative.com/mapcrap/endnodenearotherway.png
http://www.alsocreative.com/mapcrap/warnings.png

I’m not a cartographer, just a developer. What is wrong with this file?

There are plenty of tools for doing direct conversion of ESRI shape files to OSM XML format. These are a bit less of a pain than the technique you’ve used.

Check out the following on the wiki: shp2osm, ogr2osm, Merkaator (can directly read shape files). Its also possible to push SHP files to PostGIS and then use SQL to populate a ‘simple’ pgSQL schema & pull data out with osmosis. All of these processes are non-lossy with respect to data attributes.

A particular problem with standard conversion techniques from shape is the creation of duplicate nodes (nodes in the same position, usually belonging to two shapes in the original file). The validator can be used to fix them (it just merges the nodes). So it may be that your validator problems are pretty trivial.

Errors ? You said warnings!

These links do not work.

Developers don’t ignore warnings? :wink:

For the rest I think that the conversion was ok.