Opened 6 years ago
Last modified 6 years ago
#4048 new enhancement
Make _ST_BestSRID public
| Reported by: | dbaston | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
This is a useful function for which there is demand, and the cat was let out of the bag a long time ago anyway.
Why not make a public equivalent that produces actual EPSG codes and documents its behavior?
Change History (2)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
| Milestone: | PostGIS 2.5.0 → PostGIS Fund Me |
|---|
Note:
See TracTickets
for help on using tickets.
WRT the "actual EPSG" codes issue, the reason is that the EPSG table is not a fixed entity, so we cannot count on the projections we want (UTMs, etc) being at the code-points we expect. We cannot even count on there being spatial_ref_sys records at all. Hence the fake codes.