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
If I have a tile source that goes from west of Australia to east right of New Zealand, I would expect to be able to write the bounds as:
[90, -70, -170, 70] // left, bottom, right, top
Unfortunately this doesn't seem to produce a valid tilejson (in Mapbox GL JS no tiles are requested for this source).
It's not possible to workaround this by just switching the left/right longitudes, because that represents all the negative space where there is no data. Leaving the only possible workaround to specify the entire -180°/180° range:
[-180, -70, 180, 70],
This results in a lot of unnecessary requests to the server that just result in 404 responses, and also prevents the ability to draw a border around the bounds. However it works from a user perspective because all data is shown.
Extending the bounds beyond 180° to 190° (below) results in appropriate requests, but nothing between 180° and 190°(with Mapbox GL JS as the implementation).
[90, -70, 190, 70]
Should the spec be able to support bounds where the left longitude is greater than the right longitude?
The text was updated successfully, but these errors were encountered:
Thanks for the ticket @alpha-beta-soup ! Agree that enforcing bounds to 180/90 has its limitations. We’ll work on clarifying the current limitations in v3 and consider expanding beyond 180/90 for v4.
If I have a tile source that goes from west of Australia to
eastright of New Zealand, I would expect to be able to write thebounds
as:Unfortunately this doesn't seem to produce a valid tilejson (in Mapbox GL JS no tiles are requested for this source).
It's not possible to workaround this by just switching the left/right longitudes, because that represents all the negative space where there is no data. Leaving the only possible workaround to specify the entire -180°/180° range:
This results in a lot of unnecessary requests to the server that just result in 404 responses, and also prevents the ability to draw a border around the bounds. However it works from a user perspective because all data is shown.
Extending the bounds beyond 180° to 190° (below) results in appropriate requests, but nothing between 180° and 190°(with Mapbox GL JS as the implementation).
Should the spec be able to support bounds where the left longitude is greater than the right longitude?
The text was updated successfully, but these errors were encountered: