id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
31695	GDAL 3 axis order causes inconsistency in geodjango api and breaks geometry calculations	Ryan Burt	nobody	"GDAL 3 has changed the default order of coordinates to (latitude, longitude):  [https://gdal.org/tutorials/osr_api_tut.html#crs-and-axis-order]
Consequently, geometry fields are saved in the spatial database as (latitude, longitude) whereas the expected order is (longitude, latitude).

Any geospatial calculation performed on a queryset also expects the coordinates to be in (longtiude, latitude), but as they are not saved in this format, the calculations results are incorrect and cause a variety of problems.

Extra support for GDAL 3 is required such that insert order of coordinates for saving geometry fields matches what the database expects.

Tested with django 3.0.7 against gdal 3.0.4, gdal 3.1.0, and gdal 2.4.3. "	New feature	closed	GIS	3.1	Normal	duplicate	gdal 3		Unreviewed	0	0	0	0	0	0