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

EPSG 3857 service returning 404s #183

Open
sethjhs9 opened this issue Jul 13, 2024 · 4 comments
Open

EPSG 3857 service returning 404s #183

sethjhs9 opened this issue Jul 13, 2024 · 4 comments

Comments

@sethjhs9
Copy link

The EPSG 3857 service is returning incorrect tiles and 404 statuses. The bug is easy to see by scrolling/zooming in the NASA example: https://nasa-gibs.github.io/gibs-web-examples/examples/openlayers/webmercator-epsg3857.html

@jtroberts
Copy link
Member

This was a GIBS server issue with the EPSG3857 reprojection endpoint that was resolved over the weekend. We'll assess whether we can make improvements in the OnEarth software to prevent the issue from reoccurring.

@sethjhs9
Copy link
Author

sethjhs9 commented Mar 28, 2025 via email

@lucianpls
Copy link
Member

@jtroberts, is this due to the use of the ecache module and the disk filling up?

@jtroberts
Copy link
Member

No, it's a server startup configuration issue when GIBS scales up new instances. The EPSG3857 endpoints use the reproject servers which rely on the EPSG4326 layer configurations to determine whether the layers are time-dynamic on startup. On rare occasions, the time configurations can't be read and the EPSG3857 endpoint configures that layer as static (not time-dynamic) and will serve tiles for the default time regardless of what is provided in the time parameter. The load balancer will distribute requests between good and bad servers (causing that slicing effect). A permanent fix is being developed and isn't in place yet.

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

3 participants