Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#7226 closed task (fixed)

MVT: deal better with HTTP 404 tile does not exist

Reported by: jpalmer Owned by: Even Rouault
Priority: normal Milestone: 2.3.0
Component: default Version: svn-trunk
Severity: normal Keywords: MVT
Cc:

Description

When using the new MVT driver against a TileJSON endpoint that contains extents with many missing tiles I get lots of error print out with running ogrinfo. e.g:

ogrinfo MVT:"http://localhost:32769/data/parcels/4" -oo metadata_file="http://localhost:32769/data/parcels.json" nz_primary_parcels -so

ERROR 1: HTTP error code : 404 ERROR 1: Parsing error occured at line 2881

The service is return "TIle does not exist". I'm using Tileserver-gl for testing.

The service I'm testing is in NZ with data on both sides of the anti-meridian (bounds":[-180,-52.620881,180,-29.231342]), so that's why there are so many missing tiles. See full metadata for the layer I'm testing: https://www.dropbox.com/s/987fj5kv1z0gndv/parcels.json?dl=1

Change History (2)

comment:1 by Even Rouault, 6 years ago

Resolution: fixed
Status: assignedclosed

In 41401:

MVT: improve handling of HTTP errors on missing tiles (fixes #7226)

comment:2 by jpalmer, 6 years ago

Thank you so much Even!

Cheers Jeremy

Note: See TracTickets for help on using tickets.