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

Derived Data Traceability #13

Open
cholmes opened this issue Jun 15, 2017 · 0 comments
Open

Derived Data Traceability #13

cholmes opened this issue Jun 15, 2017 · 0 comments

Comments

@cholmes
Copy link
Contributor

cholmes commented Jun 15, 2017

One key thing to get right in cloud native geospatial is how to trace back to a 'source' image file. That could be an ortho-ed image back to its level 1 unrectified source, for those who want to apply their own DEM. It could be an NDVI analysis that derives from a source image, so users can trace back to the original. It could even be a mosaic of images, to trace back where it came from.

Doing this fully would need to be linked to metadata about the processes that are run on the data, linking a derived data set to both the source data and the parameters / process that created it.

But it might be good to add a 'source' field that can link back to where the data came from. If the image is the most raw source then it could express that in the field. It would also be good to think through caching on multiple clouds, if we use the 'source' field or another field to indicate that the image is the same.

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

1 participant