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
QGIS Projects are often stored in a PostGIS database. That's why it would be great if QSA could access them as well.
a possible config file could look like:
The table where the QGIS projects live must be called qgis_projects and can exist in multiple schemas. This means to reference a QGIS project one must provide the name of the project and also its schema.
The current way to call a project would not work anymore:
current way to call a project: [GET] /api/projects/<project_name>/layers
possible ways for project in different Postgres schemas:
via query param: [GET] /api/projects/<project_name>/layers?schema=<schema_name> (default should be public)
add a new param in the URL: [GET] /api/<schema_name>/projects/<project_name>/layers but this would interfere with the current way of the API ...
The text was updated successfully, but these errors were encountered:
QGIS Projects are often stored in a PostGIS database. That's why it would be great if QSA could access them as well.
a possible config file could look like:
The table where the QGIS projects live must be called
qgis_projects
and can exist in multiple schemas. This means to reference a QGIS project one must provide the name of the project and also its schema.The current way to call a project would not work anymore:
[GET] /api/projects/<project_name>/layers
[GET] /api/projects/<project_name>/layers?schema=<schema_name>
(default should bepublic
)[GET] /api/<schema_name>/projects/<project_name>/layers
but this would interfere with the current way of the API ...The text was updated successfully, but these errors were encountered: