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
Follow up on #61. Mapbox.com allows the creation and upload of features that extend W of 180dW and E of 180dE. How are these indexed?
There's definitely a search issue raised: given a bbox like 170, 5, 175, 10 should we expect to find the point [-187.5, 7.5]? Likewise, given a bbox like -190, 5, -185, 10 should we expect to find the point [187.5, 7.5]?
Should carboard normalize input features or do more splitting of its queries across the antimeridian?
The text was updated successfully, but these errors were encountered:
Conclusion: after double checking tilebelt's math (see end of https://github.com/mapbox/hey/issues/2977), I'm certain that features that go beyond the antimeridian into the shadowy "other worlds" can be found when searching the "real world." No need to fix features.
However, we do need to split search boxes at the antimeridian if we want to efficiently search for small features near it.
Follow up on #61. Mapbox.com allows the creation and upload of features that extend W of 180dW and E of 180dE. How are these indexed?
There's definitely a search issue raised: given a bbox like 170, 5, 175, 10 should we expect to find the point [-187.5, 7.5]? Likewise, given a bbox like -190, 5, -185, 10 should we expect to find the point [187.5, 7.5]?
Should carboard normalize input features or do more splitting of its queries across the antimeridian?
The text was updated successfully, but these errors were encountered: