QuickOSM should check the timeout value against its timeout

[Gustry]

From the settings saved in QGIS, QuickOSM should check the value saved and compare it to its own timeout value.

This value can be overriden by the API call per request also.

[BenStonebreaker]

QGIS-Version: 3.22.14-Białowieża QGIS-Codeversion: 4cde646c Qt-Version: 5.15.3 Python-Version: 3.9.5 GDAL-Version: 3.6.1 GEOS-Version: 3.11.1-CAPI-1.17.1 PROJ-Version: Rel. 9.1.1, December 1st, 2022 PDAL-Version: 2.4.3 (git-version: f8d673) Algorithmus beginnt bei: 2023-03-28T09:58:07 Algorithmus Laden Sie OSM Daten aus einer Abfrage in einem Bereich herunter startet… Eingabeparameter: { 'AREA' : 'Bad Rappenau', 'FILE' : 'TEMPORARY_OUTPUT', 'KEY' : 'highway', 'SERVER' : 'https://lz4.overpass-api.de/api/interpreter', 'TIMEOUT' : 25, 'VALUE' : 'public' }

Building the query. All OSM objects with the key 'highway'='public' in Bad Rappenau are going to be downloaded. Ergebnisse: {'OUTPUT_OQL_QUERY': '[out:xml] [timeout:25];\n area(3600410526) -> .area_0;\n(\n node"highway"="public";\n way"highway"="public";\n relation"highway"="public";\n);\n(._;>;);\nout body;', 'OUTPUT_URL': 'https://lz4.overpass-api.de/api/interpreter?data=[out:xml] [timeout:25];%0A area(3600410526) -%3E .area_0;%0A(%0A node%22highway%22%3D%22public%22;%0A way%22highway%22%3D%22public%22;%0A relation%22highway%22%3D%22public%22;%0A);%0A(._;%3E;);%0Aout body;&info=QgisQuickOSMPlugin'} Downloading data and OSM file. Traceback (most recent call last): File "C:\Users/r/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\quick_osm_processing\quickosm_process.py", line 351, in processAlgorithm return self.process_road(context, url) File "C:\Users//AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\quick_osm_processing\quickosm_process.py", line 138, in process_road osm_file = connexion_overpass_api.run() File "C:\Users//AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\core\api\connexion_oapi.py", line 85, in run raise NetWorkErrorException('Overpass API', ', '.join(self.errors)) QuickOSM.core.exceptions.NetWorkErrorException: Overpass API : Download gescheitert: Das Zeitlimit für die Verbindung wurde überschritten

Execution failed after 42.40 Sekunden

Lade Ergebnis Layer Algorithmus 'Laden Sie OSM Daten aus einer Abfrage in einem Bereich herunter' beendet

[Gustry]

@BenStonebreaker and others : it seems you can try to switch to z.overpass-api.de instead of lz4.overpass-api.de, according to this answer on GIS-Se

[mmd-osm]

Please use overpass-api.de instead of a single hostname like z.overpass-api.de (which will go out of service soon, and is no longer included in the overpass-api.de DNS record).

[Gustry]

Thanks @mmd-osm I was thinking the same this afternoon about a few tickets coming on GitHub. What is the best way to see this kind of updates ? I was looking on https://wiki.openstreetmap.org/wiki/Overpass_API/status this afternoon to see some news.

I was proposing z.overpass-api.de because it's second on in the pre-configured list : https://github.com/3liz/QuickOSM/blob/master/QuickOSM/definitions/overpass.py#L26

I will remove these 2 and use a single one tomorrow.

[Gustry]

A previous PR changing the list of server : https://github.com/3liz/QuickOSM/pull/173

[Gustry]

Done 9b8b58db473b402019a3d3a1264c1c8bead8f8ad

Please upgrade to 2.2.1

[mmd-osm]

I added some comments here https://wiki.openstreetmap.org/wiki/Overpass_API/status to improve the situation a bit.

[Gustry]

Thanks @mmd-osm for raising the issue on the Overpass API side. I saw that the DNS will be updated soon to forward request to new servers. From a QGIS side, we can only encourage people to upgrade their plugins.

[mmd-osm]

Meanwhile the old hostnames point to the two new servers, including proper set up of server certificates. At this point I would expect that users of older QuickOSM releases could continue using the tool as before. Avoiding hard coded server names is still recommend to avoid similar issues in the future.