[Tile-serving] [openstreetmap/osm2pgsql] Should planet_osm_polygons have MultiPolygon geometry type, not Geometry? (#573)

[Rory McCann]

Now, when you use osm2pgsql, the planet_osm_polygons table has a `way` column with type `geometry(Geometry, $SRID)`. This means the `way` could could contain any sort of geometry, points, lines, polygons, etc. This seems a little silly, surely the planet_osm_polygons table should be some sort of polygon type. Hence it would make sense for the type to be a MultiPolygon. Standard Polygons can be converted to MultiPolygons (a multipolygon with just one polygon).

The reason for the issue is firstly to ask: **Does this make sense? Or *should* planet_osm_polygons be a Geometry type?** I asked about this on `#osm-dev

My main reason for wanting this, is because I had a problem with mapnik taking a very long time to start up (>1hr) because it was trying to find the geometry type of queries in the openstreetmap/openstreetmap-carto style which used the polygon table. As far as I could tell, [this mapnik function](https://github.com/mapnik/mapnik/blob/2a46e4517a0ec32b9aad4580814e9dbcaf1221b3/plugins/input/postgis/postgis_datasource.cpp#L1130) will run each query and look at the first 5 results. Many of the osm-carto 

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/573
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20160421/23f74aa4/attachment.html>