search

qgis / QGIS

QGIS is a free, open source, cross platform (lin/win/mac) geographical information system (GIS)
https://qgis.org
GNU General Public License v2.0
10.49k stars 2.99k forks source link

No features are added to WCS layer due to wrong parameters in GetCoverage URL #57930

Closed tomcueue closed 2 months ago

tomcueue commented 3 months ago

What is the bug or the crash?

Since ltr 3.26, GetCoverage calls to WCS layer return an empty layer. By activating the network logger it can be seen that the GetCapabilities call functions properly, while the URL that is subsequantly generated for the GetCoverage call shows a wrong bbox (depending on QGIS version it may be 0,0,0,0 or tottally unreasonable numbers), resulting in adding to tthe canvas an empty layer. Parameters WIDTH and HEIGHT also seem to be off.

Below part of the problematic URL generated with the GetCoverage call:

ows?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&FORMAT=GeoTIFF&COVERAGE=p_bz-Elevation:DigitalTerrainModel-0.5m&BBOX=179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368,179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368,-179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368,-179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368&CRS=EPSG:25832&RESPONSE_CRS=EPSG:25832&WIDTH=6&HEIGHT=3

Steps to reproduce the issue

  1. Click on "Add WCS Layer"
  2. Connect to a WCS service
  3. Add a WCS layer to the map

Versions

QGIS version 3.36.3-Maidenhead QGIS code revision 2df96554 Qt version 5.15.13 Python version 3.12.3 GDAL/OGR version 3.9.0 PROJ version 9.4.0 EPSG Registry database version v11.004 (2024-02-24) GEOS version 3.12.1-CAPI-1.18.1 SQLite version 3.45.1 PDAL version 2.6.3 PostgreSQL client version 16.2 SpatiaLite version 5.1.0 QWT version 6.2.0 QScintilla2 version 2.14.1 OS version Windows 10 Version 2009

Active Python plugins annotationManager 0.5 batchvectorlayersaver 0.9 ClipMultipleLayers 3.2.0 ConvertLabels 0.3 ee_plugin 0.0.6 latlontools 3.6.20 mapflow 2.6.1 qfieldsync v4.9.1 QlrBrowser 3.0.0 quick_map_services 0.19.34 rivergis 3.0 VoGisProfilTool 3.0.2 db_manager 0.1.20 MetaSearch 0.3.6 processing 2.12.99

Supported QGIS version

New profile

Additional context

No response

agiudiceandrea commented 3 months ago

@tomcueue, thanks for reporting. Please try if the issue occurs also unchecking the "Extent (current: map view)" setting. May you please provide the WCS URL and the exact parameters and steps in order to replicate the issue? It seems to me the issue is the same as the one already reported at https://github.com/qgis/QGIS/issues/50432.

github-actions[bot] commented 3 months ago

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.

github-actions[bot] commented 2 months ago

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue. Or, if you have any further questions, there are also further support channels that can help you.