microsoft / microsoft/PlanetaryComputerDataCatalog
Spatial extent invalid for mtbs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
https://planetarycomputer.microsoft.com/api/stac/v1/collections/mtbs lists two bboxes, but according to the STAC Collection spec you must list three bboxes. First the union and then all sub-bboxes.
This leads to downstream issues in the clients where the first bbox is omitted: https://mspc.lutana.de/collections/mtbs
Contributor guide
No contributing guide indexed for this repository
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 inspecting the STAC response at the mtbs collection endpoint and compare its spatial extent with the STAC Collection specification. Verify the downstream example client behavior at mspc.lutana.de/collections/mtbs; done means the collection lists the union bbox first followed by both sub-bboxes and clients retain the first bbox.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100