--
Ticket URL: <https://code.djangoproject.com/ticket/25874>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => assigned
* needs_better_patch: => 0
* owner: nobody => sir-sigurd
* needs_tests: => 0
* needs_docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/25874#comment:1>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/25874#comment:2>
* version: 1.9 => master
Comment:
The GeoJSON format has been recently standardized in RFC 7946. In that
standard, the use of the WGS84 coordinate system is mandatory.
Quoting [https://tools.ietf.org/html/rfc7946#section-4 RFC 7946]:
{{{
4. Coordinate Reference System
The coordinate reference system for all GeoJSON coordinates is a
geographic coordinate reference system, using the World Geodetic
System 1984 (WGS 84) [WGS84] datum, with longitude and latitude units
of decimal degrees. This is equivalent to the coordinate reference
system identified by the Open Geospatial Consortium (OGC) URN
urn:ogc:def:crs:OGC::CRS84. An OPTIONAL third-position element SHALL
be the height in meters above or below the WGS 84 reference
ellipsoid. In the absence of elevation values, applications
sensitive to height or depth SHOULD interpret positions as being at
local ground or sea level.
Note: the use of alternative coordinate reference systems was
specified in [GJ2008], but it has been removed from this version of
the specification because the use of different coordinate reference
systems -- especially in the manner specified in [GJ2008] -- has
proven to have interoperability issues. In general, GeoJSON
processing software is not expected to have access to coordinate
reference system databases or to have network access to coordinate
reference system transformation parameters. However, where all
involved parties have a prior arrangement, alternative coordinate
reference systems can be used without risk of data being
misinterpreted.
}}}
Therefore, I suggest to won't fix this ticket. Any comment?
--
Ticket URL: <https://code.djangoproject.com/ticket/25874#comment:3>
Comment (by Sergey Fedoseev):
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25874#comment:4>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/25874#comment:5>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"24023c6a8fc768ccb72108d2dd4fd8ece04075fd" 24023c6]:
{{{
#!CommitTicketReference repository=""
revision="24023c6a8fc768ccb72108d2dd4fd8ece04075fd"
Fixed #25874 -- Made GEOSGeometry read SRID from GeoJSON input.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25874#comment:6>