Map canvas Problems with coordinate transformation

Issue #572 closed
Fabian Thiel created an issue

How to reproduce:
Open Testdata --> Create a Classification with Workflow (using enmap_berlin and point vector) --> Load Classification in new Map View --> Link all Map Views --> Map View with Classification might be black --> Use Zoom to full extent in this Map View

An error has occurred while executing Python code: 

AssertionError: Unable to transform 366804.1091304348083213 5808072.34999999962747097, 401700.63086956518236548 5820672.34999999962747097 from ETRS89 / UTM zone 33N (zE-N) to WGS 84 / UTM zone 33N 
Traceback (most recent call last):
  File "C:/Users/thielf54/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\gui\mapcanvas.py", line 1193, in onExtentsChanged
    CanvasLink.applyLinking(self)
  File "C:/Users/thielf54/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\gui\mapcanvas.py", line 665, in applyLinking
    assert dstCanvas == link.apply(srcCanvas, dstCanvas)
  File "C:/Users/thielf54/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\gui\mapcanvas.py", line 724, in apply
    dstCrs.description())
AssertionError: Unable to transform 366804.1091304348083213 5808072.34999999962747097, 401700.63086956518236548 5820672.34999999962747097 from ETRS89 / UTM zone 33N (zE-N) to WGS 84 / UTM zone 33N


Python version: 3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)] 
QGIS version: 3.16.0-Hannover Hannover, 43b64b13f3 

Weird things happening here: @Andreas Janz Why does the Classification Workflow produce a raster with EPSG:5650 when Inputs are EPSG:32633

Comments (6)

  1. Benjamin Jakimow

    Wrong, but not too wrong: EPSG:5650 = ETRS89 / UTM zone 33N (zE-N), so it’s an ETRS counterpart of the WGS84 based UTM 33N

  2. Andreas Janz

    @Fabian Thiel can’t reproduce it (Windows 10, QGIS 3.14.16). My result classification is still EPSG:32633

    I will update to QGIS 3.16 and try again.

    @Benjamin Jakimow can you reproduce this?

  3. Fabian Thiel reporter

    Cannot reproduce anymore. Guess there was some metadata file also calles classification* lying around in Temp

  4. Log in to comment