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

Add link to stac-fields (fields.json) in best practices #1004

Closed
m-mohr opened this issue Feb 23, 2021 · 2 comments
Closed

Add link to stac-fields (fields.json) in best practices #1004

m-mohr opened this issue Feb 23, 2021 · 2 comments
Labels
minor a relatively small change to the spec
Milestone

Comments

@m-mohr
Copy link
Collaborator

m-mohr commented Feb 23, 2021

Origin: #985 (comment)

The plan is to give users a "definitive" list of fields that don't make sense to summarize and currently the list lives as fields.json in the stac-fields package (summary: true/false flag). We should add the link once stac-fields has matured a bit more and is stable.

@m-mohr m-mohr added this to the 1.0.0 milestone Feb 23, 2021
@cholmes cholmes modified the milestones: 1.0.0, 1.0.0-rc.2, 1.0.1 Mar 24, 2021
@m-mohr
Copy link
Collaborator Author

m-mohr commented Apr 1, 2021

Machine-readable normalized list from CDN:

https://cdn.jsdelivr.net/npm/@radiantearth/stac-fields@latest/fields-normalized.json

@m-mohr m-mohr added the minor a relatively small change to the spec label May 2, 2023
@m-mohr m-mohr modified the milestones: 1.0.1, 1.1 May 2, 2023
@m-mohr
Copy link
Collaborator Author

m-mohr commented May 2, 2023

I guess we don't need this in the spec anymore. Just have a look at stac-fields if needed :-)

@m-mohr m-mohr closed this as not planned Won't fix, can't repro, duplicate, stale May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor a relatively small change to the spec
Projects
None yet
Development

No branches or pull requests

2 participants