Opened 9 years ago
Closed 8 years ago
#25874 closed New feature (fixed)
allow GEOSGeometry to read SRID from GeoJSON input
Reported by: | Sergey Fedoseev | Owned by: | Sergey Fedoseev |
---|---|---|---|
Component: | GIS | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Change History (6)
comment:1 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 9 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 8 years ago
Version: | 1.9 → master |
---|
comment:4 by , 8 years ago
If CRS is specified in GeoJSON that means it's in pre-RFC format. I don't think it's sane to set SRID to 4326, if some other SRID is specified.
The implementation of this feature is quite easy: GDAL sets SRID from GeoJSON but we simply lose it when OGR is conveted to GEOS.
Note:
See TracTickets
for help on using tickets.
The GeoJSON format has been recently standardized in RFC 7946. In that standard, the use of the WGS84 coordinate system is mandatory.
Quoting RFC 7946:
Therefore, I suggest to won't fix this ticket. Any comment?