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
{{ message }}
This repository was archived by the owner on Oct 13, 2025. It is now read-only.
Right now, a limited number of variables can be managed this way, mostly DB information like the table name and Bbox properties. It would be useful to manage an external source, even a CSV file, to map other information, like titles, descriptions, keywords etc... To avoid the creation of a new template every time a change emerges (like already done with CRUS https://github.com/byteroad/ogcapi-simple/blob/master/utils/template_crus.yml that changed the title from the table name to something more specific).
Putting here ideas to improve the upload script:
1) TEMPLATES
The entries in the pygeoapi config file are created starting from this YML template https://github.com/byteroad/ogcapi-simple/blob/master/utils/template_table.yml
Right now, a limited number of variables can be managed this way, mostly DB information like the table name and Bbox properties. It would be useful to manage an external source, even a CSV file, to map other information, like titles, descriptions, keywords etc... To avoid the creation of a new template every time a change emerges (like already done with CRUS https://github.com/byteroad/ogcapi-simple/blob/master/utils/template_crus.yml that changed the title from the table name to something more specific).