bounds should be required
Open
Nobody has claimed this yet.
v3
- Dominant language
- No language data
- Stars
- 296
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
If "bounds" is missing, how do I know valid tile-x/y? If the center is also missing, I don't see any possibility to even get valid tile-xy. This problem would be solved by making the "bounds" key required instead of optional.
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 by reviewing the TileJSON specification's handling of the bounds and center keys, then check how valid tile x/y values are determined when either is absent. Done means the specification clearly defines whether bounds is required and resolves the validity question raised in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100