Repository for the Open Energy Family metadata. Contains metadata templates, examples and schemas. For metadata conversion see https://github.com/OpenEnergyPlatform/omi
Most of them have a combination of tabular data format ordered in some structure, they all have apis that requiere special libraries to open but are to some degree integrated in some development environments.
Ideas of solution
I think we should consider including options in the json schema to add descriptors of these types of data, it might be necessary to add a new field that describes the library recommended to open the file (or at least refer to the specification of the file)
In cases such as NetCDF, one could also argue to include the whole oemetadata as part of the distributed files. But this offers edge cases where datasets consist of multiple netcdf can be tricky to annotate.
Description of the issue
It would be nice to have an indication on how to go about dense data formats such as:
Most of them have a combination of tabular data format ordered in some structure, they all have apis that requiere special libraries to open but are to some degree integrated in some development environments.
Ideas of solution
I think we should consider including options in the json schema to add descriptors of these types of data, it might be necessary to add a new field that describes the library recommended to open the file (or at least refer to the specification of the file)
In cases such as NetCDF, one could also argue to include the whole oemetadata as part of the distributed files. But this offers edge cases where datasets consist of multiple netcdf can be tricky to annotate.
Workflow checklist