Invalid GeoJSON output.

[ssrebelious]

In my model I have a linestring field with EPSG:3857: geom = LineStringField(srid=3857). Using djangorestframework-gis==0.14 I get output coordinate values like this:

{"type": "LineString", "coordinates": [[4162390.815448472, 7521835.900630971], [4161637.5299245478, 7521415.799088784], [4161478.181063718, 7520778.403645463]]}

Obviously I have output coordinates in EPSG:3857 and not in EPSG:4326. This violates GeoJSON specification:

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.

[nemesifier]

So the right solution is to output only in WGS 84 format.

[StefanBrand]

Workaround is documented here: #250 (comment)

[StefanBrand]

@ssrebelious @nemesifier I have created a PR that would fix this issue if merged. Please have a look: #326

[auvipy]

thanks! we just need little work before we merge it

[nemesifier]

#326 is merged, anyone running into this issue should be able to resolve it by using the new transform argument.