Valentine Arrieta
Valentine Arrieta
I'm upgrading my qwat database using PUM from version 1.3.4 to 1.3.6 (using windows). `pum -c pum_config.yaml upgrade -p pg_dev -t qwat_sys.info -d update\delta -v int SRID 2056` All the...
Geometry_polygon for the installation layer is in 2D and can't be created using the snapping on the construction points that are 3D
This attribute is missing in the model
Tables in sys schemas used for versioning with PUM should be generalized between QGEP and QWAT. Right now: - for QGEP : `qgep_sys.pum_info` - for QWAT : `qwat_sys.info` & `qwat_sys.upgrades`
qwat_sys tables end up empty when using .sql files for database initialization I used the files _qwat_v1.3.6_structure_only.sql_ and after that _qwat_v1.3.6_value_list_data_only.sql_. The issue was reproduced by @olivierdalang
Tables in sys schemas used for versioning with PUM should be generalized between QGEP and QWAT. Right now: - for QGEP : `qgep_sys.pum_info` - for QWAT : `qwat_sys.info` & `qwat_sys.upgrades`
The wincan2qgep plugin needs to be adapted to import data coming from the wincanVx version. The idea is to use the import/export interface for VSA KEK that is being developed...
For now on, to add new data collected from the field (example: geometry, type of the structure, material, diameter, bottom_level), someone has to use an Insert SQL. It would be...
A file can be inserted only once in qgep.od_file because of the index on the fields identifier and fk_dataowner. Problem: a picture can be referenced to only one element
I tried to delete a maintenance event from the view and got that message: > ERROR: case not found > HINT: CASE statement is missing ELSE part. > CONTEXT: PL/pgSQL...