Compatibility with QGIS3 #1075

mdouchin · 2019-02-15T10:49:46Z

This issue aims to list all the Lizmap features to check agains QGIS 3.4 which will be next LTR in the end of February 2019. I would like anyone interested to contribute to the list :

please add a comment with missing items (and I would add them in the main issue description)
please check the feature and report if there is an issue. We will open a new Github issue and reference it here when needed

Landing page

Lizmap landing page aka "Projects" page shows all the QGIS projects configured with Lizmap plugin (with a *.cfg file)

Map options

Lizmap shows the layer data in the map and respects the extent

Layer tree

The legend shows all QGIS layers
The legend tree is like the one in QGIS
The legend tree shows the embed layers
For each layer, the legend image is displayed
For each layer, the legend image respects the scale and symbology defined in QGIS
For each layer, the legend image allows to switch between different styles as defined in QGIS

Rendering

The layers are rendered in the map Only with QGIS >= 3.4.5
The layers are rendered only between the defined scales when they are set
The layers are rendered even if their projection differs from the Lizmap map display projection
The layers are rendered in the correct order based on their position in legend
The layers are rendered in the correct order based on their position in legend when the order has been changed in QGIS with the dedicated dock panel
The rendering of a group of layers is correct and respects the layers order within the group
The image type (ex: jpeg) is respected

Print

The composer layouts are shown in the print tool
The exported map respects QGIS layout
The different formats work : PDF, SVG, etc.

Popup

Popups are shown for configured layers
Popup auto mode shows the correct values, even for value relation or value list fields
Popup content respects the QGIS tooltip configuration when used, with various expressions
Popup content respects the Lizmap HTML configuration when used
Tolerance for points, lines and polygons are respected

Locate by layer

Attribute table

Selection and filter

Editing

Display an existing PgSQL feature (without geometry)
Create a PgSQL feature (without geometry)
Delete a PgSQL feature (without geometry)
Modify a PgSQL feature (without geometry)
Display an existing PgSQL feature (with geometry)
Create a PgSQL feature (with geometry)
Delete a PgSQL feature (with geometry)
Modify a PgSQL feature (with geometry)

Tooltip

Filtering data

Dataviz

Time manager

Atlas

WMS and WMTS external layers

Here is a list of contributors (not exhaustive)
@rldhont @mbernasocchi @pcav @laurentj @Gustry @slarosa @dmarteau @josemvm @nboisteault @vherreros @gerald2545 @mathieubossaert @majorxtrem @jankoja @GabrielePrestifilippo @nliaudat @jancelin @jaitor1 @jonnyforestGIS

List of available testers for early version (please tell us when and which branch is suitable for testing)
@pcav

mdouchin · 2019-02-15T11:07:20Z

@pcav @rldhont @Gustry @laurentj @dmarteau beware that we cannot edit the issue main description concurrently. Has anyone an idea of how to avoid loosing some data while another is editing the issue ? Should we only use comments to add items (and I will be in charge of copying them in the main description) or is there another preffered way ?

pcav · 2019-02-15T11:09:36Z

Sorry, I was not aware of this. Comments are OK for me, I'll refrain from direct editing. Hope nothing has been really lost.

mbernasocchi · 2019-02-15T11:50:46Z

@mdouchin great!

locate by layer seems not to work, but I'havent tested thoroughly
main.css in the default custom theme is ignored on the landing page (but I'm not sure if this is supposed to work at all)

@signedav @marioba have more feedback?

rldhont · 2019-02-18T09:03:14Z

Linked open issues:

~~The print icon disappears in QGIS 3 The print icon disappears in QGIS 3 #1100~~
~~QGIS Server 3.4.4 does not show the map anymore QGIS Server 3.4.4 does not show the map anymore #1059~~
~~child objets in popup with QGIS server 3 child objets in popup with QGIS server 3 #1024~~
~~QGIS server 3 QGIS server 3 #1018~~
~~Composer layouts not recognized at all when using QGIS3 Composer layouts not recognized at all when using QGIS3 #1007~~
~~QGIS Server 3: Can't correctly print or use the selection tool QGIS Server 3: Can't correctly print or use the selection tool #971~~
~~lizmap 3 support for QGIS 3 desktop and server lizmap 3 support for QGIS 3 desktop and server #857~~

pcav · 2019-02-25T15:23:35Z

Given that QGIS 2.18 now seems essentially unavailable from repos, I think this issue is of absolute importance.

pcav · 2019-02-25T15:55:22Z

#1059 IMHO should be closed

josemvm · 2019-02-25T22:55:43Z

attribute table not avaiable for many many layers stored in postgreSQL

rldhont · 2019-02-26T09:38:29Z

@gioman can you be more precise ? Which QGIS Server version ?

josemvm · 2019-02-26T09:53:54Z

attribute table not avaiable for many many layers stored in postgreSQL

qgis server 3.4.5

rldhont · 2019-02-26T10:28:50Z

@josemvm do you have a link to test it ?

gioman · 2019-02-26T10:37:53Z

@gioman can you be more precise ? Which QGIS Server version ?

@rldhont I'm not part of this conversation :)

rldhont · 2019-02-26T10:44:22Z

sorry @gioman

josemvm · 2019-02-26T11:04:58Z

@rldhont please check your mailbox

rldhont · 2019-02-26T11:13:10Z

@josemvm it seems there is an issue when BBOX is added to the GetFeature Request. Can you open an issue about AttributeTable with extent restriction.

josemvm · 2019-02-26T19:38:32Z

attribute table not avaiable for many many layers stored in postgreSQL

if "limitDataToBbox": "True" is set in the plugin #1084 (comment)

josemvm · 2019-02-27T10:19:36Z

edition - all the widgets are not taken by the qgis server

nboisteault · 2019-03-06T10:11:08Z

Landing page for me is ok.

nboisteault · 2019-03-06T10:34:23Z

@mbernasocchi for me locate by layer works with a QGIS 2.18 project and QGIS Server 3.4.5. We have to test with a QGIS 3.4.5 project .

josemvm · 2019-03-06T10:43:05Z

@nboisteault, qgis server 3.4.5 also prints 2.14 projects

mbernasocchi · 2019-03-06T11:08:52Z

@mbernasocchi for me locate by layer works with a QGIS 2.18 project and QGIS Server 3.4.5. We have to test with a QGIS 3.4.5 project .

@nboisteault you're right, it was a mistake on our side (PGSERVICE file missing in docker), we didn't know that lizmap does direct queries to the DB. why is that?

rldhont · 2019-03-06T11:16:32Z

@mbernasocchi lizmap is requesting directly data from Postgis instead of QGIS Server WFS GetFeature for faster request. But if lizmap cannot request Postgis, it does the WFS Request.

mbernasocchi · 2019-03-06T14:04:44Z

instead of QGIS Server WFS GetFeature for faster request.

it is what we immagined

But if lizmap cannot request Postgis, it does the WFS Request.

then this is the part that was not working for us.

nboisteault · 2019-03-06T19:45:54Z

attribute table not avaiable for many many layers stored in postgreSQL

@josemvm You said "many layers". Do you watch differences between those working and those not ?

josemvm · 2019-03-06T20:11:48Z

@nboisteault, no, the problem only happens when "limitDataToBbox": "True" is set in the lwc plugin

rmarzocchi84 · 2019-04-16T10:27:53Z

Ok @rldhont I found the PR in your repository (sorry for the previous question)

From a preliminary test it seems to work correctly.

First of all I test:

Value Map
Datetime field

I only find a strange behaviour that perhaps depends on a QGIS bug:

This value map seems not correctly defined

<Option name="map" type="Map">

and do not works:

<field name="d_origine">
      <editWidget type="ValueMap">
        <config>
          <Option type="Map">
            <Option name="map" type="Map">
              <Option name="Altro" value="5" type="QString"/>
              <Option name="Atti amministrativi" value="3" type="QString"/>
              <Option name="Palmare" value="4" type="QString"/>
              <Option name="Rilievo manuale" value="1" type="QString"/>
              <Option name="Rilievo meccanico" value="2" type="QString"/>
            </Option>
          </Option>
        </config>
      </editWidget>
    </field>

This value map is correctly defined

<Option name="map" type="List">

and works:

	<field name="d_origine">
      <editWidget type="ValueMap">
        <config>
          <Option type="Map">
            <Option name="map" type="List">
              <Option type="Map">
                <Option name="Altro" value="5" type="QString"/>
              </Option>
              <Option type="Map">
                <Option name="Atti amministrativi" value="3" type="QString"/>
              </Option>
              <Option type="Map">
                <Option name="Palmare" value="4" type="QString"/>
              </Option>
              <Option type="Map">
                <Option name="Rilievo manuale" value="1" type="QString"/>
              </Option>
              <Option type="Map">
                <Option name="Rilievo meccanico" value="2" type="QString"/>
              </Option>
            </Option>
          </Option>
        </config>
      </editWidget>
    </field>

After I test Value Relation and it do not works. This is the QGIS project definition:

    <field name="cod_strada">
      <editWidget type="ValueRelation">
        <config>
          <Option type="Map">
            <Option name="AllowMulti" value="false" type="bool"/>
            <Option name="AllowNull" value="false" type="bool"/>
            <Option name="FilterExpression" value="" type="QString"/>
            <Option name="Key" value="cod_strada" type="QString"/>
            <Option name="Layer" value="route20190320155525256" type="QString"/>
            <Option name="NofColumns" value="1" type="int"/>
            <Option name="OrderByValue" value="true" type="bool"/>
            <Option name="UseCompleter" value="true" type="bool"/>
            <Option name="Value" value="cod_strada" type="QString"/>
          </Option>
        </config>
      </editWidget>
    </field>

rldhont · 2019-04-16T10:34:14Z

Thanks for the review, I'll update the code.

nboisteault · 2019-04-16T12:52:30Z

@rldhont I tried QGIS Constraints "Not null" and "Enforce not null constraint", both didn't work and didn't show field as mandatory.

nboisteault · 2019-04-16T13:14:04Z

I have tried with QGIS 2.18 and it is the same behavior so it is not a regression but an needed enhancement.

josemvm · 2019-04-16T13:25:20Z

until now, constraints like "not null" or "default value" only could be set at the postgresql level

pcav · 2019-04-28T11:58:31Z

AFAIK version 3.2.3 should be compatible with QGIS server 3, correct? I started tessting it, and I noticed that printing is missing: is this expected?
Thanks.

Gustry · 2019-04-28T14:24:27Z

@pcav It's LWC 3.3 which will be fully compatible with QGIS 3.4, not LWC 3.2.

You should try https://github.com/3liz/lizmap-web-client/releases/tag/3.3rc1

pcav · 2019-04-28T14:28:03Z

Thanks, will do.

rldhont · 2019-04-29T12:43:33Z

@pcav you have to change the qgisServerVersion in the backoffice. If the QGIS project is a 3., to have print capabilities, the QGIS Server version has to be 3.. But the layout description is parsed in LWC 3.3.

If you have some trouble with scales: there was an issue in the plugin 3liz/lizmap-plugin#122 and a fix 3liz/lizmap-plugin#129

pcav · 2019-04-29T15:12:41Z

Thanks, I realized this too late. It would be good if somehow LM could check the QGIS version automatically, e.g. during installation, but that's obviously low priority.
Thanks a lot.

majorxtrem · 2019-07-27T13:29:46Z

"The layers are rendered in the correct order based on their position in legend when the order has been changed in QGIS with the dedicated dock panel" change 10 days ago

Is not working for me, any idea ?

Server : qgis-server 3.4.10+15buster
Lizmap : lizmap-web-client git master (on 27/07/19)
Client : Qgis 3.4.10 LTR
Qgis Plugin : lizmap 3.0.3

nboisteault · 2019-07-29T07:16:26Z

Confirmed. Debugging now.

nboisteault · 2019-08-19T08:28:32Z

@rldhont @mdouchin Does lizmap handle "Layer order" set in QGIS like in the screenshot below.

rldhont · 2019-10-13T20:46:44Z

It seems that not null constraints from QGIS Project 3 are not well detected by lizmap

rldhont · 2019-10-17T02:48:37Z

Constraint examples:

      <constraints>
        <constraint constraints="3" unique_strength="1" field="id" notnull_strength="1" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="objectid" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="commune" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="1" unique_strength="0" field="nom" notnull_strength="1" exp_strength="0"/>
        <constraint constraints="1" unique_strength="0" field="type" notnull_strength="1" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="statut" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="code_insee" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="ss_type" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="gestion" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="photo" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="valide" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="contact_te" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="courriel" notnull_strength="0" exp_strength="0"/>
        <constraint constraints="0" unique_strength="0" field="adresse" notnull_strength="0" exp_strength="0"/>
      </constraints>

laurentj · 2019-12-19T09:47:49Z

Now that the support of Qgis3 has been developed and released into lizmap 3.3, I think we should close this issue, and open new ones for new bugs related to the support of Qgis3.

pcav · 2019-12-19T09:52:01Z

+1

mdouchin added the feedback label Feb 15, 2019

mdouchin added this to the 3.3.0 milestone Feb 15, 2019

mdouchin self-assigned this Feb 15, 2019

mdouchin pinned this issue Feb 15, 2019

josemvm mentioned this issue Feb 26, 2019

attribute table - problem with bbox on getfeature request #1084

Closed

nboisteault mentioned this issue Mar 6, 2019

lizmap 3 support for QGIS 3 desktop and server #857

Closed

laurentj unpinned this issue Aug 29, 2019

laurentj pinned this issue Aug 29, 2019

nboisteault modified the milestones: 3.3.0, 3.3.1 Sep 5, 2019

rldhont mentioned this issue Oct 5, 2019

Layer order defined in QGIS Project 3 #1343

Closed

nboisteault modified the milestones: 3.3.1, 3.3.2 Oct 7, 2019

Gustry unpinned this issue Oct 31, 2019

laurentj modified the milestones: 3.3.2, 3.3.3 Nov 12, 2019

nboisteault modified the milestones: 3.3.3, 3.3.4 Dec 6, 2019

laurentj closed this as completed Jan 9, 2020

Compatibility with QGIS3 #1075

Compatibility with QGIS3 #1075

Comments

mdouchin commented Feb 15, 2019 • edited by rldhont Loading

Landing page

Map options

Layer tree

Rendering

Print

Popup

Locate by layer

Attribute table

Selection and filter

Editing

Tooltip

Filtering data

Dataviz

Time manager

Atlas

WMS and WMTS external layers

mdouchin commented Feb 15, 2019

pcav commented Feb 15, 2019

mbernasocchi commented Feb 15, 2019

rldhont commented Feb 18, 2019 • edited by nboisteault Loading

pcav commented Feb 25, 2019

pcav commented Feb 25, 2019

josemvm commented Feb 25, 2019

rldhont commented Feb 26, 2019

josemvm commented Feb 26, 2019

rldhont commented Feb 26, 2019

gioman commented Feb 26, 2019

rldhont commented Feb 26, 2019

josemvm commented Feb 26, 2019

rldhont commented Feb 26, 2019

josemvm commented Feb 26, 2019

josemvm commented Feb 27, 2019

nboisteault commented Mar 6, 2019

nboisteault commented Mar 6, 2019

josemvm commented Mar 6, 2019

mbernasocchi commented Mar 6, 2019

rldhont commented Mar 6, 2019

mbernasocchi commented Mar 6, 2019 • edited Loading

nboisteault commented Mar 6, 2019 • edited Loading

josemvm commented Mar 6, 2019 • edited Loading

rmarzocchi84 commented Apr 16, 2019 • edited Loading

rldhont commented Apr 16, 2019

nboisteault commented Apr 16, 2019 • edited Loading

nboisteault commented Apr 16, 2019

josemvm commented Apr 16, 2019

pcav commented Apr 28, 2019

Gustry commented Apr 28, 2019

pcav commented Apr 28, 2019

rldhont commented Apr 29, 2019

pcav commented Apr 29, 2019 • edited Loading

majorxtrem commented Jul 27, 2019

nboisteault commented Jul 29, 2019

nboisteault commented Aug 19, 2019

rldhont commented Oct 13, 2019

rldhont commented Oct 17, 2019

laurentj commented Dec 19, 2019

pcav commented Dec 19, 2019

mdouchin commented Feb 15, 2019 •

edited by rldhont

Loading

rldhont commented Feb 18, 2019 •

edited by nboisteault

Loading

mbernasocchi commented Mar 6, 2019 •

edited

Loading

nboisteault commented Mar 6, 2019 •

edited

Loading

josemvm commented Mar 6, 2019 •

edited

Loading

rmarzocchi84 commented Apr 16, 2019 •

edited

Loading

nboisteault commented Apr 16, 2019 •

edited

Loading

pcav commented Apr 29, 2019 •

edited

Loading