id summary reporter owner description type status priority milestone component version severity resolution keywords cc 7226 MVT: deal better with HTTP 404 tile does not exist jpalmer Even Rouault "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 " task closed normal 2.3.0 default svn-trunk normal fixed MVT