Re: [QGIS-Developer] Release Cycle update

[Greg Troxel]

Marco Bernasocchi  writes:

I'm writing with my packager hat on (pkgsrc), mostly, although I'm also
a user.

> We think that adding release candidates would benefit the project a lot
> since we would not be shipping code that has not been tested at large and
> we would have a simple way to tell people that we're getting a new version
> ready and it is now time to test it heavily.

That's great.  The really hard part is getting people to test before a
release, and this will probably help.

> Release plan:
>
>- .0 packages will be called “release candidate” allowing us to improve
>expectation management and collect user feedback
>- during the .0 release candidate period, the release is first branched
>and master un-frozen to allow the next cycle development to start
>- The splash screen will include “release candidate”
>- .1 would be the first “proper” release

I don't think that naming plan is good, because it's contrary to what
everybody knows about release numbering.  3.20.0 is obviously a real
release to many, even if you say it isn't (and therefore it actually
isn't).

There's been a problem in the world of a proliferation of version
formats.  Long ago, GNU autotools had a great scheme where the release
leading up to 3.20 would be

3.19.80 alpha
3.19.81
3.19.90 beta
3.19.91

but it seems nobody uses this.  The great thing is that they sort
correctly.

The new scheme is to call

3.20a1
3.20a2
3.20b1
3.20b2
3.20b3
3.20rc1
3.20rc2

The advantage of using this is that it's really obvious (to those that
are used to release candidates in general) that rc1 is a release
candidate.  And, packaging systems have had to deal with this for
others, and using the exact same scheme means no special-case coding for
qgis.

When I can, I update pkgsrc locally to an rc (and don't publish it).
I'm doing this for two programs I'm an upstream maintainer of, and I
have often done it for postgis.  That means that I've tested the entire
source tarball to package path, and then run the package.  qgis is so
big, and I'm not as active, so I don't quite get to this.  But I think a
number of people will.

So really the only quibble I have is that if something is an RC, name it
with rcN, rather than declaring that qgis is going to use version
numbers to use what everybody else knows (without reading your
definition) mean something else.



As an aisde, a reason I would find this hard to deal with is that the
qgis data package format seems to change with every release and I've
seen the notion that e.g. if I'm working in 3.16.4 on something and I
open it with 3.20.0rc1 and change something trivial and save it, I won't
be able to open with 3.16.4.  I realize this would be hard but I would
like to see write support for the previous formats, with upgrade only
when requested.   I may be off base or out of date, in which case please
ignore me.   But I think it would be good to articulate and document how
to test new versions without messing up existing data.

Greg


signature.asc
Description: PGP signature
___
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] Release Cycle update

[Marco Bernasocchi]

Dear developers,

following up on the 3.18.0 release issue discussion [1] and my proposal
there [2], at yesterday's PSC meeting we prepared an updated release and
communication plan.

We think that adding release candidates would benefit the project a lot
since we would not be shipping code that has not been tested at large and
we would have a simple way to tell people that we're getting a new version
ready and it is now time to test it heavily.

QGIS has clearly grown a lot in the years and has become indispensable for
many users this is why we think we should do everything in our power to
deliver the best possible product.
With the addition of the release candidates in our regular release plan, we
want to take a further step in this direction and underpin the great
testing efforts driven by the community.

Unless strong objections are risen here, the new release plan beginning
with 3.20 will look like this:

Release plan:

   - .0 packages will be called “release candidate” allowing us to improve
   expectation management and collect user feedback
   - during the .0 release candidate period, the release is first branched
   and master un-frozen to allow the next cycle development to start
   - The splash screen will include “release candidate”
   - .1 would be the first “proper” release


Communication schedule:

   - .0 release → social media posts
   - .0 packages ready → “release candidate” blog post including visual
   changelog and call for testing and social media posts
   - .1 packages ready → “release” blog post and social media posts


Example with 3.20
2021-05-14

   - release of 3.16.7 (LTR)
   - release of 3.18.3
   - feature freeze in master

2021-06-18

   - release of 3.16.8 (LTR)
   - no 3.18.4 release
   - release of 3.20.0 Release candidate -> Release candidate communication
   - feature Unfreeze in master

2021-07-16

   - possibility to release a second release candidate

2021-07-16

   - release of 3.16.9 (LTR)
   - release of 3.20.1 -> Release communication

I'd like to take the opportunity to thanks everyone that gave feedback in
the above-mentioned threads thus allowing us to come up quickly with the
new schedule.

Cheers
Marco

[1] https://lists.osgeo.org/pipermail/qgis-psc/2021-February/009264.html
[2] https://lists.osgeo.org/pipermail/qgis-psc/2021-March/009293.html
-- 
Marco Bernasocchi

QGIS.org Chair
OPENGIS.ch CEO
http://berna.io
___
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] PYQGIS - OpenGL in QgsPluginLayer

[Eric Younkin - NOAA Federal]

All,

This is very useful, thanks.  The S57 driver does appear to give the layers
by names that I recognize:

INFO: Open of `C:\collab\dasktest\data_dir\13238_FFF.000'
  using driver `S57' successful.
1: DSID (None)
2: LNDARE
3: LNDELV
4: SBDARE
5: UWTROC (Point)

I've found the QML format spec here
,
but is there any guidance on starting from scratch?  Thanks again for all
the help.

Eric


On Wed, Mar 3, 2021 at 12:38 PM Martin Dobias  wrote:

> Hi Eric
>
> On Wed, Mar 3, 2021 at 5:48 PM Eric Younkin - NOAA Federal <
> eric.g.youn...@noaa.gov> wrote:
>
>> Thanks for the quick reply.  This is for NOAA nautical chart symbology,
>> following the s57/s52 spec.  You can see the symbology in the online viewer
>> here .  It
>> is basically a very complex spec that we generated for display in a
>> wxPython widget a long time ago using GDAL 1.x commands.  S57 is already an
>> existing OGR driver, although I do not know what exactly that driver does.
>> I do know that it does not somehow generate the symbology of the data for
>> you to then render.
>>
>> The vector data would be a combination of area/line/point features, and I
>> don't think it would be a fit for the Mesh layer.
>>
>> We'd like to make this symbology available in QGIS, so that users can
>> drag in a s57 file and view the chart.  You can use one of our WMS
>> services, but having the file support would be useful.  Ideally in a plugin
>> layer, so that I can also use it in our other apps that use PYQGIS 
>> QgsMapCanvas
>> widgets.
>>
>
> Thanks for more background. In this case the mesh layer indeed is not
> useful. I have not worked with S57 before, but if there is OGR driver
> available, it should be relatively easy to load and style the data without
> a plugin layer. You do not need to rely on styling provided by OGR (if
> provided at all). It looks like you only need to load the data as a bunch
> of vector layers using OGR (one for each object type) and then apply
> styling to those individual layers. Styling of vector layers in QGIS is
> fairly strong, with features like rule-based rendering, data-defined
> properties and geometry generators you can handle even very complex styles.
> After preparing individual styles for vector layers, you can save them to
> .qml files, and then your plugin would have just a simple task of taking
> the input file(s), load layers and apply saved styles.
>
> I would resort to writing a custom plugin layer only when when all other
> options fail - it is more complex, and generally the user experience is not
> great.
>
> Regards
> Martin
>
>

-- 
Eric Younkin
Physical Scientist
NOAA OCS, Hydrographic Systems and Technology Branch
1315 East-West Highway
N/CS11, Room 6604
Silver Spring, MD 20910
Office: 240-847-8208
Cell: 828-331-8197
___
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] PYQGIS - OpenGL in QgsPluginLayer

[Eric Younkin - NOAA Federal]

Hi Martin,

Thanks for the quick reply.  This is for NOAA nautical chart symbology,
following the s57/s52 spec.  You can see the symbology in the online viewer
here .  It is
basically a very complex spec that we generated for display in a wxPython
widget a long time ago using GDAL 1.x commands.  S57 is already an existing
OGR driver, although I do not know what exactly that driver does.  I do
know that it does not somehow generate the symbology of the data for you to
then render.

The vector data would be a combination of area/line/point features, and I
don't think it would be a fit for the Mesh layer.

We'd like to make this symbology available in QGIS, so that users can drag
in a s57 file and view the chart.  You can use one of our WMS services, but
having the file support would be useful.  Ideally in a plugin layer, so
that I can also use it in our other apps that use PYQGIS QgsMapCanvas
widgets.

Thanks,
Eric

On Wed, Mar 3, 2021 at 11:00 AM Martin Dobias  wrote:

> Hi Eric
>
> On Wed, Mar 3, 2021 at 3:48 PM Eric Younkin - NOAA Federal <
> eric.g.youn...@noaa.gov> wrote:
>
>> Looking for some advice.  We have a need to use OpenGL to draw the
>> symbology associated with some vector data.  All of our code uses OpenGL
>> 1.x.  I was thinking we could use the QOpenGLWidget and the QgsPluginLayer
>> to add our OpenGL rendered symbology to a QgsMapCanvas as a new layer.
>>
>> Is this possible?  Is there an example anyone knows of that is kind of
>> similar to this idea?  Or is there a better way to approach this problem?
>>
>
> Could you please provide some more details regarding the symbology you
> would like to get rendered? A screenshot would help a lot...
>
> If you plan to use mesh-based weather data, maybe what you are trying to
> do is already possible with the mesh layer in QGIS out of the box (e.g.
> display of arrows, streamlines, trace animation), or there is only small
> amount of extra work do be done in QGIS core to achieve that.
>
> As for OpenGL approach (it looks like you already have some existing code
> you would like to adapt to QGIS)... are you looking just at 2D rendering or
> 3D rendering as well? I know some time ago for QGIS 2.x Vincent Mora has
> created a plugin layer that used OpenGL to render to offscreen image and
> then draw it in map canvas [1] which involved some hacks. With
> QOpenGLWidget approach I would be quite cautious as it may not work well,
> or have some strange issues on different platforms. For example, I _think_
> the QOpenGLWidget can't be semi-transparent (but I may be wrong), so mixing
> its content with the rest of the map could be quite tricky...
>
> Regards
> Martin
>
> [1] https://github.com/Oslandia/meshlayer
>


-- 
Eric Younkin
Physical Scientist
NOAA OCS, Hydrographic Systems and Technology Branch
1315 East-West Highway
N/CS11, Room 6604
Silver Spring, MD 20910
Office: 240-847-8208
Cell: 828-331-8197
___
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] PYQGIS - OpenGL in QgsPluginLayer

[Eric Younkin - NOAA Federal]

Hello,

Looking for some advice.  We have a need to use OpenGL to draw the
symbology associated with some vector data.  All of our code uses OpenGL
1.x.  I was thinking we could use the QOpenGLWidget and the QgsPluginLayer
to add our OpenGL rendered symbology to a QgsMapCanvas as a new layer.

Is this possible?  Is there an example anyone knows of that is kind of
similar to this idea?  Or is there a better way to approach this problem?

Thanks,
Eric

-- 
Eric Younkin
Physical Scientist
NOAA OCS, Hydrographic Systems and Technology Branch
1315 East-West Highway
N/CS11, Room 6604
Silver Spring, MD 20910
Office: 240-847-8208
Cell: 828-331-8197
___
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] PYQGIS - Numpy array to QgsRasterLayer without writing to file first

[Eric Younkin - NOAA Federal]

Hi Benjamin,

This does appear to work, I am now able to use vsimem file handlers with
gdal rasters to go from numpy arrays to qgis raster layers effectively.
Very exciting, thanks for this tip!  I had another QGIS dev question, but I
will start a new thread for that.

For anyone else, this is all that I did:

dataset = gdal_driver.Create('/vsimem/imagetst.tif', cols, rows, no_bands,
gdal.GDT_Float32, creation_options)
...write array to band, set geotransform, etc

rlayer = QgsRasterLayer('/vsimem/imagetst.tif', 'imagetst', 'gdal')

Thanks again,
Eric

On Wed, Mar 3, 2021 at 12:57 AM Benjamin Jakimow <
benjamin.jaki...@geo.hu-berlin.de> wrote:

> Hi Eric,
>
> you might try to use a /vsimem/ path. For example, save your image to
> "/vsimem/myimage.tif" and
> open it as QgsRasterLayer. I haven't tested it with gdal.Datasets, but it
> works with with ogr.DataSources.
> Probably you shouldn't overwrite or delete the "/vsimem" object while QGIS
> has still a reference on it.
>
> More details here:
> https://gdal.org/user/virtual_file_systems.html#vsimem-in-memory-files
>
> Greetings,
>
> Benjamin
>
> On 2021-03-03 00:00, Eric Younkin - NOAA Federal wrote:
>
> Hello,
>
> I've been trying to figure out how to draw grids and lines from numpy
> arrays without driving to a raster/vector file first.  I tried using the
> gdal 'MEM' driver to make a gdal Dataset from a numpy array and pass that
> in as a QgsRasterLayer, I get the following:
>
> >>> memobj
>  at 0x019B3131AC30> >
> >>> QgsRasterLayer(memobj, 'testlayer', 'gdal')
> Traceback (most recent call last):
>   File "", line 1, in 
> TypeError: QgsRasterLayer(): arguments did not match any overloaded call:
>   overload 1: too many arguments
>   overload 2: argument 1 has unexpected type 'Dataset'
>
> The only other approach that I could find was:
>
>
> https://gis.stackexchange.com/questions/201804/how-to-create-raster-layer-directly-from-numpy-array-in-qgis-without-saving-to
>
> but I suspect that the return from the processing.run command is probably
> a temp file, so it is still going to file.  Is there not a way to generate
> a raster layer from a numpy array without writing to file first?
>
> Thanks,
> Eric
>
> --
> Eric Younkin
> Physical Scientist
> NOAA OCS, Hydrographic Systems and Technology Branch
> 1315 East-West Highway
> N/CS11, Room 6604
> Silver Spring, MD 20910
> Office: 240-847-8208
> Cell: 828-331-8197
>
> ___
> 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
>
>
> --
> --
> Benjamin Jakimow, Doctoral Researcher
> Earth Observation Lab | Geography Department | Humboldt-Universität zu
> Berlin
>
> e-mail: benjamin.jaki...@geo.hu-berlin.de
>
> phone:  +49 (0) 30 2093 6894
> mobile: +49 (0) 157 5656 8477
> fax:+49 (0) 30 2093 6848
> mail:   Unter den Linden 6 | 10099 Berlin | Germany
> room: 2'222
>


-- 
Eric Younkin
Physical Scientist
NOAA OCS, Hydrographic Systems and Technology Branch
1315 East-West Highway
N/CS11, Room 6604
Silver Spring, MD 20910
Office: 240-847-8208
Cell: 828-331-8197
___
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] Filter by expression in Report(s)

[Bernd Vogelgesang]

Hi Matteo,

there is already a "whishlist" from Nyall concerning Reports:

** Reports **
- Expression based filters for sections
- Expression based custom sort order for field groups
- Relation based sections (repeat section for all related features)
- Support “aggregated” geometries for headers/footers in sections
- Support for non-full page repeating sections
- Support for "expanding" content (.e.g label items which grow to fit
the available text, causing the section's size to vary
feature-by-feature) (this one continues on from the previous point)
- Reorder report sections via drag and drop
- Add user-defined notes to sections describing the logic (not
included in the outputs, only visible while designing the report)
- Copy/paste groups and sections between different reports (or for
duplicating within the same report)

(from conversation on september 16 on qgis-user) and this query on
github:
https://github.com/qgis/QGIS/issues?q=is%3Aopen+is%3Aissue+label%3AReports

Have not checked yet if there was already progress on this.

Cheers,

Bernd



On 03.03.21 17:16, matteo wrote:

Hi devs,

I think this is a feature request, but I'm unsure. In the Report
Layout when adding a layer in a "Field Group Sections" within another
"Field Group Sections", the layers must have a field in common that is
used to filter the features.

If not, one can use the "join attributes by location" or create a
virtual field with an aggregate expression.

Is there any interest to add a Expression Combobox instead of a Field
Combobox in the Report Layout to filter the features "live"?

Or is there a simpler way I'm missing? :)

Cheers and thanks

Matteo
___
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] PYQGIS - OpenGL in QgsPluginLayer

[Martin Dobias]

Hi Eric

On Wed, Mar 3, 2021 at 5:48 PM Eric Younkin - NOAA Federal <
eric.g.youn...@noaa.gov> wrote:

> Thanks for the quick reply.  This is for NOAA nautical chart symbology,
> following the s57/s52 spec.  You can see the symbology in the online viewer
> here .  It
> is basically a very complex spec that we generated for display in a
> wxPython widget a long time ago using GDAL 1.x commands.  S57 is already an
> existing OGR driver, although I do not know what exactly that driver does.
> I do know that it does not somehow generate the symbology of the data for
> you to then render.
>
> The vector data would be a combination of area/line/point features, and I
> don't think it would be a fit for the Mesh layer.
>
> We'd like to make this symbology available in QGIS, so that users can drag
> in a s57 file and view the chart.  You can use one of our WMS services, but
> having the file support would be useful.  Ideally in a plugin layer, so
> that I can also use it in our other apps that use PYQGIS QgsMapCanvas
> widgets.
>

Thanks for more background. In this case the mesh layer indeed is not
useful. I have not worked with S57 before, but if there is OGR driver
available, it should be relatively easy to load and style the data without
a plugin layer. You do not need to rely on styling provided by OGR (if
provided at all). It looks like you only need to load the data as a bunch
of vector layers using OGR (one for each object type) and then apply
styling to those individual layers. Styling of vector layers in QGIS is
fairly strong, with features like rule-based rendering, data-defined
properties and geometry generators you can handle even very complex styles.
After preparing individual styles for vector layers, you can save them to
.qml files, and then your plugin would have just a simple task of taking
the input file(s), load layers and apply saved styles.

I would resort to writing a custom plugin layer only when when all other
options fail - it is more complex, and generally the user experience is not
great.

Regards
Martin
___
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] PYQGIS - OpenGL in QgsPluginLayer

[Sébastien Peillet]

Hi Eric,

As Martin said, Vincent Mora created a plugin layer in QGIS 2.x to
render OpenGL layer. This plugin layer was designed to render a mesh
layer as it was not available yet in QGIS. So only this kind of layer
has been developped, but you should be able to use the OpenGlLayer class
to create other kind of layer. Since last year, I inherited projects
that depend of that plugin layer and migrated the meshlayer on QGIS 3.x
. I juste pushed the recent update on the gitlab.com repository
(Oslandia left the github.com one) :
https://gitlab.com/Oslandia/qgis/meshlayer

The latest update is necessary to use the meshlayer on QGIS >= 3.14 .

Regards

Sébastien

On 03/03/2021 17:48, Eric Younkin - NOAA Federal wrote:
> Hi Martin,
>
> Thanks for the quick reply.  This is for NOAA nautical chart
> symbology, following the s57/s52 spec.  You can see the symbology in
> the online viewer here
> .  It is
> basically a very complex spec that we generated for display in a
> wxPython widget a long time ago using GDAL 1.x commands.  S57 is
> already an existing OGR driver, although I do not know what exactly
> that driver does.  I do know that it does not somehow generate the
> symbology of the data for you to then render.
>
> The vector data would be a combination of area/line/point features,
> and I don't think it would be a fit for the Mesh layer.
>
> We'd like to make this symbology available in QGIS, so that users can
> drag in a s57 file and view the chart.  You can use one of our WMS
> services, but having the file support would be useful.  Ideally in a
> plugin layer, so that I can also use it in our other apps that use
> PYQGIS QgsMapCanvas widgets.
>
> Thanks,
> Eric
>
> On Wed, Mar 3, 2021 at 11:00 AM Martin Dobias  > wrote:
>
> Hi Eric
>
> On Wed, Mar 3, 2021 at 3:48 PM Eric Younkin - NOAA Federal
> mailto:eric.g.youn...@noaa.gov>> wrote:
>
> Looking for some advice.  We have a need to use OpenGL to
> draw the symbology associated with some vector data.  All of
> our code uses OpenGL 1.x.  I was thinking we could use the
> QOpenGLWidget and the QgsPluginLayer to add our OpenGL
> rendered symbology to a QgsMapCanvas as a new layer.  
>
> Is this possible?  Is there an example anyone knows of that is
> kind of similar to this idea?  Or is there a better way to
> approach this problem?
>
>
> Could you please provide some more details regarding the symbology
> you would like to get rendered? A screenshot would help a lot...
>
> If you plan to use mesh-based weather data, maybe what you are
> trying to do is already possible with the mesh layer in QGIS out
> of the box (e.g. display of arrows, streamlines, trace animation),
> or there is only small amount of extra work do be done in QGIS
> core to achieve that.
>
> As for OpenGL approach (it looks like you already have some
> existing code you would like to adapt to QGIS)... are you looking
> just at 2D rendering or 3D rendering as well? I know some time ago
> for QGIS 2.x Vincent Mora has created a plugin layer that used
> OpenGL to render to offscreen image and then draw it in map canvas
> [1] which involved some hacks. With QOpenGLWidget approach I would
> be quite cautious as it may not work well, or have some strange
> issues on different platforms. For example, I _think_ the
> QOpenGLWidget can't be semi-transparent (but I may be wrong), so
> mixing its content with the rest of the map could be quite tricky...
>
> Regards
> Martin
>
> [1] https://github.com/Oslandia/meshlayer
>
>
>
> -- 
> Eric Younkin
> Physical Scientist
> NOAA OCS, Hydrographic Systems and Technology Branch
> 1315 East-West Highway
> N/CS11, Room 6604
> Silver Spring, MD 20910
> Office: 240-847-8208
> Cell: 828-331-8197
>
> ___
> 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

-- 
Sébastien Peillet

Ingénieur développement
Oslandia
01.88.33.76.86
sebastien.peil...@oslandia.com

___
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] Filter by expression in Report(s)

[matteo]

Hi devs,

I think this is a feature request, but I'm unsure. In the Report Layout 
when adding a layer in a "Field Group Sections" within another "Field 
Group Sections", the layers must have a field in common that is used to 
filter the features.


If not, one can use the "join attributes by location" or create a 
virtual field with an aggregate expression.


Is there any interest to add a Expression Combobox instead of a Field 
Combobox in the Report Layout to filter the features "live"?


Or is there a simpler way I'm missing? :)

Cheers and thanks

Matteo
___
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] PYQGIS - OpenGL in QgsPluginLayer

[Martin Dobias]

Hi Eric

On Wed, Mar 3, 2021 at 3:48 PM Eric Younkin - NOAA Federal <
eric.g.youn...@noaa.gov> wrote:

> Looking for some advice.  We have a need to use OpenGL to draw the
> symbology associated with some vector data.  All of our code uses OpenGL
> 1.x.  I was thinking we could use the QOpenGLWidget and the QgsPluginLayer
> to add our OpenGL rendered symbology to a QgsMapCanvas as a new layer.
>
> Is this possible?  Is there an example anyone knows of that is kind of
> similar to this idea?  Or is there a better way to approach this problem?
>

Could you please provide some more details regarding the symbology you
would like to get rendered? A screenshot would help a lot...

If you plan to use mesh-based weather data, maybe what you are trying to do
is already possible with the mesh layer in QGIS out of the box (e.g.
display of arrows, streamlines, trace animation), or there is only small
amount of extra work do be done in QGIS core to achieve that.

As for OpenGL approach (it looks like you already have some existing code
you would like to adapt to QGIS)... are you looking just at 2D rendering or
3D rendering as well? I know some time ago for QGIS 2.x Vincent Mora has
created a plugin layer that used OpenGL to render to offscreen image and
then draw it in map canvas [1] which involved some hacks. With
QOpenGLWidget approach I would be quite cautious as it may not work well,
or have some strange issues on different platforms. For example, I _think_
the QOpenGLWidget can't be semi-transparent (but I may be wrong), so mixing
its content with the rest of the map could be quite tricky...

Regards
Martin

[1] https://github.com/Oslandia/meshlayer
___
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] WITH_PDAL and WITH_EPT doubt

[Alexandre Neto]

Hello again,

Does this mean that, if entwine isn't present in the system, the
compilation won't fail or complaint, but some functionality will be missing?

Should I include entwine as a dependency for 3.18.0 on conda-forge?

Thanks,
Alexandre

A quarta, 3/03/2021, 03:40, Alexandre Neto  escreveu:

> Great, thanks!
>
> A quarta, 3/03/2021, 02:03, Nyall Dawson 
> escreveu:
>
>> On Wed, 3 Mar 2021 at 11:59, Alexandre Neto 
>> wrote:
>> >
>> > Hi,
>> >
>> > I am trying to add point cloud support to QGIS on conda-forge [0], but
>> I am unsure if I need to use
>> > WITH_PDAL=TRUE
>>
>> yes, you'll need to add this even if you have pdal library available.
>> it defaults to false to avoid breaking the compilation if pdal isn't
>> available (and we want explicit breaks here rather than silently
>> compiling without pdal provider if the library isn't found).
>>
>> > and WITH_EPT=TRUE
>>
>> That defaults to true anyway, so you can omit it if you want.
>>
>> Nyall
>>
>
___
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] Voronoi tool missing from processing, what could be wrong?

[Tim Sutton]

Hi

On Wed, Mar 3, 2021 at 7:58 AM Hernán De Angelis <
variablestarli...@gmail.com> wrote:

>
> On 2021-03-03 00:12, Nyall Dawson wrote:
> > On Wed, 3 Mar 2021 at 09:10, Tim Sutton  wrote:
> >> Hi
> >>
> >> Can you check if you have python-psycopg2 installed on your system? I
> had a similar issue a month or two back which was fixed by installing it.
> (Thanks for the nudge Nyall).
> > Ah -- that was the one!  I thought it was gdal for some reason...
> > flaky memory :)
> >
> > We should really investigate why this caused a silent failure to show
> > the algorithms instead of an error...
>
> Yes, an error message could be beneficial. I remember from previous
> installations that QGIS would complain on opening that psycopg (or other
> python modules) weren't installed.
>

Yes Nyall has already taken care of it:

https://github.com/qgis/QGIS/issues/41984
https://github.com/qgis/QGIS/issues/41984

Regards

Tim

>
> /H.
>
>
>
>
> >
> > Nyall
> >
> >
> >> Regards
> >>
> >> Tim
> >>
> >> On Tue, Mar 2, 2021 at 11:19 AM Hernán De Angelis <
> variablestarli...@gmail.com> wrote:
> >>>
> >>> On 2021-03-02 10:51, Richard Duivenvoorde wrote:
>  On 3/2/21 10:41 AM, Hernán De Angelis wrote:
> > On 2021-03-02 10:21, Nyall Dawson wrote:
> >> On Tue, 2 Mar 2021 at 18:34, Hernán De Angelis
> >>  wrote:
> >>> Hi,
> >>>
> >>> I wrote about this a few days ago in the user list but I still
> have the
> >>> problem and can find neither a cause nor a solution. I thus post
> it in
> >>> this list in the hope that some developer may have a hint on what
> is
> >>> going wrong here.
> >> Double check that you have the gdal python packages installed
> > Thanks for this,
> >
> > from osgeo import gdal
> >
> > just works, so I guess it is installed.
>  What is the value of
>  BINDINGS_GLOBAL_INSTALL
>  in your compile config?
> >>> The value is "YES"
>  Looks like something is not picked up with your install.
> >>> Agree
>  What if you run qgis 31.8 from the 'output/bin' dir in your build
> directory?
> >>> Behaves just the same
>  If all fails I would (I think) compile and set CMAKE_INSTALL_PREFIX
> in some local dir in your HOME
> 
>  I did in ~/bin/qgis_/3.18/debug (for debug build):
> 
>  And create a startup script like
> 
>  export
> LD_LIBRARY_PATH=~/bin/qgis_/3.18/debug/lib/:/usr/lib/grass78/lib/
>  export PYTHONPATH=~/bin/qgis_/3.18/debug/share/qgis/python:$PYTHONPATH
>  export QGIS_DEBUG=0
>  # passing ALL parameters to qgis bin
>  # eg to be able to call a certain translation
>  # qgis --lang nl
>  ~/bin/qgis_/3.18/debug/bin/qgis "$@"
> >>> Thanks, will think about this and try it.
> >>>
> >>> Thank you again for your ansers. I see I have a sort of linking/library
> >>> problem. GRASS is installed and GRASS modules are compiled but then
> >>> these do not appear either in the menu.
> >>>
> >>>
> >>> /Hernán
> >>>
> >>>
>  Suc6
> 
>  Richard Duivenvoorde
> >>> ___
> >>> 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
> >> Visit http://kartoza.com to find out about open source:
> >>   * Desktop GIS programming services
> >>   * Geospatial web development
> >> * GIS Training
> >> * Consulting Services
> >> Tim is a member of the QGIS Project Steering Committee
> >>
> ---
> >> ___
> >> 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
>


-- 
--

Tim Sutton
Visit http://kartoza.com to find out about open source:
 * Desktop GIS programming services
 * Geospatial web development
* GIS Training
* Consulting Services
Tim is a member of the QGIS Project Steering Committee
---
___
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