QGEP/QGEP#676 (comment)

role creation in setup is not documented
PUM upgrading and baseline not documented

I'm using https://github.com/QGEP/data/raw/demodata/qgep_demodata.backup
and qgis fails to open 3 tables :

Are the installation requirements in https://github.com/QGEP/docs/blob/master/en/installation-guide/requirements.rst up to date?

• Should Psycopg3 (available since 11/2021) be used instead of Psycopg2?
• Is Psycopg necessary for initial installation?
• Is model generation and thus pirogue necessary to install and run QGEP?
• Please specify between requirements for initial installation (and use) & further actions.

In the doc, 1.3 Setup Workstation, the URL for the plugin repository is still

https://raw.githubusercontent.com/QGEP/repository/master/plugins.xml

Where I think it should be

https://raw.githubusercontent.com/QGEP/qgepplugin/master/plugins.xml?qgis=3.3

No?

@m-kuhn could you please add TRIAGE rights to the @QGEP/triage group for datamodel and docs?

Example: I need to add an extra field:
Description in chapter 3.42 - Adding fields

The views can be re-generated any time using the following command:
./view/create_views.py --pg_service pg_qgep --srid 2056

I need to know;

• Where to enter the command (PG admin SQL? QGIS python line? osgeo4W shell? Python shell? On the QGIS computer? On the postgres computer?)
• What to replace ( replace pg_qgpep with your database? replace view with the custon field?

This is an issue for me in the whole documentation.

Using https://github.com/VilleDePully/qgep_sigip/blob/master/migration/audit.sql

The replay function doesn't work.

cc @ponceta

Hi, on my ubuntu 16.04 (lenovoX1 4 th gen), I can't run the virtual machine. debian startup shows and then I get a few errors and a dark screen. See attached log

VBox.log.zip

I hope that helps

usr/bin/pg_restore --host localhost --port 5432 --username "postgres" --dbname "qgep" --no-password "/home/regis/OSLANDIA/projets_locaux/QGEP/data-demodata/qgep_demodata.backup"

returns following errors:

pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 7468; 0 23690 MATERIALIZED VIEW DATA vw_network_segment postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  function st_curvetoline(public.geometry, integer) does not exist
LINE 1: SELECT ST_CurveToLine($1, 32)
               ^
HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
QUERY:  SELECT ST_CurveToLine($1, 32)
CONTEXT:  SQL function "st_curvetoline" during inlining
    Command was: REFRESH MATERIALIZED VIEW vw_network_segment;

I suppose that this is a pg_restore error replacing $1 variable by 'public.geometry' when it should be 'geometry'

Update that chapter on how to make this happen.

I was ask questions about the qgep import module and realized there is a lack of documentation about it :

• qgep_import documentation (I'll take care of it)
• qgep mobile demo project : would that be necessary since most of the users might create their own mobile project ?

Quick reminder of how it works:

• The view qgep_import.vw_manhole is used on the field to collect the data
• Back at the office, when synchronising back the data:
  1. when a manual interaction isn't necessary, the information is automatically udpated
  2. when a manual interaction is necessary, the information is hold in qgep_import.manhole_quarantine

Here is the discussion about the implementation :
QGEP/datamodel#74

@m-kuhn Can you tell what's the cycle (automatic, pseudo-automatic or manual) of doc releases to transifex?

I would like to extend a bit the Readme so that contributors know when their contributrions can be translated.

It seems that on https://github.com/qwat/docs an pseudo-automatic release of the doc to transifex (done every time a release is published) but with with no certainty.

You can use the network follwoing tool (upstream / downstream) to select a part of the network and use it as selection input for reaches and wastewater structures for the INTERLIS export - this video shows how:
https://user-images.githubusercontent.com/1265865/139002941-5822af4c-b2e8-440a-9064-afb9080cb977.mp4

To be able to install the new experimental version of the QGEP plugin set this flag in the plugin settings

I can't access to wincan2qgep translation on transifex?

A small section on how to enable / disable history on QGEP :

Example auditing tables :

SELECT qgep_sys.audit_view('qgep_od.vw_qgep_wastewater_structure', 'true'::boolean, '{}'::text[], '{obj_id}'::text[]);
SELECT qgep_sys.audit_view('qgep_od.vw_qgep_reach', 'true'::boolean, '{}'::text[], '{obj_id}'::text[]);
SELECT qgep_sys.audit_view('qgep_od.vw_cover', 'true'::boolean, '{}'::text[], '{obj_id}'::text[]);
SELECT qgep_sys.audit_view('qgep_od.vw_wastewater_node', 'true'::boolean, '{}'::text[], '{obj_id}'::text[]);

Example stop auditing tables :

qgep_sys.unaudit_table(target_table regclass)
qgep_sys.unaudit_view(target_table regclass)

As seen from https://qgep.github.io/docs/admin-guide/pgadmin/usage.html the ** there are some links to images that don't exist.

There is a small fix in #18 but the images from the 3.1.2.2. Database dump part are missing.
I checked and they never got pushed in the repo by @sjib and I cannot recover them from history.

@sjib Can you fix that part? Thanks!

I have translated the chapters 2.8.3 - 2.8.5 (how to: hydraulic modeling) into German same weeks ago, but in the Docu there is the english text. Something does not work!?

the file qgepplugin/processing_provider/qgep_swmm_commands.py has been moved to qgepplugin/swmm_templates/example_qgep_swmm_commands.py (the folder swmm is renamed swmm_templates)

see: QGEP/qgepplugin#60 (comment)

TO DO: the documentation must be updated to explain the usage of this file

Hi,

It seems that some of the videos used in the documentation are outdated, with the use of a previous version of the plugin.

https://vimeo.com/171536774

The actual projectfile has many untranslated values (e.g. in the hydraulic - vw-tables > field alias).
I think for the first version of the translation @m-kuhn did an automatic update with the values in the database. Is that much work? (manual translation is boring...)

There are also the fieldnames of vw_individual_surface missing in transifex.

I think that the captured screenshots should have width/length ratio more portrait alike mode because it would improve visualization.

Currently, the images in the generated pdf are hard to visualize unless you zoom in. If someone wants to print to print the pdf it wouldn't discern much out of the full screen screenshots.

Although this means more work as it's far easier to just make a print screen I think it's worth it.

I will try and rework all the Screenshots when I have more time but I wanted your opinion on this first.

@sjib As this issue mainly touches your work (thanks a lot for doing it) it would be nice if you could share your opinion on it.

What do you guys think?

Page: https://github.com/QGEP/docs/blob/master/en/installation-guide/workstation.rst

Install the demo project

Download https://github.com/QGEP/data/archive/demodata.zip
Extract the file
Restore the file qgep_demodata.backup with pgAdminIII
Open project/qgep_en.qgs with QGIS

New link: Download https://github.com/QGEP/datamodel/releases/latest
New Restore file: qgep_vx.x.x_structure_and_demo_data.backup

Looking through the docs I noticed there's no documentation on how to create a new datamodel.

In the documentation two links to the images are wrong and the images do not display because their ending is .JPG instead of .jpg

https://github.com/QGEP/docs/blob/master/en/qgep_swmm/Mapping.rst

I suggest to rename all files with lower case in the filename and ending: https://github.com/QGEP/docs/tree/master/en/qgep_swmm/images to avoid this kind of errors.

Once QGIS doc section is released, we should document how to use this functionnality in the water and wastewater modules context.

qgis/QGIS-Documentation#7260

Make documentation about hydraulic elements in QGEP - see for discussion and draft QGEP/QGEP#579

• Overflows (weirs, pumps) https://qgep.github.io/docs/en/user-guide/How-To/index.html#hydraulic-modeling-of-an-overflow-prank-weir-leapingweir-pump
• Volume description of bassins (with classes hydr_geometry and hydr_geom_relation (German: Hydr_Geometrie / Hydr_GeomRelation) https://qgep.github.io/docs/en/user-guide/How-To/index.html#collecting-a-hydr-geometry-corresponds-to-a-basin-geometry-in-mikeurban

• Overflow characteristics (with overflow_charc (Ueberlaufcharakteristik) and hq_relation (HQ_Relation) and hydr_char_data (Hydr_Kennwerte) - see documentation in Wegleitung GEP-Daten and https://qgep.github.io/docs/en/user-guide/How-To/index.html#overflow-characteristic
• throttle_shut_off_unit (Absperr_Drosselorgan)

Hi,
Looking at the http://qgep.github.io/docs/installation-guide/system/database-initialization.html I don't quite figure if the user is supposed to create a postgres user or group.

This is because in the privileges part there's talk about a group but we have created a user according to the documentation.

Also, for the Windows/Linux pgadmins that I tested, users don't won't show up in the Pgadmin privileges dialog, only groups.

As a solution, I can update the documentation by creating a qgepgroup group.
Have you got other suggestions?

Hi,
the VM is not working on my machine, and faced issues (next tickets) with sample database or master plugin version. I didn't find a procedure documented to install a specific release from github repositories.
Did I miss it?

As discussed with @m-kuhn

Part of the documentation should contain some quick example of the use of symbology fonctions (mainly for database migration and maintenance purposes)

Specifics :

• Activate / Deactivate symbology triggers
  SELECT qgep_sys.create_symbology_triggers()
SELECT qgep_sys.drop_symbology_triggers()

• Run symbology function for all entites.
  SELECT qgep_od.update_wastewater_structure_symbology(NULL,true)

• Run label function for all entities
  SELECT qgep_od.update_wastewater_structure_label(NULL, true)

• Run depth calculation for all entities
  SELECT qgep_od.update_depth(NULL, true);

it seems the index files are missing. will try quickly to sort it out.

@varrieta

@tudorbarascu
FYI I can't download "simply" https://docs.qtibia.ro/qgis.vdi.xz
docs.qtibia.ro uses an invalid security certificate. The certificate is only valid for the following names: gis.apavil.ro, www.gis.apavil.ro Error code: SSL_ERROR_BAD_CERT_DOMAIN

fetch http://docs.qtibia.ro/qgis.vdi.xz solve the problem

Since pum update usually requires a drop of views, it is important to reset history on views after update.

Should be mentionned somewhere, to avoid omissions.

Missing

Ref : QGEP/QGEP#394

Especially who does what.

QGEP/datamodel@74c65a8...1e02023#diff-9351824c20dc5c44cddc0e57f0249adfR1

• qgep_viewer
• qgep_user
• qgep_manager
• qgep_sysadmin

In https://github.com/QGEP/docs/tree/master/en/admin-guide

As QGEP/QGEP#524 raises many questions, I see we did not document how the labels are meant to be translated :

Modifications of the project file are available here but to be synthetic we should document :

• that labels are now generated separately on the db side in 4 different attributes
• How to translate a label
  replace(_output_label,'O',@qgep_output_prefix) with @qgep_output_prefix being a layer variable :
  
  what means users have to go to project settings and change these variables (create these if they were using an existing project )

Found for QWAT, and now for QGEP. Datamodels are both old.

TODO: move from travis to github ci

Especially for Windows

• Connect additional cover
• Pictures for wastewater structure

Add e.g. here.
https://qgep.github.io/docs/user-guide/digitizing/digitizingwastewaterstructures.html#further-attributes-and-classes

• Reshape tool merging feature - find adequate location in docu
• Splitting feature - document current workaround for splitting channels into different reaches (Kanäle unterteilen)
• Connecting catchement areas - to the catchement area digitizing section
  Add e.g. here https://qgep.github.io/docs/user-guide/editing/connect_wastewater_network_elements.html
• 2.2.3.3. Adding (for many events that can belong to many structures)
• Changing relations (Verknüpfungen ändern)
• Change ws_type (Subklasse eines Abwasserbauwerkes ändern (ObjektID ändert dann auch!))

Add to documentation - add chapter 1.3.6. to https://qgep.github.io/docs/installation-guide/workstation.html

Instructions copy from QGEP/QGEP#296

Todo, work out where translated images have to be placed.

There is no detailled description of how to manage photos / videos / documents in the TEKSI wastewater documentation

Proposal:
New chapter 3.3.5 Adding files (photos / videos / other documents) here https://qgep.github.io/docs/de/user-guide/editing/index.html.

• it's not possible to produce a PDF of the documentation (error 404) QGEP/QGEP#239
• images outside chapter: If there are many images in a chapter, sometime they are on the next page in the next chapter. E.g. Chapter 1.1.3 Setup workstation - first two images belong to 1.1.2. QGEP/QGEP#201
• Content list in QGEP.pdf is only 2 levels deep - can this be adapted to 3 or even 4 levels? QGEP/QGEP#200

Refer QGIS LTR (latest) doc when mentionning QGIS Documentation

qgis/QGIS-Documentation#7145

Before :

After :

https://qgep.github.io/docs/installation-guide/database-initialization.html

Download demo data

https://github.com/QGEP/data/raw/demodata/qgep_demodata.backup

as in

1.3.4. Install the demo project

Download https://github.com/QGEP/data/archive/demodata.zip
Extract the file
Restore the file qgep_demodata.backup with pgAdminIII
Open project/qgep_en.qgs with QGIS