QGIS Server for QWAT / QGEP?

[ponceta]

How do you use QGIS server with QWAT?

Same project ?

Same layers or specific views?

Editing or read only?

This would be nice to brainstorm a bit for our organisations and to be able to recommend an approach.

[haubourg]

Same layers or specific views?

From our experience, a server context, you will want to have only one point layer so that you speed up rendering a lot, we have too many layers in the project by now.
This implies to change the form logic. QGEP can be one approach (one big QGIS form with conditional tabs). Or you can set up dedicated forms and create a dedicated REST service to feed those forms.

[ponceta]

@haubourg from your experience with QGIS server : Use of conditional forms (good or bad idea?)

[haubourg]

@haubourg from your experience with QGIS server : Use of conditional forms (good or bad idea?)

You mean, reusing the qgs form automatically to generate the web client form? like Lizmap does?

I'm not sure this would be a good idea for a business application. You will look for maximum performance and ergonomy. Dealing with auto generated code, you will probably load hidden fields an ressources when the user doesn't need it. As long as we deal here with an long term application, with not so much forms, I would probably go for a REST API (see PostgRest project, might be nice), and dedicated javascript code.
In a more general GIS use case, where you want to publish easily and fast projects, I would go to contribute to QWC2 or your preferred QGIS web client so that it fully complies with QGIS forms, and remain efficient, event with 70 fields and lots of conditional logic, like we find in QGEP

Last point, QWAT is not taking profit of transaction groups, so the editing logic will remain the same as in QGIS - still we need to add the editing macros for alternative geometries.

For QGEP, well, I'm not aware transaction group editing is implemented in any web clien by now (that would be coool)