-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gml writer: FeatureCollection's envelope SRS (3.9.1 regression) #10332
Comments
I can confirm with GDAL 3.10.0dev-a44e40295c, released 2024/06/21 (OSGeo4W). Also the name of the geometry has changed. This srsName drop affects the FeatureCollection level Envelope. The featureMembers still have Envelopes with srsName - and with Lat-Lon axis order.
|
…(3.9.1 regression) Fixes OSGeo#10332 Was caused by the fix 3674ec7 for OSGeo#10071 The regression mostly occurs when writing a GML file using ogr2ogr when the source layer has a named geometry column, e.g if the source is a GeoPackage or if using -sql The problem was acutally latent and also could have occured before 3.9.1 if using CreateLayer() without a SRS + CreateGeomField()
That's expected ant not an issue, and not a new behaviour. This is due to SQL SQLite layer reporting a name GEOMETRY geometry field. Direct translation from GeoJSON which has a unnamed/empty geometry field fallbacks to using "geometryProperty" in the GML writer. For the SRS issue, fix in #10334 A workaround is to do a ogr2ogr to a format like GeoJSON (or shapefile, but not GeoPackage, PostGIS, etc) that has not a named geometry field using the -sql clause, and then ogr2ogr that temporary GeoJSON file to GML |
Thanks ! |
…(3.9.1 regression) Fixes #10332 Was caused by the fix 3674ec7 for #10071 The regression mostly occurs when writing a GML file using ogr2ogr when the source layer has a named geometry column, e.g if the source is a GeoPackage or if using -sql The problem was acutally latent and also could have occured before 3.9.1 if using CreateLayer() without a SRS + CreateGeomField()
What is the bug?
When we produce a GML from a GeoJson with a SQL dialect, the gml:Envelope in the response no longer contains SRS.
The srs is however always present if no sql query is put.
By the way, not having srs reverses the axes.
I don't think this change in behavior was intentional?
Steps to reproduce the issue
return :
while :
return :
Versions and provenance
The regression appeared in version 3.9.1.
No worries in version 3.9.0 and earlier.
Additional context
No response
The text was updated successfully, but these errors were encountered: