Force a 404 code for tiles out of bounds

[doublebyte1]

Overview

Related Issue / discussion

#2364

Additional information

On the mvt-proxy provider, we are not sure what the behaviour of the upstream server is regarding tiles out of bounds; however, we need to make sure that if the tile is out of bounds we return a 404. This PR forces that behaviour on mvt-proxy, by evaluating if the 500 error was caused by requesting a tile outside the limits of the TMS. This also ensures that we pass the conformance test.

curl -I localhost:5000/collections/srup_arvores_point/tiles/WebMercatorQuad/0/0/100?f=pbf
HTTP/1.1 404 NOT FOUND
Server: Werkzeug/3.1.8 Python/3.12.0
Date: Fri, 19 Jun 2026 12:58:03 GMT
Content-Type: application/vnd.mapbox-vector-tile
X-Powered-By: pygeoapi 0.24.dev0
Content-Language: en-US
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: *
Content-Length: 14
Connection: close

Dependency policy (RFC2)

• I have ensured that this PR meets RFC2 requirements

Updates to public demo

• I have ensured that breaking changes to the pygeoapi master demo server have been addressed
  • https://github.com/geopython/demo.pygeoapi.io/blob/master/services/pygeoapi_master/local.config.yml

Contributions and licensing

(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)

• I'd like to contribute [feature X|bugfix Y|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution
• I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines

[tomkralidis]

Can we update to:

if resp.status_code in [404, 500]: