Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POST search requests crashing due to bbox having the same pair of coords #388

Open
ggcr opened this issue Feb 2, 2023 · 1 comment
Open

Comments

@ggcr
Copy link

ggcr commented Feb 2, 2023

This is a copy of the issue opened at Radiant Earth stac-api-spec repo.

It is not urgent but I thought it's something the developers should be aware of.

Finally I would like to point out the great performance the API has, after playing with quite a lot of APIs (some of big contributors with plenty of resources...) this is by far the best one, kudos to the dev team.


Hi everyone,

While working with the API, I tried to input as bbox parameter a "window" of 0 size, having then a pair of the same coordinates. This is making the POST request to crash.

Is this intended? If yes, I have not been able to found a parameter for a single-coordinate or kinda similar.

POST /search crashing ❌
@ https://earth-search.aws.element84.com/v0/search
// body
{
  "collections": ["sentinel-s2-l2a-cogs"],
  "bbox": [
    -110,
    39,
    -110,
    39
  ]
}

I used the hacky way of adding a little offset as a quick fix for my use case but I am sure you guys will found a better way! :)

POST /search not crashing ✅
@ https://earth-search.aws.element84.com/v0/search
// body
{
  "collections": ["sentinel-s2-l2a-cogs"],
  "bbox": [
    -110,
    39,
    -110.00001,
    39.00001
  ]
}

@philvarner
Copy link
Collaborator

Clarified with OGC API team that these degenerate bboxes should be supported. API spec will be updated soon to metion this case: radiantearth/stac-api-spec#390

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants