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

STAC API returning error when a specific field has no value #536

Closed
fangfy opened this issue Oct 6, 2023 · 0 comments · Fixed by #591
Closed

STAC API returning error when a specific field has no value #536

fangfy opened this issue Oct 6, 2023 · 0 comments · Fixed by #591
Labels

Comments

@fangfy
Copy link

fangfy commented Oct 6, 2023

STAC specification says: "No error must be returned if a specified field has no value for it in the catalog. For example, if the field "properties.eo:cloud_cover" is specified but there is no cloud cover value for an Item, a successful HTTP response must be returned and the Item entities will not contain that field.

DEAfrica user raised an issuee that a Server Error is returned when a request includes an attribte in "fields" that is not defined for a collection, e.g. curl 'https://explorer.digitalearth.africa/stac/search' -H 'content-type: application/json' --data-raw '{"limit": 10, "bbox": [-20.0, 10.0, -19.0, 11.0], "datetime": "2023-01-02T00:00:00.000001Z/2023-02-01T00:00:00Z", "collections": ["s1_rtc"], "fields": {"include": ["properties.sat:absolute_orb"]}}'
This impacts search over multiple collections that have different attributes defined.

Looks like this might relates to how the fields search is handled.

@fangfy fangfy added the stac label Oct 6, 2023
@Ariana-B Ariana-B linked a pull request Mar 5, 2024 that will close this issue
@Ariana-B Ariana-B linked a pull request Apr 12, 2024 that will close this issue
@omad omad closed this as completed in #591 Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant