Opened 11 years ago

Closed 9 years ago

#294 closed task (fixed)

Rationalize support for EMPTY

Reported by: pramsey Owned by: pramsey
Priority: medium Milestone: PostGIS 2.0.0
Component: postgis Version: master
Keywords: empty Cc:


Apply the rules for EMPTY geometries as laid out in DevWikiEmptyGeometry to all geometry functions.

Change History (6)

comment:1 Changed 11 years ago by pramsey

Type: defecttask

comment:2 Changed 11 years ago by robe

Just itemizing some of these cases as I come across them in tests.

SELECT ST_Distance_Sphere(ST_GeomFromText('POLYGON EMPTY',4326),ST_GeomFromText('POINT(1 3)',4326))

Gives error: geometry_distance_spheroid: Only point/line/polygon supported.

Though curiously (which I thought they shared some code)

SELECT ST_Distance(geography(ST_GeomFromText('POLYGON EMPTY',4326)),geography(ST_GeomFromText('POINT(1 3)',4326)));

Returns null as expected

comment:3 Changed 9 years ago by strk

With r8382 I fixed handling of EMPTY by ST_Buffer and put the regression test in tickets.sql, but I guess it'd make more sense to have an empty.sql testcase testing each and every line from the wiki page.

Does anyone feel like stubbing it ? Or I'll do it.

comment:4 Changed 9 years ago by strk

r8408 inaugurates a regression test for "empty"

comment:5 Changed 9 years ago by strk

#692 is about the spatial predicates portion of this

comment:6 Changed 9 years ago by strk

Resolution: fixed
Status: newclosed

This is completed as of r8415

Note: See TracTickets for help on using tickets.