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

Webmercator anti-meridian handling #1083

Draft
wants to merge 11 commits into
base: develop-1.9
Choose a base branch
from
Draft

Conversation

SpacemanPaul
Copy link
Contributor

@SpacemanPaul SpacemanPaul commented Nov 7, 2024

Appears to be working now (barring various bugs in TerriaJS).

  1. Various docker image fixes.
  2. Use datacube>=1.9-rc11 for antimeridian extent fixes.
  3. 3857 (web-merc) requests that are closer to the antimeridian than the prime meridian are reprojected to 3832 (Pacific web-merc) internally.
  4. Auto publish 3832 if 3857 is published and 3832 isn't (as 3857 now breaks for half the world if 3832 is not published).
  5. Time-zone detection is simplified - old code was too "smart" for it's own good and ended up being crazy-wrong around the antimeridian in many cases. NB. for products that are local to the Pacific/anti-meridian region, "solar" time_resolution will always behave erratically - in this case you may find "summary" time_resolution behaves more consistently.

📚 Documentation preview 📚: https://datacube-ows--1083.org.readthedocs.build/en/1083/

@SpacemanPaul SpacemanPaul marked this pull request as draft November 7, 2024 22:47
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

Successfully merging this pull request may close these issues.

1 participant