-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Wrong encoded ids for some features #44
Comments
Luckily it's a single change, OFM uses planetiler and planetiler uses this system
onthegomap/planetiler#1042 (comment) Can you open an issue in planetiler to change the system to from 123 to 124? |
Thanks @hyperknot! I added the issue here onthegomap/planetiler#1120 🤞 |
Great and really detailed issue! I'd mention that you are planning to use it for osmapp.org, which is a very impressive project! |
Hi,
we have integrated OpenFreeMap in osmapp.org, but there is an issue with type encoded in the
id
field in the MVT tiles. The last number in theid
should encode 0=node, 1=way and 4=relation.Example
16018379311
way/1601837931
, and osmapp brings us to this URL osmapp.org/way/1601837931Expected result:
In reality it is a node, so it should end with
0
. If we use the default layer Basic from Maptiler, it works correctly..
Relevant issues / related code:
Maptiler also had a long time issues with wrong encoding IDs, I believe they were using openmaptiles internally, but later switched to thier own impl (planetiler?) and that needed fixes to the id encoding too.
(same issue in indoor= stack: indoorequal/indoorequal#49)
zbycz/osmapp#771
The text was updated successfully, but these errors were encountered: