[Tile-serving] [osm2pgsql] planet_osm_polygon import seem sensitive to tags order (#35)

jocelynj notifications at github.com
Fri May 31 23:30:48 UTC 2013

I'm hitting an issue with some tags that are not correctly imported in table planet_osm_polygons, and I think it might be because of the tags order in the .osm source.

For example, these two osm files only differ on the tag ordering of type=boundary:

--- alsace.osm  2013-06-01 00:38:25.182404624 +0200
+++ alsace-fail.osm     2013-06-01 01:29:07.841660538 +0200
@@ -31910,6 +31910,7 @@
     <member type="way" ref="48683073" role="outer"/>
     <member type="way" ref="48565263" role="outer"/>
     <member type="way" ref="23301554" role="outer"/>
+    <tag k="type" v="boundary"/>
     <tag k="admin_level" v="4"/>
     <tag k="alt_name:la" v="Elisatia"/>
     <tag k="boundary" v="administrative"/>
@@ -31933,7 +31934,6 @@
     <tag k="ref:INSEE" v="42"/>
     <tag k="ref:ISO 3166-2" v="A"/>
     <tag k="ref:NUTS" v="FR42"/>
-    <tag k="type" v="boundary"/>
     <tag k="wikipedia" v="fr:Alsace"/>

With the second file, admin_level column of planet_osm_polygon is not filled with value 4.

Must the tags be sorted before importing with osm2pgsql ?

Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20130531/b646c9e3/attachment.html>

More information about the Tile-serving mailing list