Re: [gdal-dev] GPKG geometry column name expectations with sqlite dialect

2024-09-30 Thread Scott via gdal-dev
"Geometry Column = ..." in ogrinfo output. If the method returns an empty string then a special name "_ogr_geometry_" must be used. That's from the OGR driver docs: https://gdal.org/en/latest/user/ogr_sql_dialect.html I've always found it a bit weird as well. If I'm not sure I'll try, geom, ge

Re: [gdal-dev] GPKG geometry column name expectations with sqlite dialect

2024-09-30 Thread Even Rouault via gdal-dev
Jesse, Le 30/09/2024 à 20:35, Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] via gdal-dev a écrit : Hi, I have two geopackage database files that were constructed, somehow, in a way that one has a geometry column called ‘geometry’ and the other ‘geom’.  QGIS nor OGR seem

[gdal-dev] GPKG geometry column name expectations with sqlite dialect

2024-09-30 Thread Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] via gdal-dev
Hi, I have two geopackage database files that were constructed, somehow, in a way that one has a geometry column called ‘geometry’ and the other ‘geom’. QGIS nor OGR seem to have much an issue with this. Both handle / display all the features in the expected ways. However, for the gpkg with