We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
showTileBoundaries
mapbox-gl-js version: v1.4.0
v1.4.0
I might be confused over how this works but It looks like both the reported tile coordinates and boundary lines are confusing.
If I browse around #17/35.678226/139.738022 I see a boundary reporting tile coordinates at 17/58205/25807:
#17/35.678226/139.738022
17/58205/25807
But the coordinates for the tile request is actually: 17/116411/51614. So with slight rounding, values are multiplied.
17/116411/51614
https://api.mapbox.com/styles/v1/mapbox/streets-v11/tiles/512/17/116411/51614@2x?access_token={Add token here}
Should these be at parity with one another?
Here's a quick test case: https://jsfiddle.net/tristen/6f0c9qzp/
The text was updated successfully, but these errors were encountered:
@tristen this is a duplicate of #5535, and is solved by #7314 which looks like it is seeing some movement this week.
Sorry, something went wrong.
No branches or pull requests
mapbox-gl-js version:
v1.4.0
Question
I might be confused over how this works but It looks like both the reported tile coordinates and boundary lines are confusing.
If I browse around
#17/35.678226/139.738022
I see a boundary reporting tile coordinates at17/58205/25807
:But the coordinates for the tile request is actually:
17/116411/51614
. So with slight rounding, values are multiplied.https://api.mapbox.com/styles/v1/mapbox/streets-v11/tiles/512/17/116411/51614@2x?access_token={Add token here}
Should these be at parity with one another?
Links to related documentation
Here's a quick test case: https://jsfiddle.net/tristen/6f0c9qzp/
The text was updated successfully, but these errors were encountered: