GeoJSON serializer producing invalid output (crs attribute)

[Jeremy Thompson]

The built-in GeoJSON serializer is producing invalid GeoJSON. The serialized output has a section like:

"crs": {"type": "name", "properties": {"name": "EPSG:4326"}}

However, according to the GeoJSON spec the crs attribute was removed from the spec in August of 2016 (ref: ​https://datatracker.ietf.org/doc/html/rfc7946#appendix-B.1)

This is causing issues when trying to use GeoJSON as the intermediary data format for passing data to other libraries (e.g. Leaflet ​https://leafletjs.com considers GeoJSON with the crs attribute as invalid and fails to parse it).

More information in the forum discussion here: ​https://forum.djangoproject.com/t/geojson-serializer-producing-invalid-output-crs/37097

[Claude Paroz]

Many thanks for noticing!

[Jeremy Thompson]

After a bit more investigation, I think my initial problem with Leaflet was due to how I was using the json_script filter. I was passing the string that was output from the serializer, which meant that the double quotes were getting escaped, which led to invalid JSON. When I created a Python dict with the same information, things worked as expected.

I think this issue still might be relevant though? But not for my original reason.

[Claude Paroz]

Thanks for the update. Yes, this change still makes sense, however with lesser priority.

[Jeremy Thompson]

Comments in PR addressed!

[Sarah Boyce <42296566+sarahboyce@…>]

In 918e7a2:

Fixed #35989 -- Removed crs from GeoJSON serializer.

Specification of coordinate reference systems (crs) was removed from the GeoJSON spec in 2016.
​https://datatracker.ietf.org/doc/html/rfc7946#appendix-B.1