microsoft / microsoft/planetary-computer-apis
500 from GEOS error during spatial search
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 129
- Forks
- 33
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 1
Description
Note: This repository contains a reference implementation; as such, bugs in deployment or usage of this project in other environments besides the Microsoft Planetary Computer have no guarantees of support. See SUPPORT.md for more information.
Describe the bug
The following conditions cause a GEOS error in PostGIS:
- GET Search with bbox=100.0,0.0,0.0,105.0,1.0,1.0
- POST Search with bbox:[100.0, 0.0, 0.0, 105.0, 1.0, 1.0]
Expected behavior
A 500 should not occur.
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 with the GET and POST Search entry points using the two bbox examples, and consult SUPPORT.md for repository context. Trace where these requests reach PostGIS/GEOS and verify both forms no longer return HTTP 500. Done means the reported bounding boxes produce a non-500 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- api, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100