Terrain (RGB-encoded DEM) datasource returns 404 for empty tiles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
**mapbox-gl-js version**: 2.0.0
**browser**: Chrome, Firefox
### Steps to Trigger Behavior
1. Use style with Terrain (RGB-encoded DEM) source and layer
2. Navigate to any sea area
### Link to Demonstration
https://jsfiddle.net/m6k791hj/6/
Coordinates are set to [0, 0], middle of the ocean, and there is of course no tiles for that region so tileset returns multiple 404.
### Expected Behavior
As claimed in the [issue](https://github.com/mapbox/mapbox-gl-js/issues/1800) tilesets should return 204 (No Content) for such cases
### Actual Behavior
404 (Not Found) is returned
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked JSFiddle and inspect the network responses while viewing the ocean coordinates [0, 0]. Compare the Terrain RGB-encoded DEM datasource behavior with the expectation in issue #1800, then determine whether the 404 is handled in mapbox-gl-js or returned by the tileset service. Done means empty terrain regions no longer produce the reported 404 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100