-
Notifications
You must be signed in to change notification settings - Fork 6
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
Parsing OSM tiles on WatchOS fails due to feature id overflow #45
Comments
@JeffLutzenberger Thank you for bringing this up. There are two conflicting definitions here: GeoJSON: Meaning, a GeoJSON id could be any Int, positive or negative. MVT Spec: So an Unsigned Integer in vector tiles... In the end, we need a solution that works with both:
Do you have an example URL for a OSM tile with an overflowing id? |
... and I have to admit that it was rather shortsighted of me to not handle this correctly right from the beginning... 🙄 |
it seems subtle though. I'm not 100% sure, but this might be a result of I'll see if I can get you a tile, or branch with a tile on disk that demonstrates the issue |
Here's one that fails. Parse with Ultra 2 simulator or device: |
I think it should work now with Outdooractive/mvt-tools#18 and #46, but I will test it later |
@JeffLutzenberger The new |
Testing now. Looks good so far! |
@JeffLutzenberger How is it going? Everything good so far? |
So far, so good! Thanks for the quick response and engagement on this. |
I will merge this next week if everything is working now, so that this can be closed... :-) |
It looks like integer feature ids should be explicitly cast to
UInt64
on WatchOS. I have a branch with tests for this.Gist for discussion: https://gist.github.com/JeffLutzenberger/369d3062dafb5925d9641119eef41edd
(MVT tile spec: mapbox/vector-tile-spec#94)
The text was updated successfully, but these errors were encountered: