[postgis-tickets] [PostGIS] #5367: Tiger extension loading invalid geometries

[PostGIS]

#5367: Tiger extension loading invalid geometries
----------------------------+---------------------------
 Reporter:  jnu             |      Owner:  robe
     Type:  defect          |     Status:  new
 Priority:  low             |  Milestone:  PostGIS 3.3.3
Component:  tiger geocoder  |    Version:  3.2.x
 Keywords:                  |
----------------------------+---------------------------
 I discovered a small number of invalid geometries among the data loaded
 with the Tiger CENSUS data loader. The `place` table contains 4 invalid
 entries, per `ST_IsInvalid`:


 {{{
 SELECT plcidfp, namelsad, St_IsInvalidReason(the_geom) reason
 FROM tiger.place
 WHERE St_IsInvalid(the_geom);

  plcidfp |       namelsad        |                 reason
  --------+-----------------------+---------------------------------------
  0427820 | Glendale city         | Holes are nested[-112.40957 33.529845]
  4740000 | Knoxville city        | Holes are nested[-84.082463 35.893129]
  1738570 | Joliet city           | Holes are nested[-88.074056 41.510616]
  3771940 | Wesley Chapel village | Holes are nested[-80.682658 34.989184]
 }}}

 There were 120 invalid geometries in the `zcta5` table as well. Other
 tables appeared free from errors (`state, county, cousub, tract, bg`).

 I've run `St_MakeValid(the_geom)` as a workaround. I don't believe these
 errors originated in my application, though I don't know for certain they
 are introduced by tiger extension, either.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5367>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.