Re: [QGIS-Developer] Is it allowed to sell data in a QGIS plugin?

[Alessandro Pasotti via QGIS-Developer]

On Tue, Jun 11, 2024 at 9:44 AM Christopher Frank via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi,
>
> We have developed a QGIS plugin that requires various geospatial data. Our
> company offers the relevant geospatial data in a packed way and charges a
> few euros for it.
>
> We would like to implement in the plugin the whole order process, open
> source of course. The user will feel like shoping the data in a geoshop. To
> provide the necessary information we communicate with an api of a real
> geoshop. Before we start to implement this idea, we would like to be sure
> that this is allowed.
>
> Kind regards an thx in advance.
> Chris Steimann
>
>

As long as the plugin license is compatible with QGIS license, the source
code is available and you don't package any binaries with the plugin.
I don't see any issue with that.

Kind regards.


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] UX of Raster Legend in the QGIS Layers Panel

[Alessandro Pasotti via QGIS-Developer]

Hi Niklas,

thank you for your ideas, why don't you file an "enhancement" ticket on
github so that people can discuss it there?

Attaching a few mockups about your proposed changes would also be helpful.

Kind regards.



On Fri, Jun 7, 2024 at 9:12 AM Niklas Alt via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Dear QGIS Developers,
>
> I am a long time user, first time subscriber to this list. I am active
> though for some years within the local
> OSGeo Chapter of Germany FOSSGIS (and the QGIS user group), so some
> people on the list might be able
> to put a face on this message.
>
> I am always expressing my gratitude to the QGIS dev-community in
> personal, so let me start with a big thank you.
> I have been using QGIS for the last 10 years and our community has come
> a long way.
>
> Now to my issue: A few versions back QGIS has started to expand raster
> files with a legend, once they are
> added to the layer-panel. We are working mostly with georeferenced
> historical maps, so for the most part
> the maps are simple RGB files with transparency. And often we add dozens
> of maps which make up a city.
> Leading to long lists of expanded legends informing about the fact that
> all maps are made up of RGB color bands.
>
> Additionaly we are relying on the opacity slider, which can be added to
> the layer tree, allowing for a convenient
> way to control the opacity of the added maps. However the slider is only
> visible when the map is expanded in the layer-panel.
>
> I have posted a while back on mastodon and have added some images for
> illustrative purposes:
>
> https://fedihum.org/@oshistory/111821429135997460
>
> Perhaps the following alterations might be considered for an improved UX:
>
>   - new raster layers are collapsed by default (users who need to
> inspect the legend can toggle it)
>   - users can decided if they want the legend to  be displayed. This
> could for instance be set within the Legend
> Tab of the Layer Properties panel. In fact, there already is an
> option to use a placeholder, maybe a simple boolean
> checkbox could serve as a graphical control item
>   - maybe the legend and other UI Elements (like the mentioned opacity
> slider) could be seperated.
>
> Best Wishes,
>
> Niklas Alt, Marburg, Germany
>
>
> --
> Niklas Alt  Wiss. MA. Hessisches Institut für Landesgeschichte
> Wilhelm-Röpke-Str. 6C 35032 Marburg fon +49 (0)6421 28-91759 fax -24799
>
> Hinweise zur Verarbeitung Ihrer personenbezogenen Daten finden Sie
> unterhttps://hlgl.hessen.de/datenschutzhinweise
>
> ___
> 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
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Maintainance of QGIS Plugin repository

[Alessandro Pasotti via QGIS-Developer]

On Tue, Apr 30, 2024 at 3:41 PM Admire Nyakudya via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi All
>
> I help out in the approval process of QGIS plugins. There are various
> issues that are listed  https://github.com/qgis/QGIS-Django/issues to
> streamline the approval process of plugins.
>
> Over the years there has been a steady increase in plugins that are not
> approved . This is due to a
> number of reasons:
>
> * Duplication of functionality. Plugin functionality already exists in
> QGIS.
>
> * Plugin authors not willing to address issues raised during the approval
> process.
>
> * Plugins containing binaries (Not really sure about the policy here).
>

The policy has always been that binaries are NOT allowed.


> * Plugins which are a fork of an existing plugin and then they get renamed
> to something else without permission from the original author or the author
> is no longer interested i.e https://plugins.qgis.org/plugins/active_fire2/
> .
>
> * Old plugins that still use the old architecture i.e Python2.
>
> Could we either implement the following changes to maintain/cleanup the
> plugin repository.
>
> * Old plugins that were never approved because the author did not care to
> resolve issues flagged be deleted from the repository i.e
> https://plugins.qgis.org/plugins/ban_adresse_locator/
>
* Plugins that have vague names and offer functionality that is ambiguious
> i.e https://plugins.qgis.org/plugins/upload/ be deleted.
>
> * We could automate the deletion of plugins where feedback has been
> received but the author hasn't done any corrective measure maybe after a
> month or couple of months.
>
> * Automatically flag the plugins which are not approved to Deprecated
> after some time.
>
> I think the above and other recommendations will encourage people to use
> the plugin repository properly as currently it feels like a dumping ground.
>
>
>
Seems fair to me.


> On a side note: What is the policy for plugin names. I know it is up to
> the author to give his plugin a suitable name but something like
> https://plugins.qgis.org/plugins/transfer_layerfilegdb_to_geopackage/#plugin-versions
> looks like a description rather than a name.
>

There is no policy AFAIK except that they must be unique and valid
directory names (unix) without weird characters.

Kind regards.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Backporting qt6 sip bindings to 3.34?

[Alessandro Pasotti via QGIS-Developer]

+1

Il sab 10 feb 2024, 00:06 Nyall Dawson via QGIS-Developer <
qgis-developer@lists.osgeo.org> ha scritto:

> Hey list,
>
> What does everyone think about us backporting the python/PyQt6/ directory
> from master to the 3.34 branch? I'm thinking we could do this as
> "orphan"/unused files, with the intention that it would make backporting to
> this branch easier. Obviously it introduces a bunch of "noise" in the repo
> for this branch.
>
> Right now any change to a header which entails an accompanying change to
> the .sip files will not be backportable without merge conflicts, so eg the
> backport bot is rather gutless right now...
>
> 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
>
___
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] Qt6 builds and plugins -- ready for testing!

[Alessandro Pasotti via QGIS-Developer]

Hi Nyall,

This is great news, thank you all for the efforts.

There was a budget available for QT6 releases so I think it shouldn't
be a problem,  as long as the CI tests pass on QT6 we can make the
experimental builds available for testing.



On Wed, Feb 7, 2024 at 6:10 AM Nyall Dawson via QGIS-Developer
 wrote:
>
> On Fri, 26 Jan 2024 at 07:58, Nyall Dawson  wrote:
> >
> > Hi list,
> >
> > With some excellent work recently completed by Julien, we're now at a stage 
> > where there's no *major* roadblocks preventing plugins from functioning 
> > under the Qt6 builds!
>
> OK, given the progress made over the last couple of weeks I feel like
> we're in a position now where we could start making Qt6 based "preview
> releases" available for widespread testing.  How do we feel about
> making non-default, non-recommended Qt6 preview releases of QGIS 3.36
> publicly available? Is there any particular milestone we need to
> achieve before we should consider this?
>
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Theoretical discussion: A QGIS paid plugin marketplace? (was: sponsored plugin)

[Alessandro Pasotti via QGIS-Developer]

Hi Nyall,

Thank you for resuming this topic, I remember when I made a similar
proposal some 10 years back and I felt like it was blasphemy in the
church.

Perhaps now times are more mature and I am very much in favour of
opening the official plugin space to various forms of paid plugins.

In a previous life, I have had  a very good experience and revenue by
selling my PHP plugins on the Joomla marketplace (they maintained a
plugin listing, integrated with the Joomla CMS admin panel, plugins
were hosted elsewhere and they didn't manage the payments directly).

All the plugins I was selling were GPL or AGPL, source code was
publicly available on sourceforge/github and (to my surprise) I've
never had anyone re-selling or publishing or offering downloads of my
plugins in the wild.

The Joomla marketplace was (I don't know if it still is nowaday) IMHO
a great success story: there were many large/complex paid or freemium
plugins with a flourishing ecosystem of small/middle software houses
behind them, they typically also contributed to Joomla core
development.

So, my experience is that GPL is not a problem and people does
understand that some developers have bills to pay and children to feed
and they are generally happy to contribute to a sustainable software
ecosystem.

Cheers

On Thu, Feb 1, 2024 at 2:28 AM Nyall Dawson via QGIS-Developer
 wrote:
>
> Hi lists!
>
> I wanted to kick start a (hopefully!) civil, THEORETICAL discussion about the 
> role of a paid plugin marketplace for QGIS plugins.
>
> This has been on my mind for a while, and recently was bumped by this email 
> to the list:
>
> On Fri, 19 Jan 2024 at 19:38, gam17--- via QGIS-Developer 
>  wrote:
> >
> > Hi everyone,
> > like many of you, I have developed and maintained a plugin for many
> > years completely free of charge.
> > I have never received any donation or compensation of any kind and now I
> > would like to find a solution.
> > Has anyone already found a way to receive donations?
> > I was thinking of asking for a sponsor that would be displayed during
> > execution, for example in the window titles or through a specific menu
> > item like QGIS does (in this way the sponsor would be much less
> > visible).
>
> So again, stressing that this is a THEORETICAL discussion, I'm interested in 
> hearing people's thoughts on the potential role of a paid plugin marketplace 
> for QGIS.
>
> Here's a bullet point dump of where I'm currently sitting:
>
> - Yes, I'm aware that plugins must be GPL, and that this makes paid plugins a 
> little trickier in that they're obviously still subject to the GPL.
> - The GPL does NOT prevent charging for software, or mandate making it public 
> to non-paying customers. We could potentially have GPL plugins which are only 
> available to paid users, and only make these plugins available privately to 
> those users. YES, the GPL **DOES** mean that those paying customers can 
> redistribute the plugin publicly and freely without issue if they want (and 
> regardless of whether the original developer wants!)
> - In fact, there's already likely thousands of private, paid for plugins out 
> there! I'm talking here of plugins made specifically for internal use by one 
> organisation only. Yep, that organisation COULD make the plugin public/freely 
> available, but in many cases they are specific to that one organisation's 
> needs or contain organisation sensitive logic/data. These plugins are 
> completely compliant with the GPL, despite being private and paid for by that 
> organisation.
> - There's nothing preventing a public GPL QGIS plugin from depending on a 
> subscription based back-end, and offering zero value to anyone not paying for 
> that backend. And there's a growing number of these plugins, which depend on 
> users paying xxx large corporate entity regular high fees to access the 
> backend service. The GPL doesn't (and arguably shouldn't) prevent these large 
> entities from making money off QGIS plugins.
> - But this means that the current situation is unfairly weighted toward these 
> large entities! A one-person team making an excellent plugin and providing an 
> awesome tool for use in QGIS has a MUCH MUCH harder time finding ANY 
> financial compensation for their efforts! I don't like this situation at all, 
> and I'd say it goes against the "spirit" of why QGIS was made under the GPL 
> in the first place. The big corporate entities win, the smaller community 
> focused developers lose out. 
> - Despite the fact that a paid user could freely re-distribute a paid-for 
> plugin, there's still potential financial gain for the developer in making a 
> plugin available for a charge on a theoretical QGIS plugin marketplace.
> - The blender market is a great example of this. There's LOTS of GPL blender 
> add ons available there at charge. Eg 
> https://blendermarket.com/products/hard-ops--boxcutter-ultimate-bundle?num=2=top
>  as one example. If those numbers are accurate, that developer has 

Re: [QGIS-Developer] bare isnan -- why isn't CI catching this?

[Alessandro Pasotti via QGIS-Developer]

I think the answer is here (emphasis on "an implementation is allowed
but not required to bring those functions into the global namespace")
: 
https://stackoverflow.com/questions/18128899/is-isnan-in-the-std-namespace-more-in-general-when-is-std-necessary-optio

In other words, it should be prefixed with std::, I agree this should
be tested in CI (but I don't know how).


On Fri, Jan 26, 2024 at 3:06 PM Greg Troxel via QGIS-Developer
 wrote:
>
> I am in the process of building 3.34.3 for pkgsrc.  (We've been on 3.28.x,
> and I am just now getting to jumping to the new LTR.)
>
> I am using gcc 7.5.0 on NetBSD 10 amd64.
>
> I found a case of bare isnan in a source file.  It's easy for me to
> patch to std::isnan.  I see that there are a large number of std::isnan
> in the sources.  I am guessing that formally bare isnan is an error, but
> have not passed the bar to be a practicing C++ Language Lawyer.   I see
> an include of cmath, but not "use that scope as if here" decl.
>
> My question is:
>
>   Is it in fact invalid code to use bare isnan instead of std::isnan, vs
>   would someone claim my compiler is wrong?
>
>   Assuming bare isnan is wrong, why isn't qgis's CI catching this?  I
>   would think the CI environment should have the equivalent of
>   POSIXLY_CORRECT to try to reject as much as possible in terms of using
>   extensions not required by standards.
>
> [ 56%] Building CXX object 
> src/core/CMakeFiles/qgis_core.dir/raster/qgsrasterattributetable.cpp.o
> /tmp/work/wip/qgis/work/qgis-3.34.3/src/core/raster/qgsrasterattributetable.cpp:
>  In member function 'QgsGradientColorRamp 
> QgsRasterAttributeTable::colorRamp(QStringList&, int) const':
> /tmp/work/wip/qgis/work/qgis-3.34.3/src/core/raster/qgsrasterattributetable.cpp:1362:16:
>  error: 'isnan' was not declared in this scope; did you mean 'std::isnan'?
>  1362 | if ( ! isnan( min ) && ! isnan( max ) )
>   |^
>   |std::isnan
> In file included from /tmp/work/wip/qgis/work/qgis-3.34.3/src/core/qgis.h:25,
>  from 
> /tmp/work/wip/qgis/work/qgis-3.34.3/src/core/qgsfield.h:25,
>  from 
> /tmp/work/wip/qgis/work/qgis-3.34.3/src/core/qgsfields.h:22,
>  from 
> /tmp/work/wip/qgis/work/qgis-3.34.3/src/core/raster/qgsrasterattributetable.h:19,
>  from 
> /tmp/work/wip/qgis/work/qgis-3.34.3/src/core/raster/qgsrasterattributetable.cpp:17:
> /usr/include/g++/cmath:632:5: note: 'std::isnan' declared here
>   632 | isnan(_Tp __x)
>   | ^
> gmake[2]: *** [src/core/CMakeFiles/qgis_core.dir/build.make:10842: 
> src/core/CMakeFiles/qgis_core.dir/raster/qgsrasterattributetable.cpp.o] Error 
> 1
> gmake[2]: Target 'src/core/CMakeFiles/qgis_core.dir/build' not remade because 
> of errors.
> gmake[1]: *** [CMakeFiles/Makefile2:4912: 
> src/core/CMakeFiles/qgis_core.dir/all] Error 2
> gmake[1]: Target 'all' not remade because of errors.
> gmake: *** [Makefile:166: all] Error 2
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] plugins: pip dependecies

[Alessandro Pasotti via QGIS-Developer]

Hi Martin,

plugin dependencies are for plugin dependent on other plugins, it has
nothing to do with python packages.

See:
https://docs.qgis.org/3.28/en/docs/pyqgis_developer_cookbook/plugins/plugins.html#metadata-txt



On Fri, Jan 26, 2024 at 11:29 AM Martin Landa via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi,
>
> I would like to ask regarding QGIS plugin publishing which has pip
> dependency.
>
> In metadata.txt I added:
>
> plugin_dependencies=smoderp2d
>
> When trying to install a plugin from ZIP created by pb_tool unfortunately
> smoderp2d dependency is not installed. The Plugin Dependencies Manager is
> shown, the dialog just hangs with Action -> Fix manually. No error message
> is displayed.
>
> [image: image.png]
>
> How can I fix this issue? Thanks in advance for your help. Regards, Martin
>
> PS: I tried to install smodep2d manually by pip and it worked fine.
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
> ___
> 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
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Strange Mysql (spatial) behaviour: no points visible

[Alessandro Pasotti via QGIS-Developer]

Hi Richard,

sorry, no hints except to check the logs and the QGIS dev tools query
logger: is there anything suspicious?

On Tue, Jan 16, 2024 at 8:08 PM Richard Duivenvoorde via
QGIS-Developer  wrote:
>
> No hints :-) ?
>
> I now have a live connection to the db, and can reproduce the issue here in 
> master on Linux too.
>
> It's really strange: have a local db, I can even copy features from the 
> attribute table to my local table, and THEN they show up
>
> ogrinfo shows exactly the same information of the db ( using -so).
>
> coordinates are fine too:
>
> select coord, ST_AsWKT(coord) from tblQgisProjecten tqp limit 1
>
> coord|ST_AsWKT(coord) 
> |
> -++
> POINT (168937.186906043 175180.302889316)|POINT(168937.186906043 
> 175180.302889316)|
>
> could it be in char encoding, or in a strange attribute value? We already 
> tried to create a simple view with only coord and ID, but that did not show 
> something either.
>
> As I cannot share the connection info, I'm happy to share my screen or so to 
> show this.
>
> SELECT version();
> version()|
> -+
> 8.0.34-26|
>
> but is an upgraded db, not sure where it came from
>
> Regards,
>
> Richard Duivenvoorde
>
>
> On 1/12/24 15:06, Richard Duivenvoorde via QGIS-Developer wrote:
> > Hi Devs,
> >
> > I was contacted by a company who after upgrading their db and QGIS did NOT 
> > see the points anymore.
> >
> > Note that 'all worked' when they used QGIS 3.10 (and an older mysql db)
> > After a MySQL database upgrade, QGIS 3.10 was not able to connect anymore 
> > (apparently TLS issues), so they have to use 3.28 or higher.
> >
> > A small export loaded in my local db was OK in QGIS.
> >
> > So in a online meeting, sharing their screen I tried:
> >
> > - opening the db with ogrinfo: all data is visible (POINT(.)) showing 
> > correct coords and attributes
> > - loading the table (25000 records) in QGIS: data: EPSG:31370 project 
> > EPSG:31370 :
> >  - attribute table shows all records
> >  - mapcanvas empty!
> >  - able to 'zoom to' records (Belgium), but NO points visible/selectable
> > - creating a tiny table with only id and geom column of 3 records: 
> > mapcanvas emtpy
> > - export the loaded (but invisible) layer to a geopackage: points AND 
> > attributes VISIBLE!
> > - loading the data in dbeaver: all data is shown in the spatial tab
> >
> > There was an encoding issue when exporting to gpkg, but we tried to create 
> > a smaller table (very few columns): nothing.
> >
> > Anybody familiar with QGIS and Mysql has an idea what this not showing of 
> > any point/geom could be?
> >
> > Any hint appreciated, I plan to try to get a connection to the db myself, 
> > but hoping I just miss something obvious...
> >
> > Regards,
> >
> > 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
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS - QT6 Build Status Report

[Alessandro Pasotti via QGIS-Developer]

Hi,

as you probably know during the developers meeting in s-Hertogenbosch
it was decided to allocate a budget for developers that wanted to
dedicate some time to remove the blockers that prevented QGIS to be
eventually migrated to QT6.

I volunteered to coordinate the effort and organized a few meetings to
track the advancement of the efforts.

The good news is that thanks to the efforts and the brilliant work of
the participants we now have made significant steps towards the goal.

Here are the last QT6 meeting minutes:

https://docs.google.com/document/d/1D9X3pMXJgB1pIs2sFX5O22-TJEmLYuA4ujYis7EGXpE

Kind regards.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Regular paid positions for PR reviews

[Alessandro Pasotti via QGIS-Developer]

On Fri, Dec 8, 2023 at 9:22 AM Andreas Neumann  wrote:
>
> Dear Alex,
>
> I support this idea. Code reviews are important.
>
> But I think we already do that - don't we? In 2023 there was this 14k € 
> budget that is currently being distributed between the core devs who are 
> actively reviewing on Github. Next year, we plan to increase this budget to 
> 20k.
>
> Are we missing anything?

I think the idea was to go from voluntary random PR review
contributions to a regular commitment we can count upon.

>
> I am not sure if it is useful to dedicate an "exact" number of hours and a 
> fixed rate. I'd rather have a fixed annual budget (like we already have) and 
> distribute this among the core devs who actively participate in the reviews 
> and discussions.

That's exactly the point, some of us think it would be better the other way.

>
> We can formalize this a bit better if you want. I am open for suggestions how 
> to improve the situation.
>
> Another idea is to merge the budgets for bug fixing and code reviewing - then 
> the "approved" core devs can spend their hours on both bug fixing and 
> reviewing and invoice everything together.

No, I would say we keep it separate, I agree that during the
bug-fixing time the participants can spend their time doing both
bugfixing and PR reviews provided that the reviews are oriented to bug
fixing/chores and not to new features.

>
> It is a really good timing to discuss this now - because we want to bring the 
> 2024 budget to vote next week.

I look forward to other developers' opinions.

Kind regards.

>
> Greetings,
> Andreas
>
> On Fri, 8 Dec 2023 at 08:57, Alessandro Pasotti via QGIS-Developer 
>  wrote:
>>
>> Hi,
>>
>> Recently I have had the opportunity to discuss with some core QGIS
>> developers and we agreed that it would be a good idea if the QGIS
>> organization could fund a few weekly or monthly hours for PR reviews.
>>
>> Here is my quick and initial proposal of requisites for the candidates:
>>
>> - must be an active well known and long time QGIS C++ core developer
>> (for example from the top last 5 years committers [1])
>> - ideally we'd need more than a single developer: there is not a
>> single developer who is able to review all different areas of the code
>> base
>> - available for regular work (fixed number of weekly or monthly hours,
>> to be determined)
>>
>> Note: the above list is just my quick ideas, feel free to suggest
>> anything you think best.
>>
>>  I would like this topic to be added to the next PSC meeting agenda.
>>
>> Kind regards.
>>
>>
>> [1] 
>> https://github.com/qgis/QGIS/graphs/contributors?from=2018-12-08=2023-12-08=c
>>
>> --
>> Alessandro Pasotti
>> QCooperative:  www.qcooperative.net
>> ItOpen:   www.itopen.it
>> ___
>> 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
>
>
>
> --
>
> --
> Andreas Neumann
> QGIS.ORG board member (treasurer)



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Regular paid positions for PR reviews

[Alessandro Pasotti via QGIS-Developer]

Hi,

Recently I have had the opportunity to discuss with some core QGIS
developers and we agreed that it would be a good idea if the QGIS
organization could fund a few weekly or monthly hours for PR reviews.

Here is my quick and initial proposal of requisites for the candidates:

- must be an active well known and long time QGIS C++ core developer
(for example from the top last 5 years committers [1])
- ideally we'd need more than a single developer: there is not a
single developer who is able to review all different areas of the code
base
- available for regular work (fixed number of weekly or monthly hours,
to be determined)

Note: the above list is just my quick ideas, feel free to suggest
anything you think best.

 I would like this topic to be added to the next PSC meeting agenda.

Kind regards.


[1] 
https://github.com/qgis/QGIS/graphs/contributors?from=2018-12-08=2023-12-08=c

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] HTML in plugin's metadata.txt works, but should it?

[Alessandro Pasotti via QGIS-Developer]

HI Johannes,

digging into very old memories here, IIRC when I wrote that metadata
docs I was mainly worried about displaying the plugin metadata.txt ini
file information in the plugin website, that's why I thought it was
wise to ban HTML formatting.



On Tue, Nov 28, 2023 at 11:05 AM Johannes Kröger (WhereGroup) via
QGIS-Developer  wrote:
>
> Hi!
>
> https://docs.qgis.org/3.34/en/docs/pyqgis_developer_cookbook/plugins/plugins.html#metadata-txt
> says for the fields "about", "description" and "changelog": "no HTML
> allowed"
>
> But actually we *can* use some HTML
> (https://doc.qt.io/qt-5/richtext-html-subset.html I assume).
> The plugin's information will be nicely rendered at least in QGIS'
> plugin manager.
>  does not seem to work, it just shows a placeholder. Clicking an
>  makes the plugin manager display a white page and open my system's
> web browser with the URL. But other formatting things work well.
>
> Example image:
> https://matrix.osgeo.org/_matrix/media/r0/download/matrix.wheregroup.com/nKHOTGcYWWpYqQKNWaSjuFbu/html%20in%20metadata.txt.png
>
> It would be super useful for me in a non-public plugin so I wonder:
>
> - Does "no HTML allowed" refer to the display in the official plugin
> repository https://plugins.qgis.org only?
> - Is it a bug that we can use some HTML in those fields or can we rely
> on it for the future?
>
> I am a bit torn between "oh yay, we can add some more detailed
> information in a nicely formatted way" and "oh dear lord this might lead
> to complex chaos in plugin descriptions".
>
> Cheers, Hannes
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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-psc] QGIS grant report: Improve test result handling on QGIS CI

[Alessandro Pasotti via QGIS-Developer]

On Mon, Nov 27, 2023 at 8:09 AM Nyall Dawson  wrote:
>
>
>
> On Mon, 27 Nov 2023, 4:56 pm Alessandro Pasotti,  wrote:
>>
>> Hi Nyall,
>>
>> good news, thank you for this improvement!
>>
>> Just a quick question, in the linked PR:
>> https://github.com/qgis/QGIS/pull/55417#issuecomment-1826995755
>> comment the instructions say:
>>
>> "The full test report (included comparison of rendered vs expected
>> images) can be found under the 'Checks' tab - 'QGIS tests',
>> 'Artifacts' section as test-results-5."
>>
>> But I couldn't find any test-results-5 in the artifacts section, there are 
>> only:
>>
>> Artifacts
>> build-22.04-qt5.tgz
>> build-38-qt6.tgz
>
>
> That's caused by a limitation in GitHub API. We can't retrieve the workflow 
> run id in an action, so that link will always just point to the most recent 
> workflow run for the PR.
>
> And in this case I reverted the change causing a test failure, so the most 
> recent workflow doesn't have the failure report.
>
> Hope that makes sense!
>

Yes, thanks for clarifying.



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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-psc] QGIS grant report: Improve test result handling on QGIS CI

[Alessandro Pasotti via QGIS-Developer]

Hi Nyall,

good news, thank you for this improvement!

Just a quick question, in the linked PR:
https://github.com/qgis/QGIS/pull/55417#issuecomment-1826995755
comment the instructions say:

"The full test report (included comparison of rendered vs expected
images) can be found under the 'Checks' tab - 'QGIS tests',
'Artifacts' section as test-results-5."

But I couldn't find any test-results-5 in the artifacts section, there are only:

Artifacts
build-22.04-qt5.tgz
build-38-qt6.tgz

Cheers.


On Mon, Nov 27, 2023 at 5:29 AM Nyall Dawson via QGIS-PSC
 wrote:
>
> Hi PSC,
>
> I'm happy to announce that this grant is now complete!
>
> While the original proposal was explicitly stated to be a research project 
> with no guarantees of success, the end result is predominantly a success 
> (with some limitations!)
>
> You can see the new failure handling in action in this PR: 
> https://github.com/qgis/QGIS/pull/55417#issuecomment-1826995755
>
> What we have now is that any tests which fail a rendering comparison will 
> write a descriptive comment to the PR, as shown in the above link. The 
> comment details which render tests failed, where they are in the code, and 
> includes some helpful pointers to downloading the full test report and the 
> QGIS developer documentation.
>
> Originally, I hoped to link directly to the full test report or include it as 
> an attachment to the comment. Unfortunately this is NOT possible given the 
> current Github API. There's a bunch of notes I've added to the initial 
> comment in https://github.com/qgis/QGIS/pull/54906 which link to the 
> limitations / feature requests on Github's side, so we can monitor the 
> situation and further improve the reports if/when Github add this 
> functionality.
>
> As well as the above described improvements on the CI side, I've also 
> implemented lots of improvements in running the tests locally and how the 
> render test reports are generated and presented to developers!
>
> Thanks for making this possible!
>
> Nyall
>
>
>
>
>
> ___
> QGIS-PSC mailing list
> qgis-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Next QGIS QT6 Status meeting - November 30th 2023 @ 12.00 CET

[Alessandro Pasotti via QGIS-Developer]

Hi,

The next meeting about QGIS QT6 migration status will be next week's on thursday

https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=11=30=11=0=0=47=254

If you are one of the involved developers and cannot attend please
make sure to send an email report about your activities.

Meeting link:
https://meet.jit.si/QGIS-QT6


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Removing __author__ , __date__, __copyright__ from python files?

[Alessandro Pasotti via QGIS-Developer]

Hi Nyall,

I have no objections to remove the __revision__ and __email__ and to
move remaining information to a comment instead of using the __param__
format but I am strongly against removing "author" and "date"
information altogether, especially from the C++ files.

I find it useful to quickly remind me about the origin of that part of
the code and honestly I like the fact that people who initially spent
time on that (even if they do not contribute anymore or their code was
almost totally rewritten) is mentioned and remembered in the headers
"forever".

Kind regards.

On Sun, Nov 5, 2023 at 10:53 PM Nyall Dawson via QGIS-Developer
 wrote:
>
> Hey list,
>
> I'd like to propose that we remove all the __author__ , __date__ and 
> __copyright__ strings from the python files in our repository.
>
> My thinking:
>
> - This isn't an official Python style standard or universally recommended 
> approach. It *is* used elsewhere, but there's an equally large group which 
> consider it just unnecessary noise.
> - It's misleading, and presents the incorrect impression that a single person 
> is responsible for the code in that file. That's 100% NOT the case with QGIS.
> - It's all redundant. This information is available in a MUCH more accurate 
> form via git history.
>
> Are there any objections to removing this?
>
> (For completeness: In a follow up proposal I'm going to suggest removing ALL 
> the "Date: / Copyright: / Email: " strings from our file headers, for the 
> same reasons).
>
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 Developer - Introduction

[Alessandro Pasotti via QGIS-Developer]

Welcome Lova!

Looking forward to seeing your reports!

Kind regards

On Tue, Oct 17, 2023 at 10:17 AM Lova Andriarimalala via
QGIS-Developer  wrote:
>
> Hello to everyone.
>
> My name is Lova, and I would like to introduce myself as a QGIS funded 
> developer. I studied geography at the University of Antananarivo where I 
> started using QGIS Desktop. I have a background in cartography, GIS Analysis 
> and Web-GIS Developement. I have been a QGIS user for almost 10 years and I 
> enjoy making beautiful maps with it.
>
> My intention is to forward a weekly report to you every Friday, detailing my 
> latest contributions. I kindly request your concurrence on this matter; 
> however, if you hold dissenting views, I would appreciate your prompt 
> notification. Furthermore, should you possess any recommendations, I welcome 
> your input and kindly ask that you transmit them to me.
>
> Currently, I am working on the QGIS Home Page News Feed website. Hopefully, I 
> will send you a report on Friday describing all changes and updates that I 
> made.
>
> I always believe in the power of QGIS not only as a FOSS tool but also as a 
> project that aim various sectors. I am delighted to contribute to the project.
>
> Kind regards,
> Lova
> --
>
> Lova Andriarimalala
>
> QGIS Full Stack Developer
>
> Visit http://kartoza.com to find out about open source:
>
> * Desktop GIS programming services
>
> * Geospatial web development
>
> * GIS Training
>
> * Consulting Services
>
> Office: +261(0)34 09 524 73
>
>
>
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 repository management

[Alessandro Pasotti via QGIS-Developer]

Hi Sandro,

Disclaimer: these are my personal opinions and not the official PSC position.

I understand your frustration, CI is often failing for no reason and
we are wasting a lot of time (and CPU power) to re-run the failing
workflows, any effort to fix these issues is greatly appreciated.

About the merge constraints, I think that they are important and
useful because CI failing tests have proven to be a sign of a real
problem in the past, and also because peer review (PR approval) is
almost always useful to prevent mistakes and ultimately leads to a
better and safer code.

Coming to your questions, AFAIK whoever has commit rights can approve
someone else's PR but cannot self approve (see the exceptions below
about bypassing the blocks).

The QGIS organization has a budget for PR queue management (triage)
and a separate entry for reviews (budget is public
https://www.qgis.org/en/site/getinvolved/governance/finance/index.html)
, in the past this has been working well while I agree that recently
PRs have been pending without review for a (too) long time.

If I am not mistaken, everyone with commit rights can still push to
master directly without opening a PR, this is not generally
recommended (I think I have been doing this only once or twice in the
last few years), however a direct push to master is acceptable for a
few cases (e.g. to fix an one-liner change issue where the developer
is fixing his/hers own mess and is 100% sure there will not be side
effects, fix a typo in a comment, for last minute fixes done by the
package maintainers when making the releases etc.).

A small group of us (3-4 developers including me) have admin access to
all QGIS repositories and we can bypass any check and merge all PRs
without approval.

I admit that I have been using these superpowers more and more often
(IIRC three or four times) in the last year while I have never felt
the need to use them before, in an ideal world it should not be
necessary except for the same use cases I have pointed out for the
direct pushes to master.

The bottom line is that the situation is not perfect and can certainly
be improved but at the end of the day we are all doing our best to
keep the process running as smoothly as we can.

Thank you for raising this point, you are absolutely right that it
should be clearly documented, this has been in our TODO list for a
long time.

Best regards.


On Fri, Oct 13, 2023 at 6:42 PM Sandro Santilli via QGIS-Developer
 wrote:
>
> Hello all,
> today I was finally able to more clearly see the problem that frustrates
> me everytime a take part to a new QGIS bugfixing drive, and I would like
> to share it hoping to find a solution togheter.
>
> The main problem:
>
>   - Despite having been granted write access to the QGIS repository in 2012
> [1], I cannot effectively use that power today
>
> It's not just me, I think, but I cannot tell for sure because the 
> configuration
> of the infrastructure currently in use (github) is not available for me to see
> and the governance page on the official QGIS website does not contain this
> information [2]. This being blind of course adds up to my frustration.
>
> From experience, I know that the reason why I cannot write to the QGIS
> repository is because "branch protection" is active (for the master branch
> at least) and a set of conditions are required to merge a PR, namely:
>
>   - All CI tests need to pass.
>
>   - Someone else (I don't know from which group of people) needs to
> approve the proposed change.
>
> While I do the above condition being a useful indication for "QGIS
> core developers" to decide whether to accept or not a change request,
> I find them representing an obstacle way more often than a service,
> and in particular:
>
> 1. CI is often broken for reasons that are independent from the proposed
>change.
>
> 2. An aberration of the "review" condition is that a change proposed by a
>contributor and approved by me can be merged but a change proposed by
>me and approved by the same contributor can not be merged, effectively
>giving me ("core QGIS committer") less power than the power of a random
>contributor.
>
> The rules described above are not found from the governance page [2]
> so it isn't easy for me to propose changes because I don't have a clear
> picture of current rules (like, I believe some people in QGIS can
> self-approve PRs but dunno how to tell who and why).
>
> I would personally welcome (and be able to help taking) the following actions:
>
>   1. Clearly document the roles and rules on the website
>
>   2. Allow those with "write access" to self-approve PRs
>
>   3. Define rules by which "write access" privileges to the repository
>  are revoked
>
> Thanks for having read this in full, and I hope to hear your position
> on the matter.  Happy hacking !
>
>
> [1] https://lists.osgeo.org/pipermail/qgis-developer/2012-October/022715.html
> [2] 

Re: [QGIS-Developer] [Qgis-psc] Proposal: Core committer rights for Andrea Giudiceandrea

[Alessandro Pasotti via QGIS-Developer]

+1

Cheers

Il lun 21 ago 2023, 00:37 Nyall Dawson via QGIS-PSC <
qgis-...@lists.osgeo.org> ha scritto:

> Hi PSC,
>
> I'd like to propose that core committer rights are granted to Andrea
> Giudiceandrea (@agiudiceandrea, https://github.com/agiudiceandrea ).
>
> Andrea has been active in QGIS c++ development for the last 5 years,
> and has a fantastic track record of contributions. Their contributions
> demonstrate all the qualities we need for core contributors --
> attention to detail, careful consideration of the ramifications of
> changes, and a very clear dedication to making QGIS a better
> experience for end users. Time and time again, they've shown a
> willingness to just jump in and fix things directly, and QGIS would
> not be the application it is today without their contributions.
>
> Thanks for your consideration!
> Nyall
> ___
> QGIS-PSC mailing list
> qgis-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
___
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 Documentation Writer - Introduction

[Alessandro Pasotti via QGIS-Developer]

Hi Selma,


Welcome aboard!

Looking forward to your reports.

Kind regards

Il ven 21 lug 2023, 14:15 Selma Vidimlic via QGIS-Developer <
qgis-developer@lists.osgeo.org> ha scritto:

> Hello to everyone.
>
> My name is Selma, and I'd like to introduce myself as a QGIS funded
> Documentation Writer. I have a background in geography and GIS, and I've
> been using QGIS for a while, so I'm excited to contribute to this project
> and community.
> My intention is to send you a report every Friday to let you know about
> the most recent contribution I made. I hope you all agree with me; if not,
> please let me know, and if you have any suggestions, please send them to me.
>
> For now I have set up my environment and I will start with User Manual and
> Training Manual and hopefully next Friday I will send you a report with all
> changes and updates that I made for the week.
>
> I think QGIS to be a really essential and truly fantastic project, and I'm
> thrilled to be a part of it.
>
> Kind regards,
> Selma.
>
> --
> Selma Vidimlic Husic
> QGIS Documentation Writer
> Visit http://kartoza.com to find out about open source:
> * Desktop GIS programming services
> * Geospatial web development
> * GIS Training
> * Consulting Services
> Phone: +387 61 933 651
> ___
> 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] QT6 meeting minutes

[Alessandro Pasotti via QGIS-Developer]

Hi,

here you can find the meeting minutes for yesterday's meeting.

https://docs.google.com/document/d/1qAtyoPyrPgc5NS78DxmAFS_yhkuwiUmbPcxsuWFBH-Q


Kind regards.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QT6 meeting

[Alessandro Pasotti via QGIS-Developer]

Now, at https://meet.jit.si/QGIS-QT6

(The meeting link is always the same)

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Next QGIS QT6 update meeting

[Alessandro Pasotti via QGIS-Developer]

Hi,

Here is the link to choose a time for the next QT6 update meeting,

https://doodle.com/bp/alessandropasotti/qgis-qt6-update-meeting

please fill in the form with your date/time availability.

Kind regards.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Why so many database calls?

[Alessandro Pasotti via QGIS-Developer]

Hi Cory,

I think many developers have one or two ideas about where to look,
they probably didn't have the time to look into it.

Is there a ticket already?


On Sat, Jun 24, 2023 at 8:46 PM Cory Albrecht via QGIS-Developer
 wrote:
>
> So, nobody knows why QGIS makes all those seemingly wasteful SQL reads?
>
> On Fri, Jun 16, 2023 at 1:18 PM Cory Albrecht  wrote:
>>
>> So QGIS took almost 2.5 hours to delete those 1,000-ish vertices, spitting 
>> out those seemingly unnecessary transaction blocks every second or so. 
>> Judging by the numbers of the named blocks, roughly 5,000 of them were done 
>> just to delete those 1,000-ish vertices.
>>
>> Right now, on that same feature, I went to add a new vertx in the middle of 
>> the gap created by the deletion of the 1,000-ish last night, drag it to a 
>> new spot, and right clock to place. Those same seemingly unnecessary 
>> read-only transactions with a single select are being done, but at the rate 
>> of roughly 100 per second and the process takes about 7-8 minutes after the 
>> right click before QGIS becomes responsive again. I've done it a few times 
>> this morning, exiting QGIS without saving, and same thing each time.
>>
>> Why so many of these database queries?
>>
>>
>> On Thu, Jun 15, 2023 at 5:40 PM Cory Albrecht  wrote:
>>>
>>> Hello,
>>>
>>> So I've been trying to track down why my postgresql server was getting so 
>>> many Signal 10 (SUG BS, memory bus) errors. So far I have figured out that 
>>> they are only happening when QGIS is connecting to it using GSS/Kerberos 
>>> encryption. No clue yet as to which side is the culprit (e.g. bad QGIS 
>>> kerberised data flow, or bad PostgreSQL handling of the connection). QGIS 
>>> cinnectio with SSL encryption is fine.
>>>
>>> Anyways, while doing this I've been watching a lot of PostgreSQL server 
>>> logs, and I noticed the following behaviour of QGIS:
>>>
>>> When using the vertex editor to delete a whole slew (1,000-ish) vertices 
>>> from a polygon feature, I saw that QGIS was making repeated DB cals like 
>>> this:
>>>
>>> Jun 15 17:14:19 postgresql-3 postgres[87136]: [3204-1] ::>[2023-06-15 
>>> 17:14:19.289 EDT][648b7d94.15460][87136/]  LOG:  
>>> duration: 0.330 ms  statement: BEGIN READ ONLY;DECLARE qgis_1062 BINARY 
>>> CURSOR FOR SELECT 
>>> "feature_uuid"::text,"name"::text,"start_date"::text,"end_date"::text,"main_rgb"::text,"realm_uuid"::text,"stripe_rgb"::text,"border_rgb"::text,"border_shade"::text,"sovereign"::text,"type"::text,"info_url"::text,array_out("predecessors")::text,array_out("successors")::text,boolout("visible")::text,boolout("has_children")::text,"full_name"::text,"alternate_name"::text,"flag_url"::text
>>>  FROM "Balance of Power"."timeline_level0" WHERE 
>>> "feature_uuid"::text='fbbec581-eb8f-4068-8729-8f9d63896bd5'
>>> Jun 15 17:14:19 postgresql-3 postgres[87136]: [3205-1] ::>[2023-06-15 
>>> 17:14:19.290 EDT][648b7d94.15460][87136/]  LOG:  
>>> duration: 0.628 ms  statement: FETCH FORWARD 2000 FROM qgis_1062
>>> Jun 15 17:14:19 postgresql-3 postgres[87136]: [3206-1] ::>[2023-06-15 
>>> 17:14:19.291 EDT][648b7d94.15460][87136/]  LOG:  
>>> duration: 0.045 ms  statement: CLOSE qgis_1062;COMMIT
>>>
>>> An example of the QGIS console output:
>>>
>>> ./src/core/qgsmessagelog.cpp:29 : (logMessage) [4ms] 2023-06-15T17:37:08 
>>> PostGIS[1] NOTICE: LOG:  duration: 0.399 ms  statement: FETCH FORWARD 2000 
>>> FROM qgis_2017
>>> ./src/core/qgsmessagelog.cpp:29 : (logMessage) [1ms] 2023-06-15T17:37:08 
>>> PostGIS[1] NOTICE: LOG:  duration: 0.035 ms  statement: CLOSE 
>>> qgis_2017;COMMIT
>>> ./src/core/qgsmessagelog.cpp:29 : (logMessage) [3ms] 2023-06-15T17:37:08 
>>> PostGIS[1] NOTICE: LOG:  duration: 0.240 ms  statement: BEGIN READ 
>>> ONLY;DECLARE qgis_2018 BINARY CURSOR FOR SELECT 
>>> "feature_uuid"::text,"name"::text,"start_date"::text,"end_date"::text,"main_rgb"::text,"realm_uuid"::text,"stripe_rgb"::text,"border_rgb"::text,"border_shade"::text,"sovereign"::text,"type"::text,"info_url"::text,array_out("predecessors")::text,array_out("successors")::text,boolout("visible")::text,boolout("has_children")::text,"full_name"::text,"alternate_name"::text,"flag_url"::text
>>>  FROM "Balance of Power"."timeline_level0" WHERE 
>>> "feature_uuid"::text='fbbec581-eb8f-4068-8729-8f9d63896bd5'
>>> ./src/core/qgsmessagelog.cpp:29 : (logMessage) [2ms] 2023-06-15T17:37:08 
>>> PostGIS[1] NOTICE: LOG:  duration: 0.406 ms  statement: FETCH FORWARD 2000 
>>> FROM qgis_2018
>>> ./src/core/qgsmessagelog.cpp:29 : (logMessage) [1ms] 2023-06-15T17:37:08 
>>> PostGIS[1] NOTICE: LOG:  duration: 0.034 ms  statement: CLOSE 
>>> qgis_2018;COMMIT
>>>
>>>
>>>
>>> That is repeated 4 times every couple of seconds as I wait for QGIS to 
>>> finish deleting these 1,000-ish vertices. So far it's at begin block 
>>> qgis_2058 (increasing sequentially) and it's been 20+ minutes that QGIS has 
>>> been frozen, CPU usage for the process jumping around between 100% and 300%.
>>>
>>> (Before you ask, Fall 2021 

Re: [QGIS-Developer] How to enable debugging mode on QGIS start in Win11

[Alessandro Pasotti via QGIS-Developer]

QGIS_DEBUG=X has no effect if QGIS was not built in debug mode.


On Tue, Jun 20, 2023 at 4:18 PM Vedran Stojnović via QGIS-Developer
 wrote:
>
> Hi,
>
> I just installed QGIS 3.30.3 via web installer ("qgis-full" version) and QGIS 
> won't start at all, nor does throw any error when I start it from PowerShell 
> by executing "qgis-bin.exe".
> I tried reinstalling a few times using different servers (default one and 
> norbit.de) and I also cleaned the cache folder before changing the server.
>
> I already tried adding these two lines to "qgis-bin.env" and I created 
> "qgislog.txt" on the desktop, but I still do not get any output to the 
> command line and txt file is empty after trying to start qgis:
> QGIS_DEBUG=9
> QGIS_LOG_FILE=C:\Users\phidr\Desktop\qgislog.txt
>
> so the current contents of "qgis-bin.env" is:
> PATH=C:\OSGeo4W\apps\qgis\bin;C:\OSGeo4W\apps\grass\grass82\lib;C:\OSGeo4W\apps\grass\grass82\bin;C:\OSGeo4W\apps\qt5\bin;C:\OSGeo4W\apps\Python39\Scripts;C:\OSGeo4W\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBem
> GDAL_DATA=C:\OSGeo4W\apps\gdal\share\gdal
> GDAL_DRIVER_PATH=C:\OSGeo4W\apps\gdal\lib\gdalplugins
> GDAL_FILENAME_IS_UTF8=YES
> PDAL_DRIVER_PATH=C:\OSGeo4W\apps\pdal\plugins
> GISBASE=C:\OSGeo4W\apps\grass\grass82
> GRASS_PROJSHARE=C:\OSGeo4W\share\proj
> GRASS_PYTHON=C:\OSGeo4W\bin\python3.exe
> OSGEO4W_ROOT=C:\OSGeo4W
> PROJ_LIB=C:\OSGeo4W\share\proj
> PYTHONHOME=C:\OSGeo4W\apps\Python39
> PYTHONPATH=C:\OSGeo4W\apps\grass\grass82\etc\python;
> PYTHONUTF8=1
> QGIS_PREFIX_PATH=C:/OSGeo4W/apps/qgis
> QT_PLUGIN_PATH=C:\OSGeo4W\apps\qgis\qtplugins;C:\OSGeo4W\apps\qt5\plugins
> VSI_CACHE=TRUE
> VSI_CACHE_SIZE=100
> O4W_QT_PREFIX=C:/OSGeo4W/apps/Qt5
> O4W_QT_BINARIES=C:/OSGeo4W/apps/Qt5/bin
> O4W_QT_PLUGINS=C:/OSGeo4W/apps/Qt5/plugins
> O4W_QT_LIBRARIES=C:/OSGeo4W/apps/Qt5/lib
> O4W_QT_TRANSLATIONS=C:/OSGeo4W/apps/Qt5/translations
> O4W_QT_HEADERS=C:/OSGeo4W/apps/Qt5/include
> QGIS_WIN_APP_NAME=OSGeo4W\QGIS Desktop 3.30.3
> SSL_CERT_DIR=C:\OSGeo4W\apps\openssl\certs
> SSL_CERT_FILE=C:\OSGeo4W\bin\curl-ca-bundle.crt
> QGIS_DEBUG=9
> QGIS_LOG_FILE=C:\Users\phidr\Desktop\qgislog.txt
>
> --
> Kind regards,
> Vedran Stojnović.
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Next QGIS QT6 update meeting

[Alessandro Pasotti via QGIS-Developer]

Hi,

for everybody interested, the next QT6 QGIS meeting will be Wednesday
24th may at 11.00am CET time.

Join on https://meet.jit.si/QGIS-QT6

Talk to you soon!


On Tue, May 9, 2023 at 11:11 AM Alessandro Pasotti  wrote:
>
> Hi,
>
> Gentle reminder to pick your favorite date/time for the next QT6
> meeting so we can settle the date:
>
> https://doodle.com/meeting/participate/id/bYyqoG9b/
>
> Thank you. Regards
>
> On Fri, Apr 21, 2023 at 12:10 PM Alessandro Pasotti  
> wrote:
> >
> > Hi,
> >
> > Thank you for attending the meeting.
> >
> > As agreed, pick your date:
> >
> > https://doodle.com/meeting/participate/id/bYyqoG9b
> >
> > Kind regards.
> >
> > --
> > Alessandro Pasotti
> > QCooperative:  www.qcooperative.net
> > ItOpen:   www.itopen.it
>
>
>
> --
> Alessandro Pasotti
> QCooperative:  www.qcooperative.net
> ItOpen:   www.itopen.it



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 Server and OGC API - Processes

[Alessandro Pasotti via QGIS-Developer]

Cool, thanks!

I was actually thinking of a core implementation but that's a very good start!

On Fri, May 12, 2023 at 1:10 PM David Marteau  wrote:
>
> Hi,
>
> There is an implementation of OGC API processes on top of Qgis
> Processing here: https://github.com/3liz/py-qgis-wps that supports Qgis
> algorithms as processes out of the box.
>
>
> Le 12/05/2023 à 11:44, Alessandro Pasotti via QGIS-Developer a écrit :
> > Hi,
> >
> > Is anybody working or planning to work on an implementation of OGC API
> > - Processes [1] for QGIS Server?
> >
> > [1] https://ogcapi.ogc.org/processes/overview.html
> >



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS Server and OGC API - Processes

[Alessandro Pasotti via QGIS-Developer]

Hi,

Is anybody working or planning to work on an implementation of OGC API
- Processes [1] for QGIS Server?

[1] https://ogcapi.ogc.org/processes/overview.html

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Next QGIS QT6 update meeting

[Alessandro Pasotti via QGIS-Developer]

Hi,

Gentle reminder to pick your favorite date/time for the next QT6
meeting so we can settle the date:

https://doodle.com/meeting/participate/id/bYyqoG9b/

Thank you. Regards

On Fri, Apr 21, 2023 at 12:10 PM Alessandro Pasotti  wrote:
>
> Hi,
>
> Thank you for attending the meeting.
>
> As agreed, pick your date:
>
> https://doodle.com/meeting/participate/id/bYyqoG9b
>
> Kind regards.
>
> --
> Alessandro Pasotti
> QCooperative:  www.qcooperative.net
> ItOpen:   www.itopen.it



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Next QGIS QT6 update meeting

[Alessandro Pasotti via QGIS-Developer]

Hi,

Thank you for attending the meeting.

As agreed, pick your date:

https://doodle.com/meeting/participate/id/bYyqoG9b

Kind regards.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QT6 move forward meeting next week

[Alessandro Pasotti via QGIS-Developer]

The QT6 meeting is starting in 15 minutes, here is the link to the
agenda/minutes:

https://docs.google.com/document/d/1YBRO2Uf9vzD6CqRTA1eA3nudRnUhngUvGYwpECyH2_M/edit?usp=sharing

On Thu, Apr 20, 2023 at 9:53 AM Alessandro Pasotti  wrote:
>
> Hi,
>
> The QT6 meeting will be tomorrow friday 21 april at 11.00am local time
> (The Netherlands).
>
> I will try to connect my computer to https://meet.jit.si/QGIS-QT6
>
> Talk to you soon.
>
>
>
> On Tue, Apr 18, 2023 at 2:46 PM Alessandro Pasotti  wrote:
> >
> > Hi,
> >
> > I have added an option for friday at 11am, please check if that works for 
> > you.
> >
> > Kind regards.
> >
> >
> > On Tue, Apr 18, 2023 at 12:10 PM Alessandro Pasotti  
> > wrote:
> > >
> > > ok, let's make a doodle, it's in the morning becausef of our
> > > australian/asian friends.
> > >
> > > https://doodle.com/meeting/participate/id/eXrn1KWb
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Apr 18, 2023 at 9:27 AM Jürgen E. Fischer via QGIS-Developer
> > >  wrote:
> > > >
> > > > Hi Ale,
> > > >
> > > > On Tue, 18. Apr 2023 at 09:18:12 +0200, Alessandro Pasotti via 
> > > > QGIS-Developer wrote:
> > > > > Ok, let's do it the 20th. 11:00am local time.
> > > >
> > > > Jm, I'll still be on the way then.
> > > >
> > > >
> > > > 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 Norden
> > > > https://www.norbit.de
> > > > QGIS release manager (PSC)  Germany IRC: jef on 
> > > > Libera|OFTC
> > > > ___
> > > > 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
> > >
> > >
> > >
> > > --
> > > Alessandro Pasotti
> > > QCooperative:  www.qcooperative.net
> > > ItOpen:   www.itopen.it
> >
> >
> >
> > --
> > Alessandro Pasotti
> > QCooperative:  www.qcooperative.net
> > ItOpen:   www.itopen.it
>
>
>
> --
> Alessandro Pasotti
> QCooperative:  www.qcooperative.net
> ItOpen:   www.itopen.it



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QT6 move forward meeting next week

[Alessandro Pasotti via QGIS-Developer]

Hi,

The QT6 meeting will be tomorrow friday 21 april at 11.00am local time
(The Netherlands).

I will try to connect my computer to https://meet.jit.si/QGIS-QT6

Talk to you soon.



On Tue, Apr 18, 2023 at 2:46 PM Alessandro Pasotti  wrote:
>
> Hi,
>
> I have added an option for friday at 11am, please check if that works for you.
>
> Kind regards.
>
>
> On Tue, Apr 18, 2023 at 12:10 PM Alessandro Pasotti  
> wrote:
> >
> > ok, let's make a doodle, it's in the morning becausef of our
> > australian/asian friends.
> >
> > https://doodle.com/meeting/participate/id/eXrn1KWb
> >
> >
> >
> >
> >
> > On Tue, Apr 18, 2023 at 9:27 AM Jürgen E. Fischer via QGIS-Developer
> >  wrote:
> > >
> > > Hi Ale,
> > >
> > > On Tue, 18. Apr 2023 at 09:18:12 +0200, Alessandro Pasotti via 
> > > QGIS-Developer wrote:
> > > > Ok, let's do it the 20th. 11:00am local time.
> > >
> > > Jm, I'll still be on the way then.
> > >
> > >
> > > 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 Norden
> > > https://www.norbit.de
> > > QGIS release manager (PSC)  Germany IRC: jef on 
> > > Libera|OFTC
> > > ___
> > > 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
> >
> >
> >
> > --
> > Alessandro Pasotti
> > QCooperative:  www.qcooperative.net
> > ItOpen:   www.itopen.it
>
>
>
> --
> Alessandro Pasotti
> QCooperative:  www.qcooperative.net
> ItOpen:   www.itopen.it



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QT6 move forward meeting next week

[Alessandro Pasotti via QGIS-Developer]

Hi,

I have added an option for friday at 11am, please check if that works for you.

Kind regards.


On Tue, Apr 18, 2023 at 12:10 PM Alessandro Pasotti  wrote:
>
> ok, let's make a doodle, it's in the morning becausef of our
> australian/asian friends.
>
> https://doodle.com/meeting/participate/id/eXrn1KWb
>
>
>
>
>
> On Tue, Apr 18, 2023 at 9:27 AM Jürgen E. Fischer via QGIS-Developer
>  wrote:
> >
> > Hi Ale,
> >
> > On Tue, 18. Apr 2023 at 09:18:12 +0200, Alessandro Pasotti via 
> > QGIS-Developer wrote:
> > > Ok, let's do it the 20th. 11:00am local time.
> >
> > Jm, I'll still be on the way then.
> >
> >
> > 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)  Germany IRC: jef on Libera|OFTC
> > ___
> > 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
>
>
>
> --
> Alessandro Pasotti
> QCooperative:  www.qcooperative.net
> ItOpen:   www.itopen.it



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QT6 move forward meeting next week

[Alessandro Pasotti via QGIS-Developer]

I'm sorry but this is the best I can do: Nyall & friends are not
available in our afternoon and I have a workshop plus Martin is not
here on the 21st (and he spoke first).

Maybe you will be able to attend remotely?

I think we will be able to update you in person anyway.

Talk to you soon!


On Tue, Apr 18, 2023 at 12:46 PM Jürgen E. Fischer via QGIS-Developer
 wrote:
>
> Hi Ale,
>
> On Tue, 18. Apr 2023 at 12:10:27 +0200, Alessandro Pasotti wrote:
> > ok, let's make a doodle, it's in the morning becausef of our
> > australian/asian friends.
>
> > https://doodle.com/meeting/participate/id/eXrn1KWb
>
> That doesn't have any better options.  I'm traveling in the morning to Den
> Bosch and probably will arrive shortly after 1300.
>
>
> 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)  Germany IRC: jef on Libera|OFTC
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QT6 move forward meeting next week

[Alessandro Pasotti via QGIS-Developer]

ok, let's make a doodle, it's in the morning becausef of our
australian/asian friends.

https://doodle.com/meeting/participate/id/eXrn1KWb





On Tue, Apr 18, 2023 at 9:27 AM Jürgen E. Fischer via QGIS-Developer
 wrote:
>
> Hi Ale,
>
> On Tue, 18. Apr 2023 at 09:18:12 +0200, Alessandro Pasotti via QGIS-Developer 
> wrote:
> > Ok, let's do it the 20th. 11:00am local time.
>
> Jm, I'll still be on the way then.
>
>
> 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)  Germany IRC: jef on Libera|OFTC
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QT6 move forward meeting next week

[Alessandro Pasotti via QGIS-Developer]

Ok, let's do it the 20th. 11:00am local time.

I'll find a room and post a jitsi link for remote attendees.



Il dom 16 apr 2023, 17:19 Martin Dobias  ha scritto:

> Hi Alessandro
>
> A meeting for qt6 migration would be useful... My personal preference
> would be for 20th as I will be leaving on 21st already and I would probably
> miss it...
>
> Cheers
> Martin
>
>
> On Fri, Apr 14, 2023 at 9:48 AM Alessandro Pasotti via QGIS-Developer <
> qgis-developer@lists.osgeo.org> wrote:
>
>> Hi,
>>
>> The budget for the QT6 research/migration work was approved, I was
>> thinking of organizing a meeting  next week on the 20th or 21st around
>> 11:00am local time (The Netherlands).
>>
>> Many of us will be able to attend in person but I will try to set up a
>> remote connection.
>>
>> Any preference on the date?
>>
>> --
>> Alessandro Pasotti
>> QCooperative:  www.qcooperative.net
>> ItOpen:   www.itopen.it
>> ___
>> 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] QT6 move forward meeting next week

[Alessandro Pasotti via QGIS-Developer]

Hi,

The budget for the QT6 research/migration work was approved, I was
thinking of organizing a meeting  next week on the 20th or 21st around
11:00am local time (The Netherlands).

Many of us will be able to attend in person but I will try to set up a
remote connection.

Any preference on the date?

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS Enhancement: Use pre-commit to automate installation and management of all pre-commit hooks

[Alessandro Pasotti via QGIS-Developer]

Hi,

I have just submitted a QEP: Use pre-commit to automate installation
and management of all pre-commit hooks

https://github.com/qgis/QGIS-Enhancement-Proposals/issues/265

I would like to submit a grant proposal for that work if the QEP is
accepted, please add your comments.

Kind regards.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS Enhancement: Move from astyle to clang-format for C++ code formatting

[Alessandro Pasotti via QGIS-Developer]

Hi,

I have just submitted a QEP: Move from astyle to clang-format for C++
code formatting

https://github.com/qgis/QGIS-Enhancement-Proposals/issues/264

I would like to submit a grant proposal for that work if the QEP is
accepted, please add your comments.

Kind regards.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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-psc] QGIS QT6 meeting minutes

[Alessandro Pasotti via QGIS-Developer]

Thank you for the update.

I'm going to formalize the QT6 plan in the next PSC meeting tomorrow
and then I'll organize another meeting, probably during the hackfest
considering that there are Easter holidays in the middle.



On Mon, Apr 3, 2023 at 5:19 PM Julien Cabieces via QGIS-Developer
 wrote:
>
>
> Hi,
>
> I just wanted to advertise that I'm working on builing python binding
> for QGIS with Qt6/PyQt6 . It's here : 
> https://github.com/troopa81/QGIS/tree/build_qt6_ci_pyqt
>
> This is still draft, there is a lot of hacky stuff and commented code
> but I managed to build bindings for all modules and run
> sucessfully some tests (not all).
>
> I hope I could propose a WIP PR by the end of the week so we could
> discuss about this.
>
> Regards,
> Julien
>
>
> > On Wed, 15 Mar 2023 at 18:45, Julien Cabieces via QGIS-PSC
> >  wrote:
> >>
> >>
> >> Hi,
> >>
> >> Thank you for the meeting minutes!
> >>
> >> I'm already planning to continue the effort in
> >> porting/fixing code for Qt6 in the next months using Oslandia own
> >> funding, so I'm candidate to join the working group.
> >>
> >> > ND: major missing bit: python support. Bulk of the tests are thus not 
> >> > running
> >> > Packaging issues - Sandro Mani looking into python stuff for fedora
> >> > (QVariant issues)
> >>
> >> Is there a reason why we are switching from ubuntu for Qt5 builds to
> >> fedora for Qt6 builds ? Because there is already PyQt6 packages in 
> >> ubuntu:22.10.
> >
> > Initially Fedora was the *only* platform offering qt6 binaries, so all
> > the CI setup was done using that. But now that Ubuntu/etc have caught
> > up I still think it's a good idea to leave the CI with Fedora so that
> > we get a better spread of testing environments. (Fedora generally has
> > much more recent gdal/geos/proj/etc so by running CI on this
> > environment we're more likely to catch issues/test differences across
> > a wider range of library versions)
> >
> > Nyall
> >
> >
> >>
> >> Regards,
> >> Julien
> >>
> >>
> >>
> >> > Hi,
> >> >
> >> > Here is some feedback about the QGIS QT6 status meeting we had yesterday.
> >> >
> >> > First I'd like to thank all the attendees, it was great to see the
> >> > excitement and the interest in moving forward with this project.
> >> >
> >> > If I may summarize the outcome, we decided that the best way to move
> >> > forward is to create a working group with all the interested
> >> > developers and allocate a budget (20K is the proposed budget) in order
> >> > to find a solution to the main blockers, it is very hard to estimate
> >> > the effort in advance but we thought that with that budget we will be
> >> > able to move forward.
> >> >
> >> > Any QGIS core developer with experience in the main areas involved and
> >> > willing to dedicate some time to this effort is eligible and warmly
> >> > invited to participate in the working group.
> >> >
> >> > Here is the link to the minutes:
> >> >
> >> > https://docs.google.com/document/d/1Un4Jyz9PO8t2vmEBkUKa187SytM2gsQn-jB6mSqXcvU/
> >> >
> >> > This proposal will be discussed at the next PSC meeting.
> >>
> >>
> >> --
> >>
> >> Julien Cabieces
> >> Senior Developer at Oslandia
> >> julien.cabie...@oslandia.com
> >> 09.72.52.52.76
> >> ___
> >> QGIS-PSC mailing list
> >> qgis-...@lists.osgeo.org
> >> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
>
> --
>
> Julien Cabieces
> Senior Developer at Oslandia
> julien.cabie...@oslandia.com
> 09.72.52.52.76
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] How does QGIS parses the shapefile so quickly

[Alessandro Pasotti via QGIS-Developer]

Hi,

QGIS is using the GDAL/OGR library to read the shapefiles.

On Mon, Mar 27, 2023 at 9:51 AM 余 绍健 via QGIS-Developer
 wrote:
>
> Dear All,
>   Sorry to interrupt, I'm newer to QGIS, whe I use QIGS, I find that it is so 
> quick for QGIS to parse shapefile even it is a very big file, I try to decode 
> the file by my own with shapelib library, but the result is disappointed, I 
> try to learn it by myself with QGIS source code but failed, so anyone can 
> help point the entry of  decoding process?
>
> Thanks.
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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-psc] QGIS QT6 meeting minutes

[Alessandro Pasotti via QGIS-Developer]

On Wed, Mar 15, 2023 at 4:38 PM Andreas Neumann  wrote:
>
> Hi Ale and colleagues,
>
> Thank you all for your efforts to make QGIS qt6 build a reality - and work on 
> overcoming the blockers.
>
> Perhaps we can speed up the PSC decision and give this a go through our 
> approval on the QGIS PSC mailing list, rather than having to wait for the 
> next meeting in 3 weeks.
>
> Budget wise we can cover the approximate estimated expenses of 20k €. The 
> funding drive had good results - more sustaining members on the upper levels 
> (large and platinum) are in the pipeline.
>
> From me it is a +1.

Agreed, of course +1 from me too.



>
> Andreas
>
> On Wed, 15 Mar 2023 at 09:52, Alessandro Pasotti via QGIS-PSC 
>  wrote:
>>
>> Hi Michel,
>>
>> thank you and welcome!
>>
>> The next step is to get this plan approved by the PSC (with the
>> associated budget), the next PSC meeting is in about three weeks.
>>
>> If the plan is approved I'll set up monthly meetings to coordinate the 
>> efforts.
>>
>> Kind regards.
>>
>>
>> On Wed, Mar 15, 2023 at 9:49 AM Nzikou, Michel
>>  wrote:
>> >
>> > I am okay to land sometime if there are any parts I can contribute too.
>> > FYI been working with Qgis about 7 Months. Thanks
>> >
>> > On Wednesday, March 15, 2023, Julien Cabieces via QGIS-Developer 
>> >  wrote:
>> >>
>> >>
>> >> Hi,
>> >>
>> >> Thank you for the meeting minutes!
>> >>
>> >> I'm already planning to continue the effort in
>> >> porting/fixing code for Qt6 in the next months using Oslandia own
>> >> funding, so I'm candidate to join the working group.
>> >>
>> >> > ND: major missing bit: python support. Bulk of the tests are thus not 
>> >> > running
>> >> > Packaging issues - Sandro Mani looking into python stuff for fedora
>> >> > (QVariant issues)
>> >>
>> >> Is there a reason why we are switching from ubuntu for Qt5 builds to
>> >> fedora for Qt6 builds ? Because there is already PyQt6 packages in 
>> >> ubuntu:22.10.
>> >>
>> >> Regards,
>> >> Julien
>> >>
>> >>
>> >>
>> >> > Hi,
>> >> >
>> >> > Here is some feedback about the QGIS QT6 status meeting we had 
>> >> > yesterday.
>> >> >
>> >> > First I'd like to thank all the attendees, it was great to see the
>> >> > excitement and the interest in moving forward with this project.
>> >> >
>> >> > If I may summarize the outcome, we decided that the best way to move
>> >> > forward is to create a working group with all the interested
>> >> > developers and allocate a budget (20K is the proposed budget) in order
>> >> > to find a solution to the main blockers, it is very hard to estimate
>> >> > the effort in advance but we thought that with that budget we will be
>> >> > able to move forward.
>> >> >
>> >> > Any QGIS core developer with experience in the main areas involved and
>> >> > willing to dedicate some time to this effort is eligible and warmly
>> >> > invited to participate in the working group.
>> >> >
>> >> > Here is the link to the minutes:
>> >> >
>> >> > https://docs.google.com/document/d/1Un4Jyz9PO8t2vmEBkUKa187SytM2gsQn-jB6mSqXcvU/
>> >> >
>> >> > This proposal will be discussed at the next PSC meeting.
>> >>
>> >>
>> >> --
>> >>
>> >> Julien Cabieces
>> >> Senior Developer at Oslandia
>> >> julien.cabie...@oslandia.com
>> >> 09.72.52.52.76
>> >> ___
>> >> 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
>> >
>> >
>> >
>> > --
>> > Michel Nzikou, Ph.D.
>> > ASEG WA - President
>> > -
>> >
>>
>>
>> --
>> Alessandro Pasotti
>> QCooperative:  www.qcooperative.net
>> ItOpen:   www.itopen.it
>> ___
>> QGIS-PSC mailing list
>> qgis-...@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
>
>
> --
>
> --
> Andreas Neumann
> QGIS.ORG board member (treasurer)



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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-psc] QGIS QT6 meeting minutes

[Alessandro Pasotti via QGIS-Developer]

Hi Julien,

that's great news and you are welcome!

I'll leave the answer to your question to others, IIRC at the time
fedora was the only distro packaging pyQt6 and SIP.

Sandro Mani certainly knows more about this topic.




On Wed, Mar 15, 2023 at 9:45 AM Julien Cabieces
 wrote:
>
>
> Hi,
>
> Thank you for the meeting minutes!
>
> I'm already planning to continue the effort in
> porting/fixing code for Qt6 in the next months using Oslandia own
> funding, so I'm candidate to join the working group.
>
> > ND: major missing bit: python support. Bulk of the tests are thus not 
> > running
> > Packaging issues - Sandro Mani looking into python stuff for fedora
> > (QVariant issues)
>
> Is there a reason why we are switching from ubuntu for Qt5 builds to
> fedora for Qt6 builds ? Because there is already PyQt6 packages in 
> ubuntu:22.10.
>
> Regards,
> Julien
>
>
>
> > Hi,
> >
> > Here is some feedback about the QGIS QT6 status meeting we had yesterday.
> >
> > First I'd like to thank all the attendees, it was great to see the
> > excitement and the interest in moving forward with this project.
> >
> > If I may summarize the outcome, we decided that the best way to move
> > forward is to create a working group with all the interested
> > developers and allocate a budget (20K is the proposed budget) in order
> > to find a solution to the main blockers, it is very hard to estimate
> > the effort in advance but we thought that with that budget we will be
> > able to move forward.
> >
> > Any QGIS core developer with experience in the main areas involved and
> > willing to dedicate some time to this effort is eligible and warmly
> > invited to participate in the working group.
> >
> > Here is the link to the minutes:
> >
> > https://docs.google.com/document/d/1Un4Jyz9PO8t2vmEBkUKa187SytM2gsQn-jB6mSqXcvU/
> >
> > This proposal will be discussed at the next PSC meeting.
>
>
> --
>
> Julien Cabieces
> Senior Developer at Oslandia
> julien.cabie...@oslandia.com
> 09.72.52.52.76



--
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 QT6 meeting minutes

[Alessandro Pasotti via QGIS-Developer]

Hi Michel,

thank you and welcome!

The next step is to get this plan approved by the PSC (with the
associated budget), the next PSC meeting is in about three weeks.

If the plan is approved I'll set up monthly meetings to coordinate the efforts.

Kind regards.


On Wed, Mar 15, 2023 at 9:49 AM Nzikou, Michel
 wrote:
>
> I am okay to land sometime if there are any parts I can contribute too.
> FYI been working with Qgis about 7 Months. Thanks
>
> On Wednesday, March 15, 2023, Julien Cabieces via QGIS-Developer 
>  wrote:
>>
>>
>> Hi,
>>
>> Thank you for the meeting minutes!
>>
>> I'm already planning to continue the effort in
>> porting/fixing code for Qt6 in the next months using Oslandia own
>> funding, so I'm candidate to join the working group.
>>
>> > ND: major missing bit: python support. Bulk of the tests are thus not 
>> > running
>> > Packaging issues - Sandro Mani looking into python stuff for fedora
>> > (QVariant issues)
>>
>> Is there a reason why we are switching from ubuntu for Qt5 builds to
>> fedora for Qt6 builds ? Because there is already PyQt6 packages in 
>> ubuntu:22.10.
>>
>> Regards,
>> Julien
>>
>>
>>
>> > Hi,
>> >
>> > Here is some feedback about the QGIS QT6 status meeting we had yesterday.
>> >
>> > First I'd like to thank all the attendees, it was great to see the
>> > excitement and the interest in moving forward with this project.
>> >
>> > If I may summarize the outcome, we decided that the best way to move
>> > forward is to create a working group with all the interested
>> > developers and allocate a budget (20K is the proposed budget) in order
>> > to find a solution to the main blockers, it is very hard to estimate
>> > the effort in advance but we thought that with that budget we will be
>> > able to move forward.
>> >
>> > Any QGIS core developer with experience in the main areas involved and
>> > willing to dedicate some time to this effort is eligible and warmly
>> > invited to participate in the working group.
>> >
>> > Here is the link to the minutes:
>> >
>> > https://docs.google.com/document/d/1Un4Jyz9PO8t2vmEBkUKa187SytM2gsQn-jB6mSqXcvU/
>> >
>> > This proposal will be discussed at the next PSC meeting.
>>
>>
>> --
>>
>> Julien Cabieces
>> Senior Developer at Oslandia
>> julien.cabie...@oslandia.com
>> 09.72.52.52.76
>> ___
>> 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
>
>
>
> --
> Michel Nzikou, Ph.D.
> ASEG WA - President
> -
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS QT6 meeting minutes

[Alessandro Pasotti via QGIS-Developer]

Hi,

Here is some feedback about the QGIS QT6 status meeting we had yesterday.

First I'd like to thank all the attendees, it was great to see the
excitement and the interest in moving forward with this project.

If I may summarize the outcome, we decided that the best way to move
forward is to create a working group with all the interested
developers and allocate a budget (20K is the proposed budget) in order
to find a solution to the main blockers, it is very hard to estimate
the effort in advance but we thought that with that budget we will be
able to move forward.

Any QGIS core developer with experience in the main areas involved and
willing to dedicate some time to this effort is eligible and warmly
invited to participate in the working group.

Here is the link to the minutes:

https://docs.google.com/document/d/1Un4Jyz9PO8t2vmEBkUKa187SytM2gsQn-jB6mSqXcvU/

This proposal will be discussed at the next PSC meeting.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Monday 13 March 11:00 CET (GMT+1): QGIS QT6 build status & roadmap meeting

[Alessandro Pasotti via QGIS-Developer]

Hi,

I am sorry there isn't a time that works for all of us, I'm picking
the first choice with the most people available.

The meeting will be Monday 13 March 11:00 CET (GMT+1) on

https://meet.jit.si/QGIS-QT6

Talk to you soon!

--

Here is a copy-paste of my original email:


As most of you are probably aware, a lot of work has been recently
done in order to support QT6 QGIS builds.

During the last PSC meeting we discussed the QGIS QT6 support status
because we would like to start a discussion in order to set up a
roadmap and move forward.

We decided to organize a meeting with all the interested QGIS
contributors to discuss:

- current QT6 build status
- blockers (webkit etc.)
- how to move forward

If you are willing to participate please choose a time that works for
you here  https://doodle.com/meeting/participate/id/enRwEz5e

Here are a few links to the previous discussions:
https://lists.osgeo.org/pipermail/qgis-developer/2022-August/065012.html
https://lists.osgeo.org/pipermail/qgis-psc/2022-August/009864.html



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 QT6 build status & roadmap meeting

[Alessandro Pasotti via QGIS-Developer]

Hi Richard, no, that is 11.00 AM CET time (Europe/Rome (GMT+1:00))

On Thu, Mar 9, 2023 at 3:36 PM Richard Duivenvoorde  wrote:
>
> Hi Allessandro,
>
> Very interested! Please let us know what the outcome of the doodle is,
> so I/others can try to be there/lurk if possible (my input will not be enough 
> to influence the date/time,
> but I would be really happy to try to make the build work on Debian :-) , I 
> failed last time I tried ).
>
> Am I right to conclude this is (for europe) an afternoon/evening session 
> (11AM-12PM)?
>
> All: Thanks for this work and good luck with all tough hurdles/decisions!
>
> Richard Duivenvoorde
>
> On 3/9/23 11:37, Alessandro Pasotti via QGIS-Developer wrote:
> > Hi,
> >
> > As most of you are probably aware, a lot of work has been recently
> > done in order to support QT6 QGIS builds.
> >
> > During the last PSC meeting we discussed the QGIS QT6 support status
> > because we would like to start a discussion in order to set up a
> > roadmap and move forward.
> >
> > We decided to organize a meeting with all the interested QGIS
> > contributors to discuss:
> >
> > - current QT6 build status
> > - blockers (webkit etc.)
> > - how to move forward
> >
> > If you are willing to participate please choose a time that works for
> > you here  https://doodle.com/meeting/participate/id/enRwEz5e
> >
> > Here are a few links to the previous discussions:
> > https://lists.osgeo.org/pipermail/qgis-developer/2022-August/065012.html
> > https://lists.osgeo.org/pipermail/qgis-psc/2022-August/009864.html
> >
> > Thank you!
> >
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS QT6 build status & roadmap meeting

[Alessandro Pasotti via QGIS-Developer]

Hi,

As most of you are probably aware, a lot of work has been recently
done in order to support QT6 QGIS builds.

During the last PSC meeting we discussed the QGIS QT6 support status
because we would like to start a discussion in order to set up a
roadmap and move forward.

We decided to organize a meeting with all the interested QGIS
contributors to discuss:

- current QT6 build status
- blockers (webkit etc.)
- how to move forward

If you are willing to participate please choose a time that works for
you here  https://doodle.com/meeting/participate/id/enRwEz5e

Here are a few links to the previous discussions:
https://lists.osgeo.org/pipermail/qgis-developer/2022-August/065012.html
https://lists.osgeo.org/pipermail/qgis-psc/2022-August/009864.html

Thank you!

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Additional python modules

[Alessandro Pasotti via QGIS-Developer]

Hi,

last time I checked there wasn't, mainly because the PIP API wasn't exposed.

The standard way to go is ask Juergen to add the packages you need to
the QGIS package recipes.


On Fri, Feb 24, 2023 at 4:24 PM Yoann Quenach de Quivillic via
QGIS-Developer  wrote:
>
> Hello everyone,
>
> I'm working on a new feature targeting 3.32 to reformat code written in the 
> Python Console Editor : https://github.com/qgis/QGIS/pull/51733. It works 
> great, but it requires additional python packages to be installed (namely 
> black / autopep8 / isort).
>
> Is there a reliable cross platform way we can use to distribute additional 
> python packages alongside QGIS?
>
> I could rewrite my PR to enable this feature only if the required modules are 
> installed, but it seems kind of a shame... An alternative would be, as 
> discussed in 
> (https://github.com/qgis/QGIS/pull/51733#issuecomment-1434646910) to provide 
> the end user a way to dynamically install modules as needed.
>
> Any thoughts?
> Thanks,
>
> --
> Yoann Quenach de Quivillic
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Triage permission (add labels to issues)

[Alessandro Pasotti via QGIS-Developer]

done.

On Wed, Feb 22, 2023 at 2:04 PM Yoann Quenach de Quivillic via
QGIS-Developer  wrote:
>
> Hello everyone,
>
> I'm not sure it is the right channel to discuss this, but I'd like to get 
> triage permission on qgis/QGIS (add labels to issues) for my account 
> (https://github.com/YoannQDQ). How can I get that?
>
> Thanks, and have a nice day!
>
> --
> Yoann Quenach de Quivillic
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Call for emergency 3.22 release

[Alessandro Pasotti via QGIS-Developer]

+1 for immediate release from me.

On a side note (because I sympathize thinking about what I would feel
if it was a commit of mine) : Julien is doing an amazing job, a
mistake can happen to anyone.

On Thu, Feb 2, 2023 at 7:38 AM Andreas Neumann via QGIS-Developer
 wrote:
>
> Hi Nyall,
>
> I agree, this is a pretty nasty one. Jürgen - can we release another release 
> soon?
>
> Thank you Even for your reflections on the code patterns involved. I trust 
> that the core devs will discuss and suggest improvements in our 
> documentation/guidelines in order to avoid similar cases in the future.
>
> Thank you for your response.
>
> Andreas
>
> On 2023-02-02 02:19, Nyall Dawson via QGIS-Developer wrote:
>
> Hi PSC/list,
>
> I came across this horrible regression during bug hunting today:
> https://github.com/qgis/QGIS/pull/51703
>
> If you load a project with any broken layers and then hover over the
> layer in the layer tree, QGIS will instantly crash. It's a regression
> caused by https://github.com/qgis/QGIS/pull/50256, and unfortunately
> that PR was backported to 3.22 and accordingly the crash present in
> the final release of 3.22.
>
> Given the extreme severity of this crash I believe we should be
> pushing out another unplanned 3.22 patch release, as we cannot leave
> the final 3.22 LTR with such a nasty regression in place.
>
> 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
>
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] disabling mingw64 builds

[Alessandro Pasotti via QGIS-Developer]

Great!

Thank you!

On Fri, Jan 27, 2023 at 1:18 PM Jürgen E. Fischer via QGIS-Developer
 wrote:
>
> Hi Ale,
>
> On Fri, 27. Jan 2023 at 11:29:14 +0100, Alessandro Pasotti via QGIS-Developer 
> wrote:
> > Fixing it would be a better option.
>
> Done already.
>
>
> 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)  Germany IRC: jef on Libera|OFTC
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] disabling mingw64 builds

[Alessandro Pasotti via QGIS-Developer]

Fixing it would be a better option.

Maybe Sandro can help.

Il ven 27 gen 2023, 10:57 Denis Rouzaud via QGIS-Developer <
qgis-developer@lists.osgeo.org> ha scritto:

> Hi all,
>
> The mingw64 builds have been constantly failing for a couple of days.
>
> I have a PR open to disable them https://github.com/qgis/QGIS/pull/51611
>
> If there are no objections, I will merge this.
>
> Cheers,
> Denis
> ___
> 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] How to see queries sent to GPKG layer for debugging

[Alessandro Pasotti via QGIS-Developer]

I don't, sorry.

On Mon, Dec 19, 2022 at 1:07 PM Vedran Stojnović  wrote:
>
> Hi Alessandro,
>
> thank you very much for info.
> Do you maybe know any workaround for this in the meanwhile?
> One of my coworkers is currently on hold because of this.
>
> pon, 19. pro 2022. u 12:33 Alessandro Pasotti  napisao je:
>>
>> It's coming: see https://github.com/OSGeo/gdal/pull/6837
>>
>> On Mon, Dec 19, 2022 at 12:28 PM Vedran Stojnović via QGIS-Developer
>>  wrote:
>> >
>> > Hi,
>> >
>> > I am trying to find source of some bug related to data input via form.
>> > I have set up some triggers in DB which are not executed if data is edited 
>> > through QGIS, but if I change manually in SQLite than it works as expected.
>> >
>> > How can I see what queries are sent to GPKG database?
>> > I tried to open Debugging/Development Tools Panel and enabled "Record Log" 
>> > but nothing is shown there.
>> >
>> > --
>> > Kind regards,
>> > Vedran Stojnović.
>> > ___
>> > 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
>>
>>
>>
>> --
>> Alessandro Pasotti
>> QCooperative:  www.qcooperative.net
>> ItOpen:   www.itopen.it
>
>
>
> --
> Srdačan pozdrav,
> Vedran Stojnović.



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] How to see queries sent to GPKG layer for debugging

[Alessandro Pasotti via QGIS-Developer]

It's coming: see https://github.com/OSGeo/gdal/pull/6837

On Mon, Dec 19, 2022 at 12:28 PM Vedran Stojnović via QGIS-Developer
 wrote:
>
> Hi,
>
> I am trying to find source of some bug related to data input via form.
> I have set up some triggers in DB which are not executed if data is edited 
> through QGIS, but if I change manually in SQLite than it works as expected.
>
> How can I see what queries are sent to GPKG database?
> I tried to open Debugging/Development Tools Panel and enabled "Record Log" 
> but nothing is shown there.
>
> --
> Kind regards,
> Vedran Stojnović.
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QgsSettings

[Alessandro Pasotti via QGIS-Developer]

Hi Denis,

it's been a while but IIRC the goal was to have a drop-in replacement
of QSettings, that's probably why I recreated the same ctors.




On Fri, Dec 9, 2022 at 2:48 PM Denis Rouzaud  wrote:
>
> Hi all,
>
> While working on the refactoring of settings (see 
> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/245), I am thinking 
> about deprecating the QgsSettings class and directly integrate its 
> functionality within QgsSettingsRegistry.
>
> I would need a bit of help to understand the rationale behind QgsSettings.
>
> The use of global settings is pretty clear to me and migrating this is ok.
>
> I am wondering about the different constructors 
> (https://api.qgis.org/api/3.28/classQgsSettings.html) which correspond to the 
> different constructors of QSettings.
> While it makes sense to have these constructors, I don't see them used 
> anywhere in the code. So, it means that they are never used within QGIS 
> application.
> I am wondering why QgsSettings isn't used with a static instance.
>
> So, are these constructors really used and meaningful?
> Would it make sense to have 2 static instances of QSettings (1 user, 1 
> global)?
>
> Many thanks for any input.
> Best wishes,
>
> Denis



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Question on current_value() expression in the context of filtering relation reference combo boxes

[Alessandro Pasotti via QGIS-Developer]

Sorry, I just realized that you are using relation-reference widgets
and not value-relation widgets.

I don't think that the current_(parent)_value will work in that case,
it wasn't implemented.

Cheers

On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
 wrote:
>
> Hi,
>
> In one of my form setups,  I would like to filter one relation reference 
> widget combo box with a filter expression based on the selected entry of 
> another relation reference value.
>
> A static filter like:
>
> szenario_art = 'Brand'
>
> works as expected and it returns the filtered values - but as soon as I try 
> to base it on the value of another relation reference widget, it fails ...
>
> I tried
>
> szenario_art = current_value('szenario_art')
>
> but no records get selected.
>
>
> Questions:
>
> Does the current_value() return the "internal value" or the "human readable" 
> value?
> Do I have to eval() something in the filter expression?
> Is there a way to test "current_value" somehow? I tried to write the changed 
> value into another text widget (with default values on update), but it will 
> always return "NULL". In the expression editor, I also always get "NULL" in 
> the preview.
>
> Thank you for your help,
>
> Andreas
>
>
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Question on current_value() expression in the context of filtering relation reference combo boxes

[Alessandro Pasotti via QGIS-Developer]

You probably need to use current_parent_value() to get the value of
the "parent" form in case of embedded sub-forms.

On Tue, Dec 6, 2022 at 4:34 PM Andreas Neumann  wrote:
>
> Hi Ale,
>
> Thanks for your information.
>
> What if both tables have the same column names? Would that also work?
>
> In my case the related table contains a field called "szenario_art" and the 
> parent table also has the same field name.
>
> Can one assume that a field left of the operator will be in the related table 
> while fields right of the operator are in the parent table? Or how would the 
> expression distinguish the fields if they appear in both tables?
>
> Thanks,
> Andreas
>
> On 2022-12-06 16:29, Alessandro Pasotti wrote:
>
> On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
>  wrote:
>
>
> Hi,
>
> In one of my form setups,  I would like to filter one relation reference 
> widget combo box with a filter expression based on the selected entry of 
> another relation reference value.
>
> A static filter like:
>
> szenario_art = 'Brand'
>
> works as expected and it returns the filtered values - but as soon as I try 
> to base it on the value of another relation reference widget, it fails ...
>
> I tried
>
> szenario_art = current_value('szenario_art')
>
> but no records get selected.
>
>
> Questions:
>
> Does the current_value() return the "internal value" or the "human readable" 
> value?
>
>
> The internal value.
>
> Do I have to eval() something in the filter expression?
>
>
> No.
>
> Is there a way to test "current_value" somehow? I tried to write the changed 
> value into another text widget (with default values on update), but it will 
> always return "NULL". In the expression editor, I also always get "NULL" in 
> the preview.
>
>
> That should work, the current_value returns the current value of the
> feature being edited in the context of the form, this includes any
> change that took place in the form.
>
> You might get null values in the editor and the preview because there
> is no form context in that case.
>
>
>
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Question on current_value() expression in the context of filtering relation reference combo boxes

[Alessandro Pasotti via QGIS-Developer]

On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
 wrote:
>
> Hi,
>
> In one of my form setups,  I would like to filter one relation reference 
> widget combo box with a filter expression based on the selected entry of 
> another relation reference value.
>
> A static filter like:
>
> szenario_art = 'Brand'
>
> works as expected and it returns the filtered values - but as soon as I try 
> to base it on the value of another relation reference widget, it fails ...
>
> I tried
>
> szenario_art = current_value('szenario_art')
>
> but no records get selected.
>
>
> Questions:
>
> Does the current_value() return the "internal value" or the "human readable" 
> value?

The internal value.

> Do I have to eval() something in the filter expression?

No.

> Is there a way to test "current_value" somehow? I tried to write the changed 
> value into another text widget (with default values on update), but it will 
> always return "NULL". In the expression editor, I also always get "NULL" in 
> the preview.

That should work, the current_value returns the current value of the
feature being edited in the context of the form, this includes any
change that took place in the form.

You might get null values in the editor and the preview because there
is no form context in that case.




-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 python action with Expression problem

[Alessandro Pasotti via QGIS-Developer]

On Mon, Nov 7, 2022 at 11:59 AM Andreas Neumann  wrote:
>
> Hi Ale,
>
> Thanks for the hint!

You're welcome!

the formScope adds another feature: the "form" feature which
represents a virtual feature with the values taken from the current
form status.

>
> With
>
> expContext.setFeature(form.feature())
>
> it seems to work.
>
> I was assuming that adding the formScope would also add the feature context 
> ... but apparently not.
>
> Now I can continue adding the more complex expression.
>
> Thank you for your help!
>
> Andreas
>
> On 2022-11-07 11:46, Alessandro Pasotti wrote:
>
> You need to set the feature if you want to access the feature fields.
>
> QgsExpressionContext::setFeature( const QgsFeature  )
>
> If you want the form feature values you need to use the current_value
> or the current_feature functions.
>
> Regards.
>
> On Mon, Nov 7, 2022 at 11:27 AM Andreas Neumann via QGIS-Developer
>  wrote:
>
>
> Hi,
>
> I am trying to implement a Python action in "form" and "feature" action scope 
> that uses a QGIS expression, but fail to get a valid expression calculation.
>
> Here is my code so far:
>
> from qgis.PyQt.QtWidgets import *
> from qgis.core import QgsMessageLog
>
> expContext = QgsExpressionContext()
> expContext.appendScopes(QgsExpressionContextUtils.globalProjectLayerScopes(form.layer()))
> expContext.appendScope(QgsExpressionContextUtils.formScope(form.feature(),'SingleEditMode'))
>
> exp = QgsExpression('t_id')
>
> expResult = exp.evaluate(expContext)
> QgsMessageLog.logMessage('Expression Result=' + str(expResult))
>
>
> So even the most basic expression (getting a field value) will not work in my 
> code. I always get "None" as a result.
>
> Any idea what is missing? Am I missing a certain scope or an import statement?
>
> Thank you very much for any hints what might be wrong here ...
>
> Andreas
>
> ___
> 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
>
>
>
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 python action with Expression problem

[Alessandro Pasotti via QGIS-Developer]

You need to set the feature if you want to access the feature fields.

QgsExpressionContext::setFeature( const QgsFeature  )

If you want the form feature values you need to use the current_value
or the current_feature functions.

Regards.

On Mon, Nov 7, 2022 at 11:27 AM Andreas Neumann via QGIS-Developer
 wrote:
>
> Hi,
>
> I am trying to implement a Python action in "form" and "feature" action scope 
> that uses a QGIS expression, but fail to get a valid expression calculation.
>
> Here is my code so far:
>
> from qgis.PyQt.QtWidgets import *
> from qgis.core import QgsMessageLog
>
> expContext = QgsExpressionContext()
> expContext.appendScopes(QgsExpressionContextUtils.globalProjectLayerScopes(form.layer()))
> expContext.appendScope(QgsExpressionContextUtils.formScope(form.feature(),'SingleEditMode'))
>
> exp = QgsExpression('t_id')
>
> expResult = exp.evaluate(expContext)
> QgsMessageLog.logMessage('Expression Result=' + str(expResult))
>
>
> So even the most basic expression (getting a field value) will not work in my 
> code. I always get "None" as a result.
>
> Any idea what is missing? Am I missing a certain scope or an import statement?
>
> Thank you very much for any hints what might be wrong here ...
>
> Andreas
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Writing a driver plugin for a custom vector format

[Alessandro Pasotti via QGIS-Developer]

Have look to 
https://github.com/qgis/QGIS/blob/master/tests/src/python/provider_python.py

Hope this helps

On Wed, Sep 7, 2022 at 4:59 PM Martijn Reening via QGIS-Developer
 wrote:
>
> Hi QGIS community,
>
> I am currently working with a custom file format that contains geometry 
> information. The format contains mixed geometry types and some style and meta 
> information.
>
> The geometry is simple to map onto WKT and I have a parser for Python. I 
> would like to integrate this into a QGIS plugin. It seems however that 
> writing drivers for file formats is not really documented in the PyQGIS 
> Developer Cookbook.
>
> My questions are therefore:
>
> Is it possible to introduce support for a custom file format through a plugin?
> At what level should I integrate this? It seems that most formats are handled 
> through GDAL, which has its own plugin system. I would rather have it 
> installable through the QGIS interface
>
> Are there any examples of similar formats (KML/GML) that are handled this way?
>
> Kind regards,
>
> Martijn Reening
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Work on QgsAbstractDatabaseProviderConnection for MS SQL Server

[Alessandro Pasotti via QGIS-Developer]

Hi Bo,

I could have a look but I need a few days...

On Fri, Sep 2, 2022 at 12:08 PM Bo Victor Thomsen via QGIS-Developer
 wrote:
>
> Hi List -
>
> I am working on a plugin that's is using for connections 
> (QgsAbstractDatabaseProviderConnection) to several types of databases, 
> including Postgres, GeoPackage and MS SQLServer.
>
> I was hoping to use the method "createSqlVectorLayer"  for converting some 
> fairly complex SQL queries into QGIS vector layers. This works super nice for 
> Postgres and GeoPackage. However the current version (QGIS 3.26) doesn't 
> support this method for MS SQLServer. As illustrated in this piece of code:
>
> conns = 
> QgsProviderRegistry.instance().providerMetadata('mssql').connections(False)
> conn = conns['geodata @ localhost'] # SQL server connection
> capabilities = conn.capabilities()
> print(bool(capabilities & QgsAbstractDatabaseProviderConnection.SqlLayers))
>
> The last statement shows "False" for MS SqlServer connections, indicating the 
> missing functionality. (QGIS ver. 3.26 or older)
>
>
> My first question is: Has there been done any work on this for MS SQL Server 
> connections in QGIS master (next version) ?
>
> The second question: Is it possible for someone in the group of Core 
> developers to provide me with a ballpark figure for implementing the missing 
> functionality for the mssql driver ??
>
> To be specific: get method "createSqlVectorLayer" to work for MS SQL Server 
> connections.
>
> If somebody steps up to the challenge I will send the information to my 
> customers so they can consider making QGIS better instead of paying me for an 
> ugly workaround.
>
>
> Med venlig hilsen / Kind regards
>
> Bo Victor Thomsen
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Is it possible to make QGIS show the fired queries to databases in Debugging Tools?

[Alessandro Pasotti via QGIS-Developer]

On Fri, Jul 29, 2022 at 12:30 PM Bo Victor Thomsen via QGIS-Developer
 wrote:
>
> Nice to know  -
>
> What about GeoPackage ? Is it technically difficult or was is not

The first: GPKG uses GDAL which internally calls SQLite C code, and
there is no interface to retrieve the actual SQL.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Is it possible to make QGIS show the fired queries to databases in Debugging Tools?

[Alessandro Pasotti via QGIS-Developer]

Hi,

It is currently implemented for PG, Oracle, MSSQL and spatialite.


On Fri, Jul 29, 2022 at 10:48 AM Andreas Neumann via QGIS-Developer
 wrote:
>
> Hi Richard,
>
> Yes, this happens from time to time to me as well, that I am looking for a 
> new feature and it turns out that it is already implemented ;-)
>
> As far as I know, it is only implemented for Postgis so far - other DB 
> engines could be added, if someone cares about it.
>
> Greetings,
>
> Andreas
>
> On 2022-07-29 10:41, Richard Duivenvoorde via QGIS-Developer wrote:
>
> Duh...
>
> Thanks Andreas, how can I have missed this...
>
> Too many features syndrome I think :-)
>
> Thanks, working great (at least for Postgis, not other db around here...)
>
> Regards,
>
> Richard
>
> On 7/29/22 10:34, Andreas Neumann wrote:
>
> Hi Richard,
>
> This should already be available in the debugging tools --> Query Logger
>
> It was a recent QGIS grant project and developed by elpaso.
>
> Greetings,
>
> Andreas
>
> On 2022-07-29 10:25, Richard Duivenvoorde via QGIS-Developer wrote:
>
> Doing some Postgis work with QGIS, I often asked myself what queries QGIS is 
> firing to the database.
> I can off course log that in the database, but I was wondering if QGIS had 
> some 'signal' which could be use to pass the queries used to the Debugging 
> Tools?
>
> I skimmed QgsDataProvider, QgsVectorDataProvider and the Postgres provider, 
> but I think these are not so communicative as the QGIS Network request, so I 
> think it will be harder then I hoped... as always :-(
>
> OR am I missing some signal which could be used?
>
> Regards,
>
> Richard Duivenvoorde
>
> PS else this is just a nice feature request for the Debugging Tools :-)
> ___
> 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 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] API endpoints to QGIS

[Alessandro Pasotti via QGIS-Developer]

Hi,

the answer you've got is correct: it is not currently implemented,
only HTTP Basic is available.

This leaves you with a few options:

1. write a Python plugin that implements in python a vector data provider.
2. implement in QGIS core (in C++) the support for other
authentication methods for the GDAL vector data provider (OGR).

Here is an example of a proof of concept python vector data provider:
https://github.com/qgis/QGIS/blob/master/tests/src/python/provider_python.py

Best regards.

On Mon, Jul 4, 2022 at 1:48 PM Marin M via QGIS-Developer
 wrote:
>
> hi,
>
> I have asked this question on Stack Exchange. I havent  got so many answers.
>
> Calling API end points in QGIS - Geographic Information Systems Stack Exchange
>
> So since this API endpoints calling  might not be a classical user/business  
> case in QGIS ,I thought to ask here, If there is a way to  get this into QGIS 
> ?
>
>
> And if there are no current possibilities for that, might there be something 
> like this coming in the future releases of QGIS?
>
> regards
>
> Marin Mirosevic
>
>
>
>
>
>
>
>
>
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Time for db manager to become an "opt-in" plugin?

[Alessandro Pasotti via QGIS-Developer]

On Wed, Jun 22, 2022 at 8:52 AM Nyall Dawson  wrote:
>
> On Wed, 22 Jun 2022 at 16:47, Alessandro Pasotti  wrote:
> >
> > I am +1 (of course).
> >
> > Another notable feature gap is virtual layers.
>
> What's the gap there? Can't that all be done from the "New Virtual
> Layer" dialog?


Not much of a functional gap, more a GUI one, virtual layers are not
listed in the browser: there is no icon for them like there is in
DB-manager.


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Time for db manager to become an "opt-in" plugin?

[Alessandro Pasotti via QGIS-Developer]

I am +1 (of course).

Another notable feature gap is virtual layers.

Kind regards.

On Wed, Jun 22, 2022 at 2:43 AM Nyall Dawson via QGIS-Developer
 wrote:
>
> Hi list,
>
> I wanted to raise the discussion around potentially demoting the DB Manager 
> plugin to become an opt-in, not installed by default plugin available from 
> the QGIS plugin repository only.
>
> It's likely no surprise to anyone on this list, but there's been a multi-year 
> effort (mostly thanks to Alessandro!) to move all the important functionality 
> of db manager over to the QGIS browser. This was driven by a number of 
> factors:
>
> - It was confusing and messy to expose database management tools through two 
> completely separate parts of the QGIS interface
> - The DB Manager tools are written in provider-specific ways, and don't use 
> generic QGIS database/provider API calls. As a result there's a lot of 
> duplicate code there, and db manager doesn't gain the benefits of new data 
> provider features. (E.g. only a subset of the databases supported by QGIS and 
> the browser management tools are available for management in db manager)
> - The DB Manager functionality wasn't available for other parts of 
> QGIS/plugins/scripts/etc to reuse, whereas the browser functionality is all 
> nicely exposed to PyQGIS and is used by other parts of QGIS, eg. processing 
> tools.
> - The Python code implementing db manager is fragile, and is subject to 
> semi-frequent regressions/breakage (through no fault of the authors -- it's 
> just the nature of complex python applications which aren't soaked in unit 
> tests)
>
> I'd say we've reached a stage where the browser now offers all the common 
> functionality also available in db manager, and we can start to seriously 
> discuss the future of the plugin.
>
> My personal view is that we should demote the plugin to a 
> community-maintained, non-officially supported plugin available only through 
> the QGIS plugin repositories, and remove it from the default QGIS install.
>
> Thoughts/discussion welcome :)
>
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] CDash still not working

[Alessandro Pasotti via QGIS-Developer]

On Fri, Jun 10, 2022 at 9:00 PM Sandro Santilli  wrote:
>
> On Fri, Jun 10, 2022 at 06:30:43PM +0200, Alessandro Pasotti via 
> QGIS-Developer wrote:
> > Hi,
> >
> > CDash submission from CI does work but the page shows no tests and no
> > failures, this makes it very hard to understand why some image_diff
> > tests are failing.
>
> I filed this issue yesterday:
> https://github.com/qgis/QGIS/issues/48939

Sorry I missed that, thank you for fixing it.

>
> Maybe you want to add your case there too ?

Done.

>
> Incidentally: is the produced .html supposed to be left locally, when
> running the tests locally ? We now have a .ci/run_tests.sh script that
> is supposed to run all the tests in the same docker envionment as the
> CI so it would be handy to debug this.
>
> Beside, in order for .ci/run_tests.sh to work in a worktree merging
> this pull request would be needed: https://github.com/qgis/QGIS/pull/48752
> (your review is welcome, to finalize it)
>

I'll have a look, thank you.

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] CDash still not working

[Alessandro Pasotti via QGIS-Developer]

Hi,

CDash submission from CI does work but the page shows no tests and no
failures, this makes it very hard to understand why some image_diff
tests are failing.

See: https://tinyurl.com/23g4n4c  from
https://github.com/qgis/QGIS/runs/6820302033?check_suite_focus=true

Does anyone know how to fix that?


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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-Documentation fails to build

[Alessandro Pasotti via QGIS-Developer]

Hi,

I cannot make promises, but if I'm allowed to spend the paid bugfixing
hours to fix this I think I could have a look.

Cheers

On Thu, May 19, 2022 at 12:06 PM DelazJ via QGIS-Developer
 wrote:
>
> Hi,
> well...
> For your information, I disabled the doctest github action, to stop getting 
> annoyed by (unrelated) failure messages for each interaction with the 
> repository.
> That also means no more checks for the PyQGIS Cookbook changes (which 
> includes this recent pull request), until we get a fix.
>
> Greetings,
> Harrissou
>
> Le lun. 9 mai 2022 à 16:35, DelazJ  a écrit :
>>
>> Hi,
>> Thanks again Richard for testing.
>> Any chance someone else gives it a look, please? Thanks.
>>
>> Regards,
>> Harrissou
>>
>> Le mar. 3 mai 2022 à 20:44, Richard Duivenvoorde via QGIS-Developer 
>>  a écrit :
>>>
>>> On 5/3/22 11:35, DelazJ via QGIS-Developer wrote:
>>> > Hi devs,
>>> > The "doctest" workflow in QGIS-Documentation repository is again broken. 
>>> > We are getting a segmentation fault [0]. This might have begun at least 5 
>>> > days ago, only on master branch. The 3.22 doctest passes.
>>> > If someone can give it a look, it will be much appreciated. Thanks.
>>>
>>> Hi Harrissou,
>>>
>>> I tried looking into it...
>>>
>>> A normal local build is fine... (so in a VENV with the REQUIREMENTS.txt of 
>>> QGIS-Website, calling "make html")
>>> But that does not build the doc tests (the python code in the cookbook is 
>>> tested in that)
>>>
>>> Then  I tried on my local machine, what I see in the CI log:
>>>
>>> make -f docker.mk doctest
>>>
>>> and that fails with exact the same messages, except it looks like it 
>>> crashes on random parts of the cookbook tests
>>>
>>> @devs can anybody of you make something from the stacktrace?
>>>
>>> SIP related?
>>>
>>> Missing dependency?
>>>
>>> Any hints appreciated
>>>
>>> Regards,
>>>
>>> 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
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS Enhancement: Database metadata storage

[Alessandro Pasotti via QGIS-Developer]

Hi,

I have added a QEP to allow metadata (QMD) storage into client-server DBs.

Please have a look tohttps://
github.com/qgis/QGIS-Enhancement-Proposals/issues/250

Comments welcome!

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QGIS Enhancement: Drag and drop form actions: expose QgsAttributeForm object to Python

[Alessandro Pasotti via QGIS-Developer]

Hi,

I have added a QEP for drag and drop form actions: expose QgsAttributeForm
object to Python

please have a look to:
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/251

Comments are welcome!

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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-user] Questions of a newbie starting with QGIS Server

[Alessandro Pasotti via QGIS-Developer]

Hi,

As Richard mentioned, the old XML-based OGC WMS/WFS/WCS & C. protocols are
plain API protocols and do not provide a full browseable website, they were
designed for machine2machine communications.

OAPIF (AKA WFS3) provides a full website though, but the protocol mandates
URL rewriting, which means that it won't work out of the box unless you
configure your web server to transform an URL to instruct QGIS server which
QGIS project you want to actually serve.

The other option, as Rosa suggestd is to use the new QGIS server catalog,
is also requires rewrite of the URL but a much simpler one because the
catalog itself takes care of creating rewrite rules for all the QGIS
projects that are listed in one of more directories or DB connections for
QGIS projects stored into a PG DB.

I'm not sure about windows, but you might also have a look at the
standalone development server, it integrates a web server and it is
supposed to work out of the box with (almost) zero configuration.

Cheers


On Thu, Apr 21, 2022 at 9:53 AM Aguilar Bolivar, Rosa (UT-ITC) via
QGIS-Developer  wrote:

> Hi, Harrisou
>
> You could try the catalog (
> https://docs.qgis.org/3.22/en/docs/server_manual/catalog.html) to explore
> your projects.
> I also used to the catalog to check the configuration of my projects,
> e.g., that the server had access to the sources (DB), etc.
>
> Best regards,
>
> Rosa
>
>
>
> -Original Message-
> From: Qgis-user  On Behalf Of Richard
> Duivenvoorde via Qgis-user
> Sent: Wednesday, April 20, 2022 8:24 PM
> To: Harrissou s. ; qgis-u...@lists.osgeo.org;
> qgis-developer@lists.osgeo.org
> Subject: Re: [Qgis-user] [QGIS-Developer] Questions of a newbie starting
> with QGIS Server
>
> Hi Harrissou,
>
> I think your pretty close :-)
>
> Some remarks from the times I installed on Windows:
> - I used a vanilla apache installer from https://www.apachelounge.com/
> - indeed used the httpd.conf from osgeo4w to set all paths and env vars,
> VERY convenient
> - are you sure the Qt vs qt is an issue? Thought Windows paths were not
> case sensitive?
>
> The GDAL_DATA path you will need when you use for example the ECW or other
> drivers QGIS_AUTH_DB_DIR_PATH is maybe only needed when you have a project
> which uses authentication profiles? Others?
>
> When you have a WMS/WFS server running normally you do not have a web app
> yet.
> You either use the WMS of WFS as datasource in QGIS (or other clients) or
> you use OpenLayer/Leaflet to create an app in a browser using javascript.
>
> Alessandro also created a landing page for WFS3/OGC API:
> https://docs.qgis.org/3.22/en/docs/server_manual/services/ogcapif.html
> but I found that sometimes tricky to setup...
>
> Maybe others can share more info/experience
>
> Regards,
>
> Richard Duivenvoorde
>
>
>
>
> On 4/20/22 18:58, Harrissou s. via QGIS-Developer wrote:
> > Hi QGISers (sorry for cross-posting)
> >
> > I'm trying to setup a QGIS Server... on Windows and I'd like to share
> > some suggestions/issues I faced in the process and ultimately ask for
> > help on a bigger issue.
> > I'm following the QGIS documentation instructions [0] and took the
> > opportunity to update the docs[1][2], given that osgeo4w provides
> > means to install apache. Review welcome, thanks.
> >
> > In the docs, it is suggested to add at the end of the httpd.conf file
> > a set of variables. But I notice that *most* of them are already set
> > in the httpd_qgis.conf file that is #included at the end of the
> > httpd.conf file. I hence ignored the addition but, Questions:
> > - are the GDAL_DATA and QGIS_AUTH_DB_DIR_PATH necessary for any purpose?
> > - If so, for what? And is it possible (does it make sense) to add them
> > to the httpd_qgis.conf file also?
> >
> > - Issue report: I think there is a typo in the httpd_qgis.conf file
> > setting PATH and QT_PLUGIN_PATH. It mentions apps/qt5/ while it should
> > be apps/Qt5/ (uppercase Q).
> >
> > In my process, I didn't set the gdal or db paths above, I fixed the
> > uppercase typo and when I tested I could get a reply for
> > GetCapabilities as in the docs. Using the QGIS training project, I could
> do a GetMap which successfully returned my map canvas image. Good! My
> server is OP!
> > Well, this is where I got lost. I thought the request would output in
> > the browser some image i could zoom in, pan, maybe identify... But NO,
> > I got a plain, static image. What am I supposed to do next? How can I
> > make my project queryable, zoomable, pannable, anythingable... in a web
> browser?
> > I might have overlooked, but the docs does not seem t provide any
> > information for newbies like me, for the next step. Where should I
> > look now? Your help to get out of this trouble would be much
> appreciated. Thanks.
> >
> > Regards,
> > Harrissou
> >
> > [0]
> > https://docs.qgis.org/3.22/en/docs/server_manual/getting_started.html#
> > installation-on-windows
> >  > 

Re: [QGIS-Developer] Unexpected results from GPKG table query using executeSql()

[Alessandro Pasotti via QGIS-Developer]

Hi Raymond,

I tested your samples and I cannot reproduce the issue on QGIS master and
GDAL 3.4.

Here is the result of my query on your test file:

In [13]: md = QgsProviderRegistry.instance().providerMetadata('ogr')
...: conn =
md.createConnection('/home/x/Scaricati/soilext_db.gpkg', {})
...:
...: # Would expect this to return 4 columns: edit_id, timestamp, name,
can_undo
...: q = 'SELECT * FROM soilexc_edits ORDER BY edit_id'
...: qr = conn.executeSql(q)
...:
...:
...: # This does not return the edit_id field (Which is the PK)
...: for rec in qr:
...: print(rec)
...: '''
...: [PyQt5.QtCore.QDateTime(2022, 3, 1, 0, 0), '', True]
...: [PyQt5.QtCore.QDateTime(2022, 3, 2, 0, 0), '', True]
...: [PyQt5.QtCore.QDateTime(2022, 3, 3, 0, 0), '', True]
...: '''
[1, PyQt5.QtCore.QDateTime(2022, 3, 1, 0, 0), '', True]
[2, PyQt5.QtCore.QDateTime(2022, 3, 2, 0, 0), '', True]
[3, PyQt5.QtCore.QDateTime(2022, 3, 3, 0, 0), '', True]
[4, PyQt5.QtCore.QDateTime(2022, 3, 30, 0, 0), 'purge', False]
[5, PyQt5.QtCore.QDateTime(2022, 3, 31, 0, 0), 'test_new', True]
[6, PyQt5.QtCore.QDateTime(2022, 3, 31, 0, 0), 'test_new', True]
[7, PyQt5.QtCore.QDateTime(2022, 3, 31, 0, 0), 'test_new', True]
[8, PyQt5.QtCore.QDateTime(2022, 3, 31, 0, 0), 'test_new', True]

the edit_id is actually in the results.

Cheers


On Fri, Apr 1, 2022 at 8:28 AM Raymond Nijssen 
wrote:

> For a workaround I found that selecting this way:
>
> SELECT
>edit_id + 0 AS edit_id,
>timestamp,
>name
> FROM
>...
>
> The +0 seem to makes QGIS (or GDAL?) unaware of edit_id being the PK
> field and it does return it. Works both in 3.10 and 3.25.
>
> Raymond
>
>
>
> On 31-03-2022 18:15, Alessandro Pasotti wrote:
> > Hi Raymond,
> >
> > your code looks good.
> >
> > Can you provide a test file?
> >
> > There are some test in core here:
> >
> https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsproviderconnection_ogr_gpkg.py
> > <
> https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsproviderconnection_ogr_gpkg.py
> >
> >
> >
> > On Thu, Mar 31, 2022 at 6:09 PM Raymond Nijssen via QGIS-Developer
> > mailto:qgis-developer@lists.osgeo.org>>
>
> > wrote:
> >
> > Hi devs,
> >
> > I'm working on a plugin that connects to a custom table (without
> > geometry) in a GPKG. When I'm sending queries to it, I keep on
> getting
> > unexpected results. Somehow the id field is missing, sometimes it
> > appears twice (!). And this seems to be different between QGIS 3.10
> and
> > 3.25. (I think it changed since 3.22).
> >
> > Here is a piece of my code:
> >
> >
> > fn = '/path/to/test.gpkg'
> > md = QgsProviderRegistry.instance().providerMetadata('ogr')
> > conn = md.createConnection(fn, {})
> >
> > q = 'select * from test_table;'
> > qr = conn.executeSql(q)
> > print(qr) # No id field in result
> >
> >
> >
> > Before diving into the QGIS code I'd like to check if this is the
> > way to
> > go. Or should i use another way to query that GPKG (SQLite) db?
> >
> >
> > Kind regards,
> > Raymond
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org  QGIS-Developer@lists.osgeo.org>
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > 
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > 
> >
> >
> >
> > --
> > Alessandro Pasotti
> > QCooperative: www.qcooperative.net 
> > ItOpen: www.itopen.it 
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] QEP: Use QgsExpression to set a compiled subset string

[Alessandro Pasotti via QGIS-Developer]

Hi,

I have submitted a QEP for subset strings based on expressions, please have
a look:

https://github.com/qgis/QGIS-Enhancement-Proposals/issues/249

Comments are welcome!

Cheers

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Unexpected results from GPKG table query using executeSql()

[Alessandro Pasotti via QGIS-Developer]

Hi Raymond,

I'll have a look but keep in mind that for GPKG the implementation uses
GDAL/OGR to execute the queries, there might be some fid/id handling that
messes up with the returned fields.



On Fri, Apr 1, 2022 at 8:28 AM Raymond Nijssen 
wrote:

> For a workaround I found that selecting this way:
>
> SELECT
>edit_id + 0 AS edit_id,
>timestamp,
>name
> FROM
>...
>
> The +0 seem to makes QGIS (or GDAL?) unaware of edit_id being the PK
> field and it does return it. Works both in 3.10 and 3.25.
>
> Raymond
>
>
>
> On 31-03-2022 18:15, Alessandro Pasotti wrote:
> > Hi Raymond,
> >
> > your code looks good.
> >
> > Can you provide a test file?
> >
> > There are some test in core here:
> >
> https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsproviderconnection_ogr_gpkg.py
> > <
> https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsproviderconnection_ogr_gpkg.py
> >
> >
> >
> > On Thu, Mar 31, 2022 at 6:09 PM Raymond Nijssen via QGIS-Developer
> > mailto:qgis-developer@lists.osgeo.org>>
>
> > wrote:
> >
> > Hi devs,
> >
> > I'm working on a plugin that connects to a custom table (without
> > geometry) in a GPKG. When I'm sending queries to it, I keep on
> getting
> > unexpected results. Somehow the id field is missing, sometimes it
> > appears twice (!). And this seems to be different between QGIS 3.10
> and
> > 3.25. (I think it changed since 3.22).
> >
> > Here is a piece of my code:
> >
> >
> > fn = '/path/to/test.gpkg'
> > md = QgsProviderRegistry.instance().providerMetadata('ogr')
> > conn = md.createConnection(fn, {})
> >
> > q = 'select * from test_table;'
> > qr = conn.executeSql(q)
> > print(qr) # No id field in result
> >
> >
> >
> > Before diving into the QGIS code I'd like to check if this is the
> > way to
> > go. Or should i use another way to query that GPKG (SQLite) db?
> >
> >
> > Kind regards,
> > Raymond
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org  QGIS-Developer@lists.osgeo.org>
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > 
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > 
> >
> >
> >
> > --
> > Alessandro Pasotti
> > QCooperative: www.qcooperative.net 
> > ItOpen: www.itopen.it 
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Unexpected results from GPKG table query using executeSql()

[Alessandro Pasotti via QGIS-Developer]

Hi Raymond,

your code looks good.

Can you provide a test file?

There are some test in core here:
https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsproviderconnection_ogr_gpkg.py


On Thu, Mar 31, 2022 at 6:09 PM Raymond Nijssen via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi devs,
>
> I'm working on a plugin that connects to a custom table (without
> geometry) in a GPKG. When I'm sending queries to it, I keep on getting
> unexpected results. Somehow the id field is missing, sometimes it
> appears twice (!). And this seems to be different between QGIS 3.10 and
> 3.25. (I think it changed since 3.22).
>
> Here is a piece of my code:
>
>
> fn = '/path/to/test.gpkg'
> md = QgsProviderRegistry.instance().providerMetadata('ogr')
> conn = md.createConnection(fn, {})
>
> q = 'select * from test_table;'
> qr = conn.executeSql(q)
> print(qr) # No id field in result
>
>
>
> Before diving into the QGIS code I'd like to check if this is the way to
> go. Or should i use another way to query that GPKG (SQLite) db?
>
>
> Kind regards,
> Raymond
> ___
> 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
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] [Plugins]: is 'plugin_dependencies' being enforced somewhere?

[Alessandro Pasotti via QGIS-Developer]

Hi Richard,

it is (was?) enforced by the installer, AFAIK there are no checks on the
plugins website.

See:
https://github.com/qgis/QGIS/blob/master/python/pyplugin_installer/plugindependencies.py

Cheers


On Tue, Mar 29, 2022 at 9:02 AM Richard Duivenvoorde via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi Devs,
>
> Reading
>
> https://docs.qgis.org/3.22/en/docs/pyqgis_developer_cookbook/plugins/plugins.html#plugin-metadata
>
> about 'plugin_dependencies' and trying it out in a plugin locally, it
> does not seem to be enforced or so? I added another plugin in metadata
> (it's not clear from docs what name you need to use: plugin name or
> module name) thinking I would see some message somewhere.
>
> Is there some message on plugins.qgis.org?
>
> Or is it just a 'memo' for users who happen to see it in the metadata of
> a plugin, then a dev should notify the user theirselves?
>
> Thanks for any info,
>
> Regards,
>
> 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
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] Override System Locale user interface with American English by Default?

[Alessandro Pasotti via QGIS-Developer]

Hi Alexandre,

it seems reasonable to me but I'd suggest adding a first-time notice and an
option for the user to actually set the system locale, maybe only for the
first QGIS launch.


On Thu, Mar 24, 2022 at 12:12 PM Alexandre Neto via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi,
>
> I have raised this before, but I wanted to ask for it again. Currently,
> QGIS default is not to Override System Locale and use the system's locale
> for User interface.
>
> If the system locale language happens to have good and reliable
> translations, this works well, but when the language is incomplete or
> poorly translated, this IMHO poses a problem.
>
> The European Portuguese translation is quite poor, with many errors and
> bad translations. In the end it is sometimes hard to work with the GUI in
> PT_pt. To me the bad thing is it looks bad on the project reputation and
> people (users) read it as a symptom of bad quality software, which is not
> the case.
>
> So, I wanted to suggest if we could have American english as the default
> for the GUI? Would this  be reasonable?
>
> Thanks,
>
> Alexandre Neto
> ___
> 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
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] issue transforming coords from EPSG:4258 'ETRS89' to 4326

[Alessandro Pasotti via QGIS-Developer]

On Mon, Mar 21, 2022 at 8:20 PM Patrick Dunford via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> How do you specify the CRS for the raster?
>
> I know that you can assign this in the Qgis software but there is also
> provision to assign CRS in a sidecar file. Which one takes precedence?
>
>
The sidecar file provides the default CRS when the layer is loaded, you can
override that in QGIS.

But in my case it was a postgres raster layer and the CRS was set
incorrectly in the database itself (no sidecar file).

Kind regards

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] issue transforming coords from EPSG:4258 'ETRS89' to 4326

[Alessandro Pasotti via QGIS-Developer]

t; ID["EPSG",8607]],
> OPERATIONACCURACY[1.0],
> USAGE[
> SCOPE["(null/copy) Approximation for medium and low accuracy
> applications assuming equality between plate-fixed static and earth-fixed
> dynamic CRSs, ignoring static/dynamic CRS differences."],
> AREA["Europe - onshore and offshore: Albania; Andorra; Austria;
> Belgium; Bosnia and Herzegovina; Bulgaria; Croatia; Cyprus; Czechia;
> Denmark; Estonia; Faroe Islands; Finland; France; Germany; Gibraltar;
> Greece; Hungary; Ireland; Italy; Kosovo; Latvia; Liechtenstein; Lithuania;
> Luxembourg; Malta; Moldova; Monaco; Montenegro; Netherlands; North
> Macedonia; Norway including Svalbard and Jan Mayen; Poland; Portugal;
> Romania; San Marino; Serbia; Slovakia; Slovenia; Spain; Sweden;
> Switzerland; United Kingdom (UK) including Channel Islands and Isle of Man;
> Vatican City State."],
> BBOX[32.88,-16.1,84.73,40.18]],
> ID["EPSG",1149],
> REMARK["ETRS89 and WGS 84 are realizations of ITRS coincident to
> within 1 metre. This transformation has an accuracy equal to the
> coincidence figure."]]
>
> So basically ETRS89 and WGS 84 are considered the same with a 1 metre
> accuracy when considering the generic/datum ensemble versions of EPSG:4258
> and EPSG:4326. You might possibly get time-dependent transformations if
> considering one of the ETRF realization and a WGS 84 (G) / ITRF
> realization instead.
>
> Even
> Le 21/03/2022 à 16:56, Alessandro Pasotti via QGIS-Developer a écrit :
>
> Hi,
>
> I'm not sure if this is a local issue on my dev env or if it is a real
> issue, I have a raster layer in EPSG:4258 ('ETRS89') from copernicus and
> the project's CRS is 4326, the transformation silently fails and the raster
> is not reprojected.
>
> The issue can be reproduced from the console too:
>
> ct = QgsCoordinateTransform(QgsCoordinateReferenceSystem(4258),
> QgsCoordinateReferenceSystem(4326),
> QgsProject.instance().transformContext())
>
> ct.transformBoundingBox(QgsRectangle(4153600, 1296000, 500, 200))
>
> ct.isValid()
>
> True
>
> Result:
>
>  199.720603228>
>
> Any ideas?
>
> --
> Alessandro Pasotti
> QCooperative:  www.qcooperative.net
> ItOpen:   www.itopen.it
>
> ___
> QGIS-Developer mailing listqgis-develo...@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> -- http://www.spatialys.com
> My software is free, but my time generally not.
>
>

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] issue transforming coords from EPSG:4258 'ETRS89' to 4326

[Alessandro Pasotti via QGIS-Developer]

Hi,

I'm not sure if this is a local issue on my dev env or if it is a real
issue, I have a raster layer in EPSG:4258 ('ETRS89') from copernicus and
the project's CRS is 4326, the transformation silently fails and the raster
is not reprojected.

The issue can be reproduced from the console too:

ct = QgsCoordinateTransform(QgsCoordinateReferenceSystem(4258),
QgsCoordinateReferenceSystem(4326),
QgsProject.instance().transformContext())

ct.transformBoundingBox(QgsRectangle(4153600, 1296000, 500, 200))

ct.isValid()

True


Result:




Any ideas?

-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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] PostGIS Raster loading extrem long in QGIS 3.16 and 3.22

[Alessandro Pasotti via QGIS-Developer]

Hi,

the reason for the different behavior is that the old QGIS version was
using GDAL to access PG rasters while the new versions uses a QGIS native
data provider which is using ST_SummaryStatsAgg() to calculate statistics,
I believe that this call can become very slow on large rasters and we
should probably reduce the time by using a smaller sample size but this has
to be implemented/fixed yet, feel free to file a ticket on the QGIS bug
tracker.

The good news is the you can still load the raster from QGIS using the GDAL
provider with a connection string that looks like this:  "PG:
dbname={dbname} mode=2 host={host} port={port} table={table}
schema={schema} sslmode=disable"

Hope this helps.

Regards.
___
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