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

pygeoapi fails to gracefully catch missing tiles #1936

Open
webb-ben opened this issue Feb 12, 2025 · 0 comments
Open

pygeoapi fails to gracefully catch missing tiles #1936

webb-ben opened this issue Feb 12, 2025 · 0 comments
Assignees
Labels
bug Something isn't working OGC API - Tiles OGC API - Tiles
Milestone

Comments

@webb-ben
Copy link
Member

Description
Per the OGC API - TIles spec, tiles that are not found are supposed to return a 400 or 404 status. pygeoapi does this, but at the cost of logging a full error stack for every tile requested that does not exist.

Steps to Reproduce

  1. Run pygeoapi with a Tile provider and log level set to error.
  2. View tile map, in and out of where there map be tiles.
  3. View pygeoapi logs

Expected behavior
pygeoapi is able to return the proper HTTP status without spamming the logs for an expected behavior.

Screenshots/Tracebacks
500+ errors from last 15 minutes
Image

Environment

  • OS: all
  • Python version: 3.10
  • pygeoapi version: 0.20.dev0

Additional context
pygeoapi tile providers could consistently throw ProviderTileNotFoundError which can be handled in api/tiles.py to gracefully return such an error. Not sure it is wise to rely on ProviderTileNotFoundError.

@webb-ben webb-ben added bug Something isn't working OGC API - Tiles OGC API - Tiles labels Feb 12, 2025
@doublebyte1 doublebyte1 added this to the 0.21.0 milestone Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working OGC API - Tiles OGC API - Tiles
Projects
None yet
Development

No branches or pull requests

2 participants