Some geometries don't work with ST_Union and gives a non-noded intersection

Question

I'm getting a lot of errors like this:

GEOSUnaryUnion: TopologyException: found non-noded intersection between LINESTRING (147.254 -42.8705, 147.254 -42.8705) and LINESTRING (147.254 -42.8705, 147.254 -42.8705) at 147.25355728849621 -42.870521684000678

I am calling ST_MakeValid(ST_Union(ST_SnapToGrid(mpoly))) on an aggregate of all rows that match my filter.

You want to call ST_MakeValid before ST_Union. If union runs into an invalid geometry, it's more likely to throw a topo exception — Regina Obe, Oct 06 '15 at 06:04
yeah I ran MakeValid before Union and I still got this error — Theo F, Feb 28 '19 at 16:43

score 2 · Answer 1 · answered Jul 17 '17 at 20:17

There is a similar question at How best to fix a non-noded intersection problem in PostGIS?. Some have had success by performing ST_MakeValid, ST_Buffer or ST_SnapToGrid to the geometry before to performing the union. I see you tried SnapToGrid. Have you tried something like:

ST_Union(ST_MakeValid(mpoly))

or

ST_Union(ST_Buffer(mpoly, 1e-5))

The presentation PostGIS: Tips for Power Users outlines some potential sources of trouble when unioning geometries.

score 0 · Answer 2 · answered Jun 30 '21 at 13:34

Just change the order of functions, add the grid size to snap 0.0001 for degrees, collenct only polygons for query ( 3 stands for polygons):

Select
ST_Union(
  ST_CollectionExtract(
    ST_MakeValid(
      ST_SnapToGrid(geom,0.0001)
    ),3
  )
)
From
  mpoly

Some geometries don't work with ST_Union and gives a non-noded intersection

2 Answers2

Linked