Skip to content
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

Incorrect handling of the antimeridian #41

Open
SmylerMC opened this issue Aug 9, 2021 · 0 comments
Open

Incorrect handling of the antimeridian #41

SmylerMC opened this issue Aug 9, 2021 · 0 comments

Comments

@SmylerMC
Copy link
Collaborator

SmylerMC commented Aug 9, 2021

Bug Description
Terra++ is not able to handle generating areas that cross the 180th meridian. The is mainly due to CornerBoundingBox2d not supporting bounding boxes that cross over the meridian. It always considers the "starting" longitude to be the lowest number and the "end" longitude to be the highest. This causes bounding boxes that should be [175, -175] to be [-175, 175], which results in Terra++ trying to download OSM tiles across the entire world.

To Reproduce

  1. Make a TerrainPreview centered at -16.79326,-179.99903 (a small town that's crossed by the 180th meridian, view on osm )
  2. Run TerrainPreview
  3. Force the the program to quit or wait until it has download gigabytes of data it doesn't need, and hasn't downloaded what it actually needs.

Expected behavior
There should be a way to handle those areas, maybe by splitting the bounding box in two.

Version:

  • Commit 0bf7149 (latest one on master as of writing this)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant