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

What are the processing levels and where do they belong in STAC #161

Closed
jeffnaus opened this issue Aug 14, 2018 · 11 comments
Closed

What are the processing levels and where do they belong in STAC #161

jeffnaus opened this issue Aug 14, 2018 · 11 comments

Comments

@jeffnaus
Copy link
Contributor

We should start reporting on the processing levels of our images. What are the processing levels and where should we report them. Is this one extension or is this additions to lots of extensions.

@jeffnaus
Copy link
Contributor Author

Can we get direction from the ARD group about this?

@dlindenbaum
Copy link
Contributor

As a second comment:

Should there be a processing extentension

@sjskhalsa
Copy link

a little history - processing levels for satellite data originated with CEOS, I believe, but were adopted by NASA - "To facilitate the discussion of data processing in practice, several processing levels were first defined in 1986 by NASA as part of its Earth Observing System and steadily adopted since then" (wikipedia).
https://science.nasa.gov/earth-science/earth-science-data/data-processing-levels-for-eosdis-data-products

@matthewhanson
Copy link
Collaborator

There are no standard processing levels, everyone uses different nomenclature, and I really don't think there's any way we can hope to define a standard for that providers would use.

It makes more sense to have fields that specify units, or a flag for surface reflectance or atmospheric correction, or orthorectification, but even then I'm not sure how useful that is. Only if users were searching a catalog for specific types of data.

It seems more useful to use Datasets/Collections and have a good description of what the data is rather then trying to define a new set of standards for how data has been processed.

@jeffnaus
Copy link
Contributor Author

I would go along with the idea of flags for "well know" processing steps like orthorectification and atmospheric correction and so on.

@fredliporace
Copy link
Contributor

I've drafted something on the line that @jeffnaus suggested:

https://gist.github.com/fredliporace/217d1dbd59ff1ba633ce145f04a39d55

I'm in transit now, will detail later as I reach the office.

@fredliporace
Copy link
Contributor

See #150 for related discussion

@cholmes
Copy link
Contributor

cholmes commented Aug 24, 2018

Where are we going to put this? As some attribute on the asset / asset definition?

@fredliporace
Copy link
Contributor

@cholmes I'm preparing a PR to the EO extension based on the draft above for further discussion. Note that I'll limit that to "Electro-optical" sensors, other sensors should probably have specific attributes defining their processing levels.

@m-mohr m-mohr modified the milestones: 0.6.0-RC1, 0.7.0 Oct 16, 2018
@cholmes cholmes modified the milestones: 0.7.0, 0.8.0 Apr 20, 2019
@m-mohr m-mohr removed the PR ✓ label Aug 14, 2019
@m-mohr
Copy link
Collaborator

m-mohr commented Aug 14, 2019

@matthewhanson wrote in #235:

@fredliporace I recently went to the ARD workshop this month at USGS, and this was one the things that was discussed.

It's just the start, but we've set up an ard-spec repo to start hashing out some sort of standards to describe processing as well as metrics for uncertainty.

If some standard fields come out of that effort, we can utilize those in STAC.

So I'm going to close this, feel free to post your ideas over in the ard-spec.

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

No branches or pull requests

7 participants