You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many NOAA, USAID, EPA, and even NASA EGIS data layers are served in ArcGIS Image Service/feature layer formats. Converting and loading these into the VEDA infrastructure is time-consuming and breaks provenance / data ownership.
Is there a perspective of integrating these layers from their original source into VEDA UI to be explored alongside data in the STAC/eoAPI data store?
To be clarified
What are examples of such layers?
...
Acceptance criteria
Clarified the ask
Answered the question about the feasibility
The text was updated successfully, but these errors were encountered:
Hello! I'm looking at the VEDA-UI repo and trying to understand the data structure used by VEDA. I've found a guide on nasa-impact.github.io on dataset ingestion and it appears that the VEDA uses Cloud-Optimized GeoTIFFs (COGs) format. According to the File Preparation page, a tool called rio-cogeo can be used. There appears to be a guide on creating COGs, as well. Assuming a given feature layer is of the type .tif, it should be feasible to write a script to transform the data layers into the COGs format. I'd be happy to try and make a solution for this if sample data are available!
Thanks for offering your help, @g-r-a-e-m-e - great research into our default data model, btw. 👍
This ticket is actually about the opposite - whether we can integrate data in their original format/service (some ArcGIS service), without transforming or copying the data.
So I think this ticket needs the input from someone from our team first, who can provide details about these data sources. It might also be more of a backend integration job, rather than data conversion, but we will see.
Many NOAA, USAID, EPA, and even NASA EGIS data layers are served in ArcGIS Image Service/feature layer formats. Converting and loading these into the VEDA infrastructure is time-consuming and breaks provenance / data ownership.
Is there a perspective of integrating these layers from their original source into VEDA UI to be explored alongside data in the STAC/eoAPI data store?
To be clarified
Acceptance criteria
The text was updated successfully, but these errors were encountered: