#1299 closed enhancement (invalid)
ST_UnknownSRID()
Reported by: | dustymugs | Owned by: | pramsey |
---|---|---|---|
Priority: | low | Milestone: | PostGIS Fund Me |
Component: | postgis | Version: | master |
Keywords: | Cc: |
Description
I'd like to see PostGIS provide a SQL function that output's the software's UNKNOWN_SRID. This would help at the present time where it looks like there still is discussion about 0 vs -1.
Also, nothing is stopping a user from changing UNKNOWN_SRID to something other than 0 or -1, say -9999. So a function ST_UnknownSRID would allow users of that PostGIS instance to know what that instance's unknown SRID is.
Heck, I'll write the patch and attach it if everyone is fine with it.
Change History (5)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Thanks strk! That's easy enough.
As for changing UNKNOWN_SRID, I meant SRID_UNKNOWN. A user could change the value of SRID_UNKNOWN in liblwgeom.h before compiling PostGIS.
comment:3 by , 13 years ago
I wasn't necessarely against wrapping my implementation in a function… maybe an SQL one.
comment:4 by , 13 years ago
It'd be great if you could turn your implementation into an SQL function. I'm always hesitant to make changes to the PostGIS side.
The function implementation would be $$ SELECT ST_Srid('POINT(0 0)') $$
I'm not sure what you mean by "nothing is stopping a user from changing UNKNOWN_SRID".