Python bindings: GetOutputDriversFor outdated #8277
Assignees
Comments
rouault
added a commit
that referenced
this issue
Sep 2, 2023
osgeo_utils: allign base.get_extension() and util.DoesDriverHandleExtension() on C++ versions, and add tests (fixes #8277)
rouault
added a commit
that referenced
this issue
Sep 2, 2023
…ension() on C++ versions, and add tests (fixes #8277)
rouault
added a commit
that referenced
this issue
Sep 3, 2023
[Backport release/3.7] osgeo_utils: allign base.get_extension() and util.DoesDriverHandleExtension() on C++ versions, and add tests (fixes #8277)
elpaso
pushed a commit
to elpaso/gdal
that referenced
this issue
Sep 4, 2023
…ension() on C++ versions, and add tests (fixes OSGeo#8277)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't really use it, but I noticed it so just as a heads up.
GetOutputDriversFor in the python bindings is a duplicated implementation of the cpp version in commonutils.cpp, but it isn't really up-to-date anymore: eg. the specific logic to handle ".gpkg.zip" and ".shp.zip" isn't implemented.
I also noticed a bug: in the python version of
DoesDriverHandleExtensionthe space-delimited extensions aren'tsplitbut just a string-find is used. This leads to too many drivers being returned: e.g. for.geojson2 drivers are returned (GeoJSONandGeoJSONSeq) instead of onlyGeoJSONbecause extension"geojson"is also found in the string"geojsonl geojsons".Possibly it would be better if the cpp version would be reused one way or the other to avoid the double implementation...
The text was updated successfully, but these errors were encountered: