Opened 6 years ago

Closed 6 years ago

#2696 closed defect (fixed)

ST_NumInteriorRings and MULTIPOLYGONS

Reported by: pramsey Owned by: robe
Priority: medium Milestone: PostGIS 2.0.6
Component: documentation Version: 2.1.x
Keywords: Cc: robe

Description

As discussed in #1345 (but never resolved?) ST_NumInteriorRings returns NULL when called on a MULTIPOLYGON. Previous behavior (and still documented that way: http://postgis.org/docs/ST_NumInteriorRings.html) was to return the number of rings in the first geometry of the collection. This should be fixed in code or changed in docs.

Change History (4)

comment:1 Changed 6 years ago by robe

Component: postgisdocumentation
Milestone: PostGIS 2.1.3PostGIS 2.0.6
Owner: changed from pramsey to robe

Please don't point at the old documentation :) but admittedly the new documentation hasn't beeen update either.

http://postgis.net/docs/ST_NumInteriorRings.html

Sooo we will just call this a documentation bug and flag behavior changed in 2.0?

comment:2 Changed 6 years ago by pramsey

I guess. I hate that this broke my workshop examples, or that I have to explain polygon/multipolygon in my workshop, but I suppose I can live w/ it. All these singleton functions, it's nice if they work on non-singletons, since multi's are so common in shapefile loads, but there's always that fuzzzyness about their correctness then. Returning NULL seems like a bit of a dodge in its own way.

comment:3 Changed 6 years ago by robe

Hey you had your chance to fix it in 2.0 when I screamed about it that it broke my tiger geocoder and we also screamed it broke pgRouting code and they had to recode all their stuff to work around it. Did anyone listen :).

comment:4 Changed 6 years ago by robe

Resolution: fixed
Status: newclosed

corrected doco

branch 2.0 at r12416, branch 2.1 at r12414, trunk 2.2 at r12412 (minor edits at r12415 and r12413)

Note: See TracTickets for help on using tickets.