[Bug] Handling fetch requests for tiles created for irregular shapes that may not exist

[alaws-USGS]

Loader

MVTLoader

Description

I am reading in .pbf tiles to a deck.gl MVTLayer and getting an error message about unimplemented types. I reviewed the network tab in my browser and found that some of the responses had a content-type of html/text while others were application/x-protobuf. My layers were also rendering properly so I figured it was the wrong content-type that was triggering the warnings.

I found that one such request for tiles at 4/2/3 (z/x/y) was for a tile that did not exist in my server. This was due to there not being an features that would intersect with that tile and therefore a tile was not created by tippecanoe.

I am not sure if this issue is 100% within the context of loaders.gl and not deck.gl but I wanted to start here as loaders.gl is at the top of the traceback.

Expected Behavior

I would like there to be a way for MVTLoader to recognize content-types that indicate tiles do not exist and move to trying to load the next tile rather than throwing an error that litters the console. I was able to overcome this by overriding the fetch as suggested by @Pessimistress in this discussion

Steps to Reproduce

Unfortunately I am unable to share the dataset but ifsomeone did want to reproduce our workflow, the could:

1. Generate tiles for a geometry that matched the continental United States.
2. Use those tiles in an deck.gl MVTLayer and open the console to view the errors.

Environment

• Framework version: loaders.gl@4.3.3
• Browser: Edge
• Node: Node 22.15.0
• OS: Ubuntu 22.14

Logs