geopython / geopython/pygeometa
sidecar filename conventions for multi-tabled datasets
- Dominant language
- Python
- Stars
- 127
- Forks
- 52
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
not sure if this is a relevant use case for some, but i have this issue now on some of our geopackage databases
the geopackage contains multiple tables, for which each different metadata is relevant
how can i store multiple sidecar files for a single geopackage
say foo.gpkg contains a roads and rivers table
a suggestion could be to create a foo.gpkg:roads.mcf.yml sidecar file, which seems used in gdal
alternatively, better to use the metadata conventions of geopackage itself in this scenario....
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing how pygeometa handles sidecar files and how GeoPackage table metadata can be represented; done means an agreed convention for separate metadata for tables such as roads and rivers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100