Opened 2 years ago
Last modified 22 months ago
#5262 closed enhancement
Add support of Undefined Cartesian SRS (-1) — at Initial Version
| Reported by: | lbartoletti | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 3.4.0 |
| Component: | postgis | Version: | 3.3.x |
| Keywords: | Cc: | lbartoletti |
Description
Postgis uses 0 as undefined SRS. But you can have an undefined geographic srs (0) and an undefined cartesian srs (-1). This is what is proposed in the GeoPackage table[1][2] (and I think it comes from an OGC standard I forgot).
If, with ogr2ogr, I convert my "local" cartesian table to postgis, it will be an undefined srs (0, since there is a constraint CHECK (srid > 0 AND srid ⇐ 998999) and SRID_UNKOWN is 0[3]).
Can cause trouble if you have two undefined tables, one geographic and the other one cartesian.
[1] https://gdal.org/drivers/vector/gpkg.html#coordinate-reference-systems [2] http://www.geopackage.org/guidance/getting-started.html#gpkg_spatial_ref_sys [3] https://github.com/postgis/postgis/blob/3e38e0b83b98925122bb22dff958a7a603ee4a42/liblwgeom/liblwgeom.h.in#L210
