-
Notifications
You must be signed in to change notification settings - Fork 18
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
QgsProcessingException when loading GMLAS #263
Labels
bug
Houston, we've a problem!
Comments
Seems like it was simply not tested and fully implemented on newer QGIS. As a workaround I removed the if clause to always use the internal |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Description
Trying to load a layer from a WFS using the wizard with GMLAS results in an error for me:
The german message says that there was no value passed for the parameter
INPUT
.The code path confirms that:
gml_application_schema_toolbox/gml_application_schema_toolbox/gui/import_gmlas_panel.py
Lines 314 to 319 in f40f85f
I already tried changing that to
INPUT
but then I get anotherQgsProcessingException
about the file path not being found (GMLAS:/tmp/tmpfudmiwrq.gml
). I guess the prefix is the issue, the file exists. My GDAL should support GMLAS,ogrinfo GMLAS:/tmp/tmpfudmiwrq.gml
lists 25 layers in it.The QGIS docs for gdal:convertformat do not list a
INPUT_FILE
parameter so I guess it is simply swallowed in any case?To Reproduce
Steps to reproduce the behavior:
Expected behavior
I guess the data should get loaded as layer?
Additional Context
get_db_format
crashWithout an available spatialite database, the plugin would crash with:
I checked
"get_db_format in dir(self.databaseWidget) == True
to be true, no idea what's going on there...Also not working with internal
gmlas:convertformat_gmlas
algorithmWhen I changed the if clause in
gml_application_schema_toolbox/gml_application_schema_toolbox/gui/gmlas_panel_mixin.py
Line 99 in 607accd
gmlas:convertformat_gmlas
algorithm instead, it also crashed saying that theINPUT
file could not be found.Logs
The text was updated successfully, but these errors were encountered: