[Tile-serving] [openstreetmap/osm2pgsql] Import of changes failing because of TopologyException (#787)

[Paul Norman]

> The original error does not look like it comes from osm2pgsql itself. @JesseCrocker Do you have additional triggers installed on planet_osm_polygon? Then you can add a validity check there (using ST_IsValid().

My guess is a functional index is present.

The two options I see are to require geos again and validate the geometries, or to default to adding a trigger for anything other than 4326.

-----

> I just checked and relation 2823696 as assembled by osmium correctly converts from EPSG:4326 to EPSG:3857 without becoming invalid. So whatever happens here is probably the result of some other error in processing and not inherent to the coordinate conversion.

How'd you check this, and what versions of components?

> you cannot completely rely on the database being free of self intersections

All geometries being ST_IsValid is an **essential** constraint.

-- 
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/787#issuecomment-331764202
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20170925/15dafc75/attachment-0001.html>