Re: [QGIS-Developer] Using QgsMapCanvas in a python plugin dialog

[Eric Brelsford]

I believe I got this working by making the mapLayers a member of the dialog
rather than a variable created in show(). For anyone who is curious or runs
into this in the future, this commit worked for me:


https://github.com/ebrelsford/qgis-map-canvas-test/commit/3bf48449aaf8430d03dad58c54a80c227c2852c1

eric

On Mon, Apr 22, 2019 at 7:42 PM Eric Brelsford  wrote:

> I'm unsuccessfully trying to use a QgsMapCanvas in a python plugin's
> dialog.
>
> The canvas renders the map, which appears and disappears the first time I
> load the dialog. The second time I load the dialog, the map is rendered and
> remains. However, I've only accomplished this by using
> waitWhileRendering(), which I know is incorrect.
>
> I have posted a minimal plugin on GitHub (
> https://github.com/ebrelsford/qgis-map-canvas-test/) demonstrating this
> issue. It was created using Plugin Builder. The relevant parts will be the
> .ui file:
>
>
> https://github.com/ebrelsford/qgis-map-canvas-test/blob/master/map_canvas_test_dialog_base.ui#L15
>
> and the dialog python file:
>
>
> https://github.com/ebrelsford/qgis-map-canvas-test/blob/master/map_canvas_test_dialog.py#L55
>
> Is anyone familiar with what I'm doing wrong here? Or does anyone know
> python plugins using QgsMapCanvas in the dialog that I could use as a
> reference? I'd appreciate any thoughts you have on it!
>
> eric
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Bug in QgsPathResolver ?

[David Marteau]

> Le 23 avr. 2019 à 23:35, Nyall Dawson  a écrit :
> 
> On Fri, 19 Apr 2019 at 23:24, David Marteau  > wrote:
>> 
>> Hi devs,
>> 
>> I have  a strange behavior with QgsPathResolver that prevent layer to be 
>> loaded if a QgsProject read config file from relative path:
>> 
>> The problem has been reduced to the following behavior (pyQgis):
>> 
>> ```
>> # Init a QgsPathResolver as with a relative path
>> pr = QgsPathResolver('./geography/data/france_parts.qgs')
> 
> Isn't this an odd/dangerous/fragile situation to begin with? I'd be in
> favour of requiring QgsPathResolver to accept only absolute paths in
> the constructor.

Hi,

That would mean that only absolute may be passed to QgsProjet::read(), why not, 
it's  a decision to make; I cannot
tell it there would be side effects or not.

but IMHO, in all case,  I think we should have explicite error/warnings and not 
end with 
meaningless path (see below) and ' unavailable layers found' errors which is 
confusing.

Regards
David,

> 
> Nyall
> 
> 
>> 
>> pr.readPath('./france_parts/france_parts.shp')
>> # Output -> '/geography/data/france_parts/france_parts.shp'
>> # Note the leading '/'
>> ```
>> 
>> Worst:
>> ```
>> pr = QgsPathResolver('../geography/data/france_parts.qgs')
>> 
>> pr.readPath('./france_parts/france_parts.shp')
>> # Output -> '/../geography/data/france_parts/france_parts.shp'
>> # which is a meaningless path
>> ```
>> 
>> The side effect is that if you do:
>> ```
>> prj = QgsProject()
>> prj.read("./geography/data/france_parts.qgs")
>> ```
>> then you get the error:
>> ```
>> 
>> Qgis OGR: Cannot open /geography/data/france_parts/france_parts.shp.()
>> Qgis : 1 unavailable layers found:
>> Qgis :  * ./france_parts/france_parts.shp
>> 
>> ```
>> 
>> This is with Qgis 3.6.1
>> 
>> Can anybody confirm that this behavior is a bug ? I will submit a PR  if 
>> this is the case.
>> Thanks,
>> 
>> Cheers
>> David
>> 
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org 
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Bug in QgsPathResolver ?

[Nyall Dawson]

On Fri, 19 Apr 2019 at 23:24, David Marteau  wrote:
>
> Hi devs,
>
> I have  a strange behavior with QgsPathResolver that prevent layer to be 
> loaded if a QgsProject read config file from relative path:
>
> The problem has been reduced to the following behavior (pyQgis):
>
> ```
> # Init a QgsPathResolver as with a relative path
> pr = QgsPathResolver('./geography/data/france_parts.qgs')

Isn't this an odd/dangerous/fragile situation to begin with? I'd be in
favour of requiring QgsPathResolver to accept only absolute paths in
the constructor.

Nyall


>
> pr.readPath('./france_parts/france_parts.shp')
> # Output -> '/geography/data/france_parts/france_parts.shp'
> # Note the leading '/'
> ```
>
> Worst:
> ```
> pr = QgsPathResolver('../geography/data/france_parts.qgs')
>
> pr.readPath('./france_parts/france_parts.shp')
> # Output -> '/../geography/data/france_parts/france_parts.shp'
> # which is a meaningless path
> ```
>
> The side effect is that if you do:
> ```
> prj = QgsProject()
> prj.read("./geography/data/france_parts.qgs")
> ```
> then you get the error:
> ```
>
> Qgis OGR: Cannot open /geography/data/france_parts/france_parts.shp.()
> Qgis : 1 unavailable layers found:
> Qgis :  * ./france_parts/france_parts.shp
>
> ```
>
> This is with Qgis 3.6.1
>
> Can anybody confirm that this behavior is a bug ? I will submit a PR  if this 
> is the case.
> Thanks,
>
> Cheers
> David
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1705] Visualist approval notification.

[noreply]

Plugin Visualist approval by pcav.
The plugin version "[1705] Visualist 0.3" is now approved
Link: http://plugins.qgis.org/plugins/visualist/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1629] GISELA Fertilizer approval notification.

[noreply]

Plugin GISELA Fertilizer approval by pcav.
The plugin version "[1629] GISELA Fertilizer 0.12 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/FertilizerMap/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1313] AGT - Archaeological Geophysics Toolbox approval notification.

[noreply]

Plugin AGT - Archaeological Geophysics Toolbox approval by pcav.
The plugin version "[1313] AGT - Archaeological Geophysics Toolbox 2.1" is now 
approved
Link: http://plugins.qgis.org/plugins/AGT/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] non-standard-library Python modules available to QGIS plugins

[Jürgen E . Fischer]

Hi Raphael,

On Tue, 23. Apr 2019 at 17:09:37 +0200, Raphael Das Gupta wrote:
> So it seems there is no authoritative source that the Debian/Ubuntu package
> definitions, OSGeo4W and the OS X installer (and all the plugin developers)
> can rely on as a common base.

Correct.


> Doesn't this lead to compatibility problems?

Yes, but the list is not set in stone - often when somebody mentions something
it will be included quickly (in osgeo4w for instance).

 
> On 23.04.19 15:11, Saber Razmjooei wrote:
> > You can find all the Python 3 modules we are packaging with macOS
> > installer here:
> > https://lutraconsulting.github.io/qgis-mac-packager/
 
> This list (under "Used Python3 modules") seems to include even more than the
> OSGeo4W one does.

It lists also secondary dependencies (eg. idna, certifi, cffi) - that will also
available for debian and osgeo4w and will be pulled in.


> I've posted a comparison of control.in vs. setup.hint vs. lutraconsulting
> installer at
> https://github.com/NixOS/nixpkgs/issues/59842#issuecomment-485832623 (Click
> "Details" in that comment to see it.)

Hm, there is stuff missing - xlrd & xlrw are also in qgis-full.


> It seems to me like currently, plugin developers have to limit themselves to
> a common subset of these if they want their plugins to be interoperable
> between different QGIS installations of the same version. Do they do that?
> Do they even know?

And do they have to?  Stuff can also be installed afterwards if necessary.  The
problem is just that there are platform differences on how that is done.


> For the time being, I think I'll use the Debian/Ubuntu dependencies as a
> guideline for NixOS, as both are Linux operating systems. For simplicity,
> I'll probably at least initially leave out PyQt5.QtWebKit though, hoping
> that no plugins actually use it.

qgis2web uses QtWebKit


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] non-standard-library Python modules available to QGIS plugins

[Raphael Das Gupta]

Thanks Jürgen and Saber for your insights!

On 23.04.19 14:53, Jürgen E. Fischer wrote:

Yes, control.in lists the dependencies that installed with the (debian) package
- and those are the only ones you can actually rely on (installing via pip
might not work everywhere and shouldn't be done anyway for packages the
distribution already can provide).

I don't know of any other documentation (except for the osgeo4w qgis-full*
setup.hint files - that are essentially the same thing [0])


Is it, though? As far as I can see that includes SciPy and Shapely, 
which the control.in file 
(https://github.com/qgis/QGIS/blob/master/debian/control.in) doesn't.




- and if there was
it would problably be old and out of sync.


So it seems there is no authoritative source that the Debian/Ubuntu 
package definitions, OSGeo4W and the OS X installer (and all the plugin 
developers) can rely on as a common base. Doesn't this lead to 
compatibility problems?


On 23.04.19 15:11, Saber Razmjooei wrote:
You can find all the Python 3 modules we are packaging with macOS 
installer here:

https://lutraconsulting.github.io/qgis-mac-packager/


This list (under "Used Python3 modules") seems to include even more than 
the OSGeo4W one does. Some of those might be build-only dependencies 
(though, are they then available at plugin runtime anyway?) or effects 
of differing packaging granularity, others are maybe indirect 
dependencies that the `*.deb` based systems (and OSGeo4W?) would pull in 
transitively, but I guess not all can be explained by that. So I'm 
pretty sure that QGIS plugins on different platforms will have a 
different set of modules available.


I've posted a comparison of control.in vs. setup.hint vs. 
lutraconsulting installer at 
https://github.com/NixOS/nixpkgs/issues/59842#issuecomment-485832623 
(Click "Details" in that comment to see it.)


It seems to me like currently, plugin developers have to limit 
themselves to a common subset of these if they want their plugins to be 
interoperable between different QGIS installations of the same version. 
Do they do that? Do they even know?


For the time being, I think I'll use the Debian/Ubuntu dependencies as a 
guideline for NixOS, as both are Linux operating systems. For 
simplicity, I'll probably at least initially leave out PyQt5.QtWebKit 
though, hoping that no plugins actually use it.


Kind regards,
Raphael

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS and GeoNode

[Tim Sutton]

Hi

> On 23 Apr 2019, at 08:19, johnrobot  wrote:
> 
> Hi
> Thanks for the reply, Tim.
> 
> We will soon be moving from QGIS 2.18 to 3.4, so the current GeoNode/QGIS
> Server solution only supporting 2.18 seems like a problem.

The main issue for 3.x support is that we need to port the ‘on the fly project’ 
creation QGIS Server plugin that makes a QGIS project for a layer on the fly so 
that we can serve it up via QGIS Server. Other than that I actually don’t think 
it is a massive amount of work to migrate everything to 3.x.

> 
> I guess it´s OK for our users to create their web maps from the web client,
> but it would be even better if they could do it without leaving QGIS.

The workflows here are more tricky since we would need to parse out QGIS 
Project layers that are not available from within the GeoNode context. I agree 
though it would be a cool feature to add.

> 
> 3D web map support is not required at the moment for us, but it could be of
> interest later on.

Yeah - for me too!


> 
> I´ll see if I can get started with the Rancher catalogue.

Great - let me know how you get on….

Regards

Tim

> 
> Regards,
> 
> Magnus
> 
> 
> 
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—









Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

I'd love to connect. Here's my calendar link  to 
make finding time easy.

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] non-standard-library Python modules available to QGIS plugins

[Saber Razmjooei]

You can find all the Python 3 modules we are packaging with macOS installer
here:
https://lutraconsulting.github.io/qgis-mac-packager/

Regards
Saber

On Tue, 23 Apr 2019, 13:54 Jürgen E. Fischer,  wrote:

> Hi Raphael,
>
> On Tue, 23. Apr 2019 at 14:41:26 +0200, Raphael Das Gupta wrote:
> > I don't quite understand. (Maybe there's just a full-stop missing in your
> > message between "are" and "It's"?) Are you saying that the dependencies
> of
> > python3-qgis are "documented" (and that they are "documented" in
> > https://github.com/qgis/QGIS/blob/master/debian/control.in#L370) or are
> you
> > saying that these dependencies actually are the "documentation" of what
> > Python modules QGIS plugins are allowed to rely on (and implying that no
> > other (or no more official) documentation/specification about that topic
> > exists)?
>
> Yes, control.in lists the dependencies that installed with the (debian)
> package
> - and those are the only ones you can actually rely on (installing via pip
> might not work everywhere and shouldn't be done anyway for packages the
> distribution already can provide).
>
> I don't know of any other documentation (except for the osgeo4w qgis-full*
> setup.hint files - that are essentially the same thing [0]) - and if there
> was
> it would problably be old and out of sync.
>
>
> Jürgen
>
> [0] http://download.osgeo.org/osgeo4w/x86_64/release/qgis/
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
> Software Engineer   D-26506 Norden
> https://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] non-standard-library Python modules available to QGIS plugins

[Jürgen E . Fischer]

Hi Raphael,

On Tue, 23. Apr 2019 at 14:41:26 +0200, Raphael Das Gupta wrote:
> I don't quite understand. (Maybe there's just a full-stop missing in your
> message between "are" and "It's"?) Are you saying that the dependencies of
> python3-qgis are "documented" (and that they are "documented" in
> https://github.com/qgis/QGIS/blob/master/debian/control.in#L370) or are you
> saying that these dependencies actually are the "documentation" of what
> Python modules QGIS plugins are allowed to rely on (and implying that no
> other (or no more official) documentation/specification about that topic
> exists)?

Yes, control.in lists the dependencies that installed with the (debian) package
- and those are the only ones you can actually rely on (installing via pip
might not work everywhere and shouldn't be done anyway for packages the
distribution already can provide).

I don't know of any other documentation (except for the osgeo4w qgis-full*
setup.hint files - that are essentially the same thing [0]) - and if there was
it would problably be old and out of sync.


Jürgen

[0] http://download.osgeo.org/osgeo4w/x86_64/release/qgis/

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] non-standard-library Python modules available to QGIS plugins

[Raphael Das Gupta]

Hi Jürgen

Thanks for the quick reply!

On 23.04.19 14:07, Jürgen E. Fischer wrote:

The dependencies of python3-qgis are It's "documented" in debian/control.in
([0]).


Jürgen


[0]https://github.com/qgis/QGIS/blob/master/debian/control.in#L370


I don't quite understand. (Maybe there's just a full-stop missing in 
your message between "are" and "It's"?) Are you saying that the 
dependencies of python3-qgis are "documented" (and that they are 
"documented" in 
https://github.com/qgis/QGIS/blob/master/debian/control.in#L370) or are 
you saying that these dependencies actually are the "documentation" of 
what Python modules QGIS plugins are allowed to rely on (and implying 
that no other (or no more official) documentation/specification about 
that topic exists)?


Kind regards,
Raphael

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] non-standard-library Python modules available to QGIS plugins

[Jürgen E . Fischer]

Hi Raphael,

On Tue, 23. Apr 2019 at 13:51:15 +0200, Raphael Das Gupta wrote:
> While one could probably determine this by looking at existing packaging
> efforts, e.g. the dependencies of Ubuntu package "python3-qgis" from
> https://qgis.org/ubuntu-ltr, I wonder whether this isn't already documented
> somewhere, as this should be of interest for both plugin authors and
> application packagers.

The dependencies of python3-qgis are It's "documented" in debian/control.in
([0]).


Jürgen


[0] https://github.com/qgis/QGIS/blob/master/debian/control.in#L370

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] non-standard-library Python modules available to QGIS plugins

[Raphael Das Gupta]

Heya all

What Python modules (beyond the "qgis" module provided by QGIS itself 
and the ones built into the Python language or included in its standard 
library) can QGIS plugins expect to be accessible?


Or asked the other way around: When packaging QGIS (e.g. for a Linux 
distribution), what Python modules do I have to make available in its 
Python, so that plugins may use it?


While one could probably determine this by looking at existing packaging 
efforts, e.g. the dependencies of Ubuntu package "python3-qgis" from 
https://qgis.org/ubuntu-ltr, I wonder whether this isn't already 
documented somewhere, as this should be of interest for both plugin 
authors and application packagers.


My context: I'm trying to improve the QGIS experience on NixOS and other 
NixPkgs-based installations and would like to do that "right" rather 
than basing my changes on guesswork. I've collected my current findings 
on https://github.com/NixOS/nixpkgs/issues/59842


Kind regards,
Raphael

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] issues with constraints(?)

[Giovanni Manghi]

Hi all,


> I have some questions on table/attributes constraints, not sure if it
> is me I don't understand how they work or if they are issues. I would
> appreciate a clarification.

no feedback, so I assume they are all bugs, see tickets links below.

cheers!

-- G --



> 1) they seem to work while adding a new feature or when updating the
> attributes using feature form that opens using the identify tool, but
> not they do not work in the table of attributes both in table view or
> form view. Is this expected?

https://issues.qgis.org/issues/21906

>
> 2) the "not null" constraint works if the attribute shows "NULL" while
> does not not if the cell is empty. While I understand the difference
> between NULL and empty, for the vast majority of users NULL=empty. Is
> this the intended behavior or is a bug? if it is the former than I
> would suggest add a "not empty" option


https://issues.qgis.org/issues/21907



> 3) I have difficulties in understand how the "expression" and
> "expression description" work: if I choose a column for the former and
> fill the latter (that is optional) with some kind of text, then when
> reopening the vector properties I find the description in the
> "expression" and the column name in the "expression description".


https://issues.qgis.org/issues/21908
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS and GeoNode

[johnrobot]

Hi
Thanks for the reply, Tim.

We will soon be moving from QGIS 2.18 to 3.4, so the current GeoNode/QGIS
Server solution only supporting 2.18 seems like a problem.

I guess it´s OK for our users to create their web maps from the web client,
but it would be even better if they could do it without leaving QGIS.

3D web map support is not required at the moment for us, but it could be of
interest later on.

I´ll see if I can get started with the Rancher catalogue.

Regards,

Magnus



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1705] Visualist approval notification.

[noreply]

Plugin Visualist approval by pcav.
The plugin version "[1705] Visualist 0.2" is now approved
Link: http://plugins.qgis.org/plugins/visualist/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1704] EDE Interpolation approval notification.

[noreply]

Plugin EDE Interpolation approval by pcav.
The plugin version "[1704] EDE Interpolation 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/ede_interpolation/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer