Opened 10 years ago
Last modified 7 years ago
#3130 new enhancement
ST_MMin(geometry), ST_MMax(geometry)
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
It's easy to get min/max values for X,Y and Z for geometries (via implicit cast to BOX3D) but there's no way to get min M (not having a BOXAnyD).
This ticket is to add ST_MMin(geometry) and ST_MMax(geometry) ( then one day we should maybe have all the others also work directly on geometry )
Change History (2)
comment:1 by , 10 years ago
| Milestone: | PostGIS 2.2.0 → PostGIS Future |
|---|---|
| Priority: | high → medium |
Note:
See TracTickets
for help on using tickets.
By implementing #3139 this would not be that important anymore as it could be expressed with:
ST_M(ST_StartPoint(ST_BoundingRange(geom))) and ST_M(ST_EndPoint(ST_BoundingRange(geom)))