-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
Locate by layer shift with EPSG:3003 #1624
Comments
Still true for current release (3.4.1).
to no avail. |
My interpretation is that the |
In fact, in
|
@pcav Could this be related? qgis/QGIS#39040 |
I confirm the same problem It seem related to specific EPSG (e.g 3003 or 3004 for Italy), so I confirm it is related to towgs84 parameter. I am not sure it can be related to WMTS becuase the GetFeatureInfo is a WMS method |
I believe it is related to |
The locate by layer has been rewritten for LWC 3.8, allowing expressions and HTML layouts. @pcav @mind84 @ghmttt or @rmarzocchi84 Can you try package 3.8.1-pre if you still replicate the issue ? Is-it only on |
This issue is missing some feedbacks. 👻 |
Hi @Gustry! yep, the shift problem still standing. I think that it has nothing to do with the specific tool, as it also affects, for example You can see the shift also on this project (Lizmap 3.8.2): just click on a feature and zoom in on the features boundaries. Client side, as far as I understand, the feature geometry (yellow line) is retrieved in EPSG:4326 (geojson specs) and converted by proj4 library into the project projection POSSIBLE SOLUTION, NOT TESTED |
A shift in the geom shown by locate by layer (the yellow line in comparison with the original geom) is apparent. This happens with several servers.
See for an example:
http://95.216.241.41/index.php/view/map/?repository=castelplanio&project=prg&layers=000BFFFFFTFTTTFTT&bbox=2364771.856423%2C4817408.903284%2C2364919.891094%2C4817515.927457&crs=EPSG%3A3004&layerStyles=PRG%3Apredefinito%3Bconfine%3Adefault
search e.g. for strada VIA BATTISTI CESARE
EPSG:3004, so possibly due to different +towgs parameters
See a thread here:
https://lists.osgeo.org/pipermail/lizmap/2020-February/000059.html
QGIS 3.10, Lizmap 3.3.0
The text was updated successfully, but these errors were encountered: