Better maximumLevel for WebMapTileServiceImageryProvider
Open
category - terrain and imagery
type - enhancement
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
`maximumLevel` defaults to `18`, which cuts off high-resolution imagery. We can
- implement `GetCapabilities` (perhaps covered in #2362?), or
- just let requests for tiles that don't exist fail, I imagine.
Contributor guide
Research direction
Start with the WebMapTileServiceImageryProvider entry point and read issue #2362 for the proposed GetCapabilities context. Determine whether the accepted scope is capability discovery or allowing missing tiles to fail, then verify that maximumLevel no longer cuts off supported high-resolution imagery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100