You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is not focused on this region, I have done the test in other countries and when touching any node osmapp brings to the screen the information corresponding to a way with the same numbering from the original node.
The text was updated successfully, but these errors were encountered:
The problem is even stranger since it only occurs when OpenFreeMap is enabled, it does not occur with MapTiler or any of the other maps.
Why can a particular layer (OpenFreeMap) generate a query error?
Thanks for the report. Yes, OpenFreeMap unfortunately encodes the ids wrong.
I should add a warning when using OFR here. I thought it would be resolved quickly as it is small change, but for some reason it had to be probably thought about more 🙂
Hi, I just noticed that OsmApp is bringing wrong information when touching a node on the screen. Example= when touching node123 it brings the info of way123.
Real example=
https://osmapp.org/#17/5.3302/-75.2873
Click on the name "Caldas" and you will see what I am trying to indicate.
This node corresponds to: https://www.openstreetmap.org/node/306394562
But osmapp brings to screen the information of:
https://www.openstreetmap.org/way/306394562
The problem is not focused on this region, I have done the test in other countries and when touching any node osmapp brings to the screen the information corresponding to a way with the same numbering from the original node.
The text was updated successfully, but these errors were encountered: