Open kannes opened 1 year ago
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 gmlas:convertformat_gmlas
algorithm. In that case one must not tinker with the INPUT_FILE
parameter as I did above, INPUT_FILE
is correct then, INPUT
is not.
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: https://github.com/BRGM/gml_application_schema_toolbox/blob/f40f85f02fac714217c0278ae1f47d93dd6270e7/gml_application_schema_toolbox/gui/import_gmlas_panel.py#L314-L319
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 https://github.com/BRGM/gml_application_schema_toolbox/blob/607accd5fc69892878d432694947517bdb7acb2b/gml_application_schema_toolbox/gui/gmlas_panel_mixin.py#L99 to always use the
gmlas:convertformat_gmlas
algorithm instead, it also crashed saying that theINPUT
file could not be found.Logs