-
Notifications
You must be signed in to change notification settings - Fork 8
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
Crash opening features with lots of xlink:href #19
Comments
Thanks for the report. Looking at https://gdal.org/drivers/vector/gml.html#gml-xlink-resolving then setting I wonder whether there any disadvantages to it? I guess a slight overhead in saving resolved objects to DB rather than keeping them in memory, but any others? Maybe it would be better to allow the user to choose between |
It seems that there are no disadvantages to using |
* Use HUGE instead of NONE for GDAL option GML_SKIP_RESOLVE_ELEMS See #19
Thank you for fixing the issue. Are there any plans to deploy those fixes to the QGIS Plugin repository's version of the plugin? That would make rollout easier in our organisation. |
@JPPauly Thanks for the feedback. To be honest I'd completely forgotten that this hadn't been done - I'll see to it, that the repo version gets updated and close this ticket once it's done. |
Plugin version 0.9.10 is now published and approved in the QGIS Plugins repository. |
* Due to qgisinspiretools#19 the GDAL-configuration GML_SKIP_RESOLVE_ELEMS was set to HUGE when the user requests resolving of xlink:href (previously NONE). * This change is presumably the reason for problems reported resolving in qgisinspiretools#25. * Since probably not everyone will be satisified with one or other of the options then the user should be able to choose which to use once resolving of xlink:href is activated, thus removing the need for the devloper to decide which option to use and passing this decision to the user. * The default GML_SKIP_RESOLVE_ELEMS is maintained as HUGE.
Hello,
on loading features with lots of xlink:href elements with the resolve option activated, f.e. from INSPIRE AU.AdministrativeUnits, QGIS3 crashes.
Example-service that leads to crashes on loading AdministrativeUnits: https://www.geodaten-mv.de/dienste/inspire_au_atkis_bdlm_download
I found a solution by changing the line 1010 in wfsclientdialog.py to:
gdal.SetConfigOption('GML_SKIP_RESOLVE_ELEMS', 'HUGE')
The text was updated successfully, but these errors were encountered: