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
35058	Update GDAL integration	David Smith	David Smith	"During the GDAL 2.x and 3.x releases GDAL has expanded its public entry points, added new features. While one of these new features is curved geometries #34406 I think we should conduct a review and consider if new items should be added to Django. Here's a few specific items to start with:

**OGR_G_CoordinateDimension**

[https://gdal.org/api/vector_c_api.html#_CPPv428OGR_G_GetCoordinateDimension12OGRGeometryH OGR_G_CoordinateDimension ] is deprecated in favour of `OGR_G_CoordinateDimension()`, `OGR_G_Is3D()` and `OGR_G_IsMeasured()`.

**OGRwkbGeometryType**

Support should be added to understand a wider scope of WKT inputs. For example [https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry `POINT ZM (1 1 5 60)`] is valid but currently results in an error. ( `Invalid OGR Integer Type: 3001`). 

I think maybe this is because new WKB types are supported see OGRwkbGeometryType : https://gdal.org/doxygen/ogr__core_8h.html and https://github.com/OSGeo/gdal/blob/62c1489feab9312d0468abde0ad13d7b35ce27f7/ogr/ogr_core.h#L529. 

This likely needs to be fixed before `OGR_G_CoordinateDimension`. (You can't write a test for `OGR_G_IsMeasured` without first creating a geometry with a measure)

**OGR_G_CreateFromWkbEx**

[https://gdal.org/api/vector_c_api.html#_CPPv421OGR_G_CreateFromWkbExPKv20OGRSpatialReferenceHP12OGRGeometryH6size_t OGR_G_CreateFromWkbEx] is added in GDAL 3.3. I think we should prefer this over the existing `OGR_G_CreateFromWkb` when available. The difference is the new method supports large (2gb+) inputs. In 3.3+ the old method now raises and error suggesting use of the new method, and was unsupported in previous versions. 
"	Cleanup/optimization	assigned	GIS	4.2	Normal				Accepted	0	0	0	0	0	0