Opened 9 years ago
Last modified 7 years ago
#3013 new enhancement
Dimension-based geometry column constraints
| Reported by: | mpd | Owned by: | pramsey |
|---|---|---|---|
| Priority: | low | Milestone: | PostGIS Fund Me |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
Geometry column constraints are type-based, eg POINT, LINESTRING, POLYGON.
In the case of an awful lot of polygonal (dimension==2) data this makes it necessary to use GEOMETRY (because so much data contains MULTIPOLYGONS as well as POLYGONS, eg any dataset of the countries of the world).
If the type constraints could also, optionally, be dimension==0 (ie POINT or MULTIPOINT), dimension==1 (ie LINESTRING or MULTILINESTRING) or dimension==2 (ie POLYGON or MULTIPOLYGON), then GEOMETRY would not have to be used so frequently.
Newer geometry types could also be added to the relevant constraint, eg CURVEPOLYGON to dimension==2, TIN to dimension==3, etc.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Milestone: | → PostGIS Future |
|---|
Note:
See TracTickets
for help on using tickets.
The usual way to handle this case is by forcing all inputs to multi (ST_Multi).
Concepts of "puntal", "lineal" and "areal" started being introduced (from GEOS to PostGIS Topology) but no attempt is been made to land them in geometry_columns or typmod