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

Clarify use of "Feature" in GeoJSON result response #327

Closed
m-mohr opened this issue Jul 20, 2020 · 1 comment
Closed

Clarify use of "Feature" in GeoJSON result response #327

m-mohr opened this issue Jul 20, 2020 · 1 comment
Assignees
Labels
documentation patch requires a patch-version (x.x.1 for example)
Milestone

Comments

@m-mohr
Copy link
Member

m-mohr commented Jul 20, 2020

A question that recently came up:

I have a doubt about the response of /jobs/{job_id}/results
the field type, can it be only Feature?
I set it to raster in my response, and the validator complains
but then it is a hard-coded value?

We need to clarify that the "Feature" is there because it's GeoJSON and only describes that the spatial reference (geometry) in the metadata is a feature, it doesn't describe what type the assets are.

cc @lforesta @bgoesswe

@m-mohr m-mohr added documentation patch requires a patch-version (x.x.1 for example) labels Jul 20, 2020
@m-mohr m-mohr added this to the v1.0.1 milestone Jul 20, 2020
@m-mohr m-mohr self-assigned this Nov 19, 2020
@m-mohr
Copy link
Member Author

m-mohr commented Nov 19, 2020

@lforesta I added the following clarification in the commit above:

        The GeoJSON type that applies to this metadata document,
        which MUST always be a "Feature" according to the STAC specification.

        This type does **not** describe the spatial data type of the assets.

Please let me know if there's anything that can still be improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation patch requires a patch-version (x.x.1 for example)
Projects
None yet
Development

No branches or pull requests

1 participant