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

Create metadata document for imagery tiles, such as WMTSCapabilities document or STAC catalog entry #25

Open
robyngit opened this issue Jun 14, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@robyngit
Copy link
Member

The workflow-generated imagery layers would benefit from the addition of a metadata document to enhance their accessibility and reusability. This document could be incorporated into an ADC data package along with the tile files. It could also be used to provide instructions for map tools on how to render the data.

A few potential formats have been identified:

  1. WMTSCapabilities Document: This document offers an overview of the server capabilities and metadata about the dataset, and while Cesium doesn't seem to support it, several other significant map tools (e.g., QGIS, ESRI) do. We could potentially add our own method in MetacatUI to parse a WMTSCapabilities doc and use it the configure a layer in the map.

  2. STAC Metadata: The SpatioTemporal Asset Catalog (STAC) provides a standardized way to describe geospatial assets, which could facilitate discovery and reuse of our datasets.

We may also want to explore the potential of using other metadata formats.

The goal of this issue is to investigate metadata formats specific to geospatial assets, to decide on the most appropriate format(s) to use, and to create a mechanism that automates the creation of these metadata for future datasets.

@robyngit robyngit added the enhancement New feature or request label Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Status: No status
Development

No branches or pull requests

3 participants