Re: [QGIS-Developer] Maintainance of QGIS Plugin repository
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 <https://plugins.qgis.org/plugins/unapproved/>. 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?
+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!
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)
his. 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 sold >35k > copies of a GPL licensed add on at $39 each. I'm going to go out on a limb > here and guess that that developer's motivation to make their add-on > excellent is considerably higher than the developer of an equivalent QGIS > plugin 藍 (not to mention that their time investment is much more > justifiable). And any ONE of those 35k paid users could have made the plugin > freely available for everyone else... but that hasn't stopped the sales. > > So what does everyone else think? Would there be a THEORETICAL place for a > THEORETICAL paid QGIS plugin marketplace somewhere in the future? Or is there > a better model we could (theoretically 浪) follow to financially reward plugin > developers? > > 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] bare isnan -- why isn't CI catching this?
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
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
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
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
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
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?
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
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
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
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?
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
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
g 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] https://qgis.org/en/site/getinvolved/governance/governance.html > > --strk; > > Libre GIS consultant/developer > https://strk.kbt.io/services.html > _______ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer -- 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] Proposal: Core committer rights for Andrea Giudiceandrea
+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
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
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
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
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?
ldren")::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 Dell XPS 9510, 11th Gen Intel Core i9-11900H @ >>> 2.50GHz 8 cores, 64GB RAM.) >>> >>> So why is it repeatedly making database calls to get the non geometry >>> attributes of that same singular feature? Why can't it just use the cached >>> data instead of making all these wasteful DB queries? >>> >>> And why is it taking so long to delete the vertices? Is it related to all >>> the unnecessary DB queries? >>> >>> > ___ > 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 to enable debugging mode on QGIS start in Win11
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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)
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
+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
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
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
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
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
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
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
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
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
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
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
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
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?
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?
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 <mailto:QGIS-Developer@lists.osgeo.org> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <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
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?
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?
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
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
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
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
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
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
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 > > <https://docs.qgis.org/3.22/en/docs/server_manual/getting_started.html > > #installation-on-windows> > > [1] reading: > > https://github.com/DelazJ/QGIS-Documentation/blob/installQGISServerWin > > dows/docs/server_manual/getting_started.rst > > <https://github.com/DelazJ/QGIS-Documentation/blob/installQGISServerWi > > ndows/docs/server_manual/getting_started.rst> > > [2] pull-request: https://github.com/qgis/QGIS-Documentation/pull/7508 > > <https://github.com/qgis/QGIS-Documentation/pull/7508> > > > > ___ > > 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-user mailing list > qgis-u...@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > ___ > 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] Unexpected results from GPKG table query using executeSql()
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
> > <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
> >
> >
> >
> > --
> > Alessandro Pasotti
> > QCooperative: www.qcooperative.net <https://www.qcooperative.net>
> > ItOpen: www.itopen.it <http://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
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()
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
> > <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
> >
> >
> >
> > --
> > Alessandro Pasotti
> > QCooperative: www.qcooperative.net <https://www.qcooperative.net>
> > ItOpen: www.itopen.it <http://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()
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?
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?
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
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
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
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
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
Re: [QGIS-Developer] WFS3 API POST PUT Methods
On Thu, Mar 3, 2022 at 9:12 AM Enrico Ferreguti wrote: > > > Il giorno mer 2 mar 2022 alle ore 18:09 Alessandro Pasotti < > apaso...@gmail.com> ha scritto: > >> >> Enrico, >> >> We only accept 4326 currently. >> >> I think we could be more tolerant if the OAPIF extensions allows it, we >> currently allow GET with other CRSs but POST/PUT/PATCH are not implemented >> to handle different CRSs. >> > > What about accepting requests with same CRS of feature source? Could be > this a reasonable feature request? > Yes, I think you could add a custom/vendor crs parameter to the request. Might be worth taking a look at what other server implementations are doing in this regard. > Anyway on REST Interface you did a great job. Thanks. > Thank you! Kind regards. > > >> >> Kind Regards >> >> >> On Wed, Mar 2, 2022 at 1:53 PM Enrico Ferreguti >> wrote: >> >>> Hi QGIS devs, >>> I'm testing the API REST interface for updating a WFS3 and I verified >>> that the new/modified feature had to be expressed in geojson format in >>> EPSG:4326 coordinates regardless of the SRID of the served layer. I >>> verified the behaviour with QGIS server 3.16 LTR and latest 3.22 >>> >>> Is this an issue or a feature due to compliance to OGC or RFC7946 >>> standards? >>> >>> Anyway I found this behaviour very uncomfortable because it obliges to >>> perform preliminarly unaccurate reprojections from javascript/python >>> clients. >>> >>> Best regards. >>> Enrico Ferreguti. >>> _______ >>> 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] WFS3 API POST PUT Methods
Enrico, We only accept 4326 currently. I think we could be more tolerant if the OAPIF extensions allows it, we currently allow GET with other CRSs but POST/PUT/PATCH are not implemented to handle different CRSs. Kind Regards On Wed, Mar 2, 2022 at 1:53 PM Enrico Ferreguti wrote: > Hi QGIS devs, > I'm testing the API REST interface for updating a WFS3 and I verified that > the new/modified feature had to be expressed in geojson format in EPSG:4326 > coordinates regardless of the SRID of the served layer. I verified the > behaviour with QGIS server 3.16 LTR and latest 3.22 > > Is this an issue or a feature due to compliance to OGC or RFC7946 > standards? > > Anyway I found this behaviour very uncomfortable because it obliges to > perform preliminarly unaccurate reprojections from javascript/python > clients. > > Best regards. > Enrico Ferreguti. > ___ > 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] Server: wording WFS3 / OGC API - Features
Yes, definitely. Also the mention of "Draft" should be now removed. On Thu, Feb 10, 2022 at 12:14 PM pathmapper wrote: > Hi, > > currently the term "WFS3" is still used for the standard QGIS Server > "OGC API - Features" landing page URL: > > http://localhost/qgisserver/wfs3 > > and the docs: > > https://docs.qgis.org/testing/en/docs/server_manual/services/ogcapif.html > > Looks like WFS3 is not the official OGC wording anymore, also GDAL > renamed the driver: > https://gdal.org/drivers/vector/oapif.html > > Should we also go ahead and drop the use of the term "WFS3"? > > Cheers, > Bjoern > ___ > 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] QgsBlockingNetworkRequest and PATCH method (Python)
Hi, I think PATCH would be a nice addition and it's not difficult to implement. Kind regards. On Fri, Feb 4, 2022 at 9:00 AM Richard Duivenvoorde wrote: > On 2/1/22 08:35, Julien Cabieces wrote: > > >> I can see, that QgsBlockingNetworkRequest Class supports methods GET, > >> PUT, POST, HEAD and DELETE. However, according to the documentation for > >> the resource, I have to use the "PATCH" method for updating existing > >> objects on the server > >> > >> Is this possible using the QgsBlockingNetworkRequest Class from > >> Python? > > > > In this actual state no, because the doRequest method that you could > > have called with the PATCH method is private. So, you won't be able to > call > > it directly, and you won't be able to inherit QgsBlockingNetworkRequest > > to call it either. > > I'd say this is a nice FeatureRequest, as more and more web-services start > to use this newish [0][1](1995) PATCH thing... > > Maybe Ale is available (if you have some funding?)? I know he is known to > fly around in that area of the code :-) > > >> Or is there any other Python Class I can use for this purpose ?? > > > > I think one good solution is to use the request python framework ( > https://3.python-requests.org/) > > Which I found out recently is packaged with Windows QGIS...(?) So 'safe' > to use in QGIS... (though I would prefer to use > QgsBlockingNetworkRequest) > > Regards, > > Richard Duivenvoorde > > [0] > https://rubyonrails.org/2012/2/26/edge-rails-patch-is-the-new-primary-http-method-for-updates > [1] https://en.wikipedia.org/wiki/Patch_verb > > -- 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] MultiPart post network request stopped working in master
Hi Raymond,
can you please file a bug and assign it to me, I'll have a look.
On Sat, Jan 22, 2022 at 1:32 PM Raymond Nijssen
wrote:
> Dear all,
>
> One of my plugins stopped working in QGIS master, because some of the
> requests seem invalid. I spent quite some time on debugging but cannot
> find the problem.
>
> This script runs in 3.22.3 but not ion 3.23. It uploads an xml file to a
> validation service. It should print: {'successful': True, 'errors': [],
> 'warnings': []}
>
> Anyone a clue? I'm feeling that the best way would be using the
> QgsBlockingNetworkRequest post() function but that does not seem to work
> with a QHttpMultiPart variable.
>
> Thanks!
> Raymond
>
>
>
> import json
>
> manager = QgsNetworkAccessManager.instance()
>
> url = QUrl('https://connect.aerius.nl/api/v7/utility/validate')
>
> request = QNetworkRequest(url)
>
> multi_part = QHttpMultiPart(QHttpMultiPart.FormDataType)
>
> file_parts = []
> gml_fn =
>
> '/home/raymond/terglobo/projecten/aerius/202007_calc_input_plugin/demodata/test_20220121/test_kort.gml'
>
> file_parts.append({'name': 'filePart', 'file_name': gml_fn, 'file_type':
> 'application/gml+xml'})
>
> for fp in file_parts:
> file = QFile(fp['file_name'])
> file_part = QHttpPart()
> file_part.setHeader(QNetworkRequest.ContentTypeHeader,
> QVariant(fp['file_type']))
> name = fp['name']
> file_part.setHeader(QNetworkRequest.ContentDispositionHeader,
> QVariant(f'form-data; name="{name}";
> filename="{QFileInfo(file).fileName()}"'))
> file.open(QIODevice.ReadOnly)
> file_part.setBodyDevice(file)
> file.setParent(multi_part)
> multi_part.append(file_part)
>
> # This line already fires an invalid request in qgis 3.23:
> reply = manager.post(request, multi_part)
>
>
> # In qgis 3.22 the request is ok. The rest of the code will wait for the
> json
> # reply and display it.
>
>
> # make request blocking
> loop = QEventLoop()
> reply.finished.connect(loop.quit)
> loop.exec_()
>
>
> bstr = reply.readAll()
> result_dict = json.loads(bytes(bstr))
> print(result_dict)
>
>
>
>
>
> ___________
> 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] Donations
Hi, Honestly, whether this is a bug or a feature request is debatable, I personally think that it is a bug because a user would not expect that a basic software action like editing gets broken when the temporal controller is active: we should either disable editing in that case or make editing work with the controller. Anyway, I just wanted to underline that if this is to be considered a feature request it wouldn't be eligible for a grant (that explicitly forbids new features). Kind regards. On Mon, Jan 17, 2022 at 4:28 PM Andreas Neumann wrote: > Hi Cory, > > Yes - I would also think that this is not a bug, but a feature request. It > was never claimed that the temporal controller works fine in conjunction > with editing tools. The temporal controller was designed as a presentation > tool and not for editing. > > To improve the situation you would have to consult with one of the core > contributor companies listed at > https://www.qgis.org/en/site/forusers/commercial_support.html > > You could write a specification, ask one of the core contributor companies > for a quote and finance it yourself. Or you could try to write a QEP (QGIS > enhancement proposal) and submit it as a QGIS grant project. Incidentally, > Anita just issued the "Call for participation > <https://blog.qgis.org/2022/01/16/qgis-grants-7-call-for-grant-proposals-2022/>" > for the 2022 QGIS grants. If you could find a company that is interested in > working on this, and team up with them to write a QEP, it could be > submitted as a QGIS grant. The deadline for the QGIS grants is February 13. > > This would definitely be more work than what could be covered by smaller > donations. > > Hope this helps, > Andreas > > On Mon, 17 Jan 2022 at 01:21, Cory Albrecht wrote: > >> I filed a number of bugs a year ago about various digitising tools that >> no longer worked correctly as a result of the newly implemented Dynamic >> Temporal Controller. Things like the vertex tool and the snapping tool that >> continue to react to invisible features outside of temporal scope making it >> difficult, if not impossible to use those tools with temporal data. >> >> The bugs were, unfortunately, reclassified as feature requests, and have >> not been fixed since. I'd like to see them fixed because they cause me much >> difficulty and frustration when I am using QGIS. >> >> On Sun, Jan 16, 2022 at 12:54 PM Andreas Neumann >> wrote: >> >>> Hi Cory, >>> >>> We don't offer targeted donations where you can influence a specific bug >>> fix. If you need that - please contact one of the QGIS commercial support >>> providers - see >>> https://www.qgis.org/en/site/forusers/commercial_support.html >>> >>> Primarily one of the "core contributors". >>> >>> What specific issue do you want to see fixed? >>> >>> Andreas >>> >>> On Sun, 16 Jan 2022 at 18:46, Cory Albrecht >>> wrote: >>> >>>> Hello, >>>> >>>> Whom do I contact to make sure that a donation goes for development >>>> work on a specific bug or feature? The Donations doesn;t list any contacts >>>> except for tax deductions. >>>> ___ >>>> 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) >>> >> > > -- > > -- > Andreas Neumann > QGIS.ORG board member (treasurer) > ___ > 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] Leveraging Conda-Forge to create QGIS installers ?
Hi, Just a quick followup on this: we briefly discussed this topic within the PSC and the conclusion was that this is not a PSC matter. Kind regards. On Wed, Nov 10, 2021 at 12:16 AM Nyall Dawson wrote: > On Wed, 10 Nov 2021 at 00:42, Alexandre Neto > wrote: > > > > No comments?l > > > > I was expecting at least a bit of discussion about this. > > Honestly, I see it as a bit of a non-starter. Conda is still stuck to > such an old Qt version that you can't build anything past QGIS 3.18. > > To me that's reflective of a larger issue with the ecosystem, not an > isolated example. These mega-packaging-everything projects just seem > to consistently get bogged down by the sheer number of dependent > packages they try to satisfy, resulting in an overall worse experience > all round. > > But that's just my 2c ;) > > Nyall > > > > > > :-) > > > > Alexandre Neto > > > > A sábado, 6/11/2021, 20:46, Even Rouault > escreveu: > >> > >> Hi, > >> > >> Probably a topic that can raise passions and on which I'm moderately > >> legitimate to speak, but shouldn't we seriously consider leveraging the > >> Conda / Conda-Forge (https://conda-forge.org/) ecosystem for QGIS > >> packaging, especially on the Windows and Mac platforms ? QGIS depends on > >> a lot of external dependencies, and building them and updating them is > >> really about maintaining a packaging system, and QGIS has two such > >> separate and bespoke systems for Windows (OSGeo4W) and Mac > >> (QGIS-Mac-Packager). The ideal vision would be that the QGIS project > >> mostly maintains the bits specific to QGIS, but not be the sole > >> maintainer of its dependencies such as QT, GDAL (and its many > >> dependencies), PDAL, GRASS etc, as it is today. Conda-Forge provides a > >> truly collaborative environment and active community that already > >> bundles a number of those dependencies, and QGIS is already there (not > >> full capabilities yet, due to some dependencies missing. That would be > >> one of the points to address). The Conda-Forge community is really > >> vibrant (if you look at > >> > https://github.com/conda-forge/staged-recipes/pulls?q=is%3Apr+is%3Aclosed, > >> you can see that 20 packages were added in the last 24 hours!). It is > >> also a NumFocus sponsored project. It has support from a number of > >> institutions. It is unlikely to disappear anytime soon. > >> > >> There would certainly work needed to build installers from them. I found > >> https://github.com/conda/constructor project where you can build > >> standalone installers from Conda packages, but was told it is perhaps > >> not super mature. Even if QGIS needs require a dedicated installer with > >> custom bits, leveraging already packaged dependencies would probably be > >> a big enough win compared to the current situation where the whole stack > >> needs to be built and rebuilt from scratch by only a few knowledgeable > >> people, on non-shared infrastructure. > >> > >> There would be the possibility to pin dependencies at certain known good > >> points, for example to base LTR builds on top of them. > >> > >> I guess also that Conda based installers could help for plugins that > >> require installing native or Python dependencies, but that'd be already > >> more a secondary advantage. > >> > >> Another proof that Conda is to be taken seriously: > >> https://developers.arcgis.com/python/guide/understanding-conda/ > >> > >> I'm not saying this is a magical solution: there would clearly be a > >> significant amount of work and technical hurdles to solve to reach the > >> same degree of maturity as our current installers, but it is probably an > >> investment worth considering for the long term. > >> > >> Even > >> > >> -- > >> http://www.spatialys.com > >> My software is free, but my time generally not. > >> > >> ___ > >> 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] Retrieving error details for when a loaded layer is not valid
Hi,
you can try with
https://qgis.org/pyqgis/3.0/core/Data/QgsDataProvider.html#qgis.core.QgsDataProvider.error
On Sat, Nov 27, 2021 at 12:11 AM Ricardo Filipe Soares Garcia da <
ricardo.garcia.si...@gmail.com> wrote:
> Hi list
>
> When loading a vector layer via Python, is there a way to get a hold of
> the error message for when the loading fails?
>
> I can check if the layer is valid or not, but I'd like to get a
> description of the error. I see the error on the QGIS log panel, so I'm
> hoping it is possible to access it from Python.
>
> ```
> # a sample of my code
> layer = QgsVectorLayer("some-bogus-url", "mylayer", "WFS")
> layer.isValid() # this returns False
> ```
>
> Thanks in advance!
>
> --
> ___ ___ __
> Ricardo Garcia Silva
> ___
> 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] Cleaning up the QGIS Developers/QGIS Community groups
On Mon, Nov 22, 2021 at 12:41 AM Nyall Dawson wrote: > On Sun, 21 Nov 2021 at 18:22, Alessandro Pasotti > wrote: > > > > Yes please, thanks! > > Sorry -- turns out I don't have access to modify the QGIS member > groups. Want me to just collate a list of changes instead? > > Nyall > Hi Nyall, you should have enough permissions now, but I'm happy to help if you need. 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] Cleaning up the QGIS Developers/QGIS Community groups
Yes please, thanks! Il sab 20 nov 2021, 23:34 Nyall Dawson ha scritto: > On Sat, 20 Nov 2021 at 02:12, Alessandro Pasotti > wrote: > > > > On Mon, Oct 18, 2021 at 9:49 AM Nyall Dawson > wrote: > >> > >> On Mon, 18 Oct 2021 at 17:46, Alessandro Pasotti > wrote: > >> > > >> > Hi Nyall, > >> > > >> > To summarize: > >> > > >> > 1. QGIS core contributor status is for life > >> > 2. github core committer rights will be revoked after 24 months of > inactivity > >> > 3. github core committer rights will be given back if the contributor > restarts to contribute > >> > > > > > > Hi Nyall, > > > > Just to let you know that your proposal has been approved. > > Thanks Alessandro! To confirm -- should I apply this now? > > Nyall > > > > > > > -- > > 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] Cleaning up the QGIS Developers/QGIS Community groups
On Mon, Oct 18, 2021 at 9:49 AM Nyall Dawson wrote: > On Mon, 18 Oct 2021 at 17:46, Alessandro Pasotti > wrote: > > > > Hi Nyall, > > > > To summarize: > > > > 1. QGIS core contributor status is for life > > 2. github core committer rights will be revoked after 24 months of > inactivity > > 3. github core committer rights will be given back if the contributor > restarts to contribute > > Hi Nyall, Just to let you know that your proposal has been approved. -- 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 LTR releases -- is it time to pull the plug?
On Tue, Nov 16, 2021 at 8:50 AM Marco Bernasocchi wrote: > Hi Anita, Hi Nyall, Hi All > I think that it is a good idea to allocate the first half hour (and more > if needed) in tonight's budget meeting to this very pressing subject. > Nyall, thanks a lot for your analysis, we'll use it as discussion base. > > I extended the meeting invitation from 18:00 to 19:30. > > See you later > Marco > > > Hi, thinking about how to possibly prevent this to happen again I think that the manual testing cycles as proposed with https://lists.osgeo.org/pipermail/qgis-psc/2020-December/009186.html could help in identifying biggest issues before a release. I think we should consider the possibility of investing in that direction. 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] Problems with QgsProviderRegistry providerMetadata method
Hi Bo,
Is that with or without `cached` ?
QMap connections( bool cached = true )
On Mon, Oct 25, 2021 at 11:46 AM Bo Victor Thomsen <
bo.victor.thom...@gmail.com> wrote:
> Hi list members -
>
> I stumbled on something weird (for me at least):
>
> If I run the following code in the Python console:
>
> metadata = QgsProviderRegistry.instance().providerMetadata('postgres')
> conn = metadata.connections()
> for c in conn.keys(): print(c)
>
> It shows me (as I would expect): A list of names of postgres connections
> in QGIS.
>
> However, if I 1) Make a *new* postgres connection and 2) Rerun the same
> lines in the console, the new connection is *not* shown in the list.
>
> But if I restart QGIS and run the same code, the new connection will be
> shown together with the older connections.
>
> What gives ? Is there some kind of "refresh" method I've overlooked??
>
> Version: QGIS 3.20.3 on Windows 10.
>
>
> --
> 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] Cleaning up the QGIS Developers/QGIS Community groups
On Mon, Oct 18, 2021 at 12:55 AM Nyall Dawson wrote: > Hi lists, > > Given that we've recently granted membership to the github QGIS > Developers group to a bunch of new members, I think it's timely that > we also take the opportunity to clean up the membership and drop some > members. > > What I specifically mean here is that we should (hopefully > temporarily!!) remove developers/contributors from the groups if they > haven't been active in the project for say, the last 24 months. While > it's obviously sad to see once regular contributors move on, it's a > perfectly natural thing as people's work/life situations evolve and > change. > > Leaving these users with access to the repos is ultimately a security > risk to QGIS. I'm concerned that there's github accounts with > absolutely no Github activity at all in recent years who still have > direct commit access to the QGIS repository (e.g. > https://github.com/homann ). > > So I would propose that we set some policy regarding "temporary > hiatus/removal" from the QGIS Developers/QGIS Community groups for > users who aren't currently active in the project. Something like "if > the user shows no activity on the QGIS repositories for 24 months, > then that user will be temporarily removed from the security groups. > The user is still considered a core contributor/community member, and > can have these access rights revived at any time via emailing the QGIS > PSC". > > Thoughts? > > Nyall > Hi Nyall, To summarize: 1. QGIS core contributor status is for life 2. github core committer rights will be revoked after 24 months of inactivity 3. github core committer rights will be given back if the contributor restarts to contribute This makes total sense to me, we discussed this briefly in the PSC but we didn't decide anything yet. We can put it in the agenda for the following meeting but I think that if there are no objections from the qgis-dev ML I guess it will be approved right away. 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] Default QgsFeatureFid ?
IMO the default value should be FID_NULL, IIRC 0 is a valid fid for some providers. On Fri, Oct 15, 2021 at 11:50 AM Sandro Santilli wrote: > On Fri, Oct 15, 2021 at 10:45:52AM +0200, Alessandro Pasotti wrote: > > Hi, > > > > maybe you can use > > > > #define FID_NULLstd::numeric_limits::min() > > Maybe, but the question is more generic: *should* a QgsFeatureId have > a default value ? In that case maybe we could change its definition > from a typedef to a class and define such default value ? OR keep > it a typedef and consider 0 (the current typedefe'd type default) > as meaning NULL (can we ensure no *real* feature would ever have a > fid value of 0, from every provider?). > > --strk; > > -- 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] Default QgsFeatureFid ?
Hi, maybe you can use #define FID_NULLstd::numeric_limits::min() On Fri, Oct 15, 2021 at 10:40 AM Sandro Santilli wrote: > While writing unit test for QgsFeatureRequest in core I found > that the filterFid() method for the default-constructed > QgsFeatureRequest returns -1 rather than what a default-constructed > QgsFeatureId() would return (0) > > So I've been wondering: *should* a QgsFeatureFid have a default > value of -1 instead ? More generically: does QGIS make any assumption > about *which* special value of QgsFeatureFid means "no fid" ? > > If there's no such notion as an "unspecified FID" then I wonder > why QgsFeatureRequest is taking the effort of specifying a default > value of it different from the default, and if there's a good reason > it should probably be documented there. > > --strk; > > Libre GIS consultant/developer > https://strk.kbt.io/services.html > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > -- 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] Core committer status for Stefanos Natsis (uclaros)
Hi Stefanos, would you please send an email to the PSC stating that you have read and agreed with the following documents: - Read and agree to the Code of Conduct <https://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html#codeofconduct> . - Read and agree to the Coding Standards <https://docs.qgis.org/testing/en/docs/developers_guide/codingstandards.html> . - Read and agree to the Diversity statement <https://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html#diversitystatement> . They are from the page: https://qgis.org/en/site/getinvolved/development/contributor_requirements.html Kind regards. On Thu, Oct 14, 2021 at 12:32 AM Stefanos Natsis wrote: > Wow! That would be a great honor for me! Thank you Nyall for the > proposition and the kind words and thank you all for supporting and > reviewing my work! > It's been a real pleasure contributing! > Stefanos > > On Wed, 13 Oct 2021 at 10:47, Matthias Kuhn wrote: > >> A well deserved +1 for Stefanos, great contributions and stream of >> involvement. >> >> On Wed, Oct 13, 2021 at 8:54 AM Alessandro Pasotti >> wrote: >> >>> Warm +1 from me! >>> >>> Il 13 ott 2021 04:08, Nyall Dawson ha scritto: >>> >>> Hi PSC, dev list, >>> >>> I would like to formally propose that we grant core committer status >>> to Stefanos Natsis (https://github.com/uclaros). >>> >>> Stefanos has proven to be a very valuable contributor to QGIS, with a >>> great history of careful, well designed work. He brings some much >>> needed skills and insight to the QGIS project, and I'm always very >>> happy to see his pull requests flow in, as they consistently address >>> important bugs, paper cuts, and functionality gaps in the QGIS >>> application. >>> >>> I'd love to see us formally recognise the value he brings to the >>> project by granting Stefanos a core committer status. >>> >>> Thanks for your consideration! >>> Nyall >>> ___ >>> Qgis-psc mailing list >>> qgis-...@lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >>> >>> ___ >>> 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 > -- 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
