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

Support layer metadata register to annotate data objects/layers built from data directory #374

Open
eblondel opened this issue Nov 8, 2023 · 0 comments

Comments

@eblondel
Copy link
Collaborator

eblondel commented Nov 8, 2023

Relates to #263 on multiple data/layer support for a single entity.

By default, N data objects will be created based on the datasources found in a data directory (eg. multiple geopackages, multiple geotiff), etc. The only information available to identify each particular source is the filename, which is inherited as layername. No other metadata information is handled, eg; human description that characterizes and distinguishes each data object/layer

The objective of this development is to complement the handling of multiple data sources (through a data directory approach) with layer metadata information, through a standardized register (following the geoflow register data structure code/uri/label/definition; as CSV file) that can be made available in the data directory.

When not available, the default naming for layers / online resources will be used (as of now). When available, these additional layer metadata will be recycled to annotate the layers/online resources. This aims to provide meaninful domain description of multi layers associated with a dataset;

cc @helraynal

Sponsored by INRAE

@eblondel eblondel added this to the 1.0 milestone Nov 8, 2023
@eblondel eblondel self-assigned this Nov 8, 2023
@eblondel eblondel changed the title Support layer metadata register to annotate data objects/layers built from data direcotry Support layer metadata register to annotate data objects/layers built from data directory Nov 8, 2023
eblondel added a commit that referenced this issue Nov 9, 2023
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