[QGIS-Developer] Plugin [995] dzetsaka : Classification tool approval notification.
Plugin dzetsaka : Classification tool approval by pcav. The plugin version "[995] dzetsaka : Classification tool 3.4.1" is now approved Link: http://plugins.qgis.org/plugins/dzetsaka/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1595] NeatMap approval notification.
Plugin NeatMap approval by pcav. The plugin version "[1595] NeatMap 1.0 Experimental" is now approved Link: http://plugins.qgis.org/plugins/NeatMap/ ___ QGIS-Developer mailing list 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] Any ways to avoid offsets being shown in printed map legend?
I would love to be able to sponsor the development, but I work in a large company who is "engaged" with ESRI, so if I ask for funding I will just get the answer: We already pay to Esri, so use ArcGIS :-( And I have no knowledge on python While talking about legends in print composer I sometimes find it hard to get it to update like if I have added a new category on a layer. Ticking auto update will add all layers to the print composer and I almost never show all layers in printed maps (I ususally exclude background maps like google Maps etc.) . Normal workaround is to add the layer a second time to the print composer legend and redoo any edits :-( Sometimes also turning feature class count on and off does the trick - Regards Morten Currently using Qgis 2.18.23 (OSGeo4) and Qgis 3.4.2 in parallel Windows 7, 64bit -- Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Call for nominations for new QGIS community voting members
Dear QGIS Community This is a call for nominations for new QGIS community voting members. Please read the instructions carefully and establish your eligibility to vote which I repeat here for your convenience: "Only community members with commit rights to an official QGIS git repository or with write access in transifex are eligible to make nominations.” The nomination form is here. https://goo.gl/forms/Lfk1VBDKlRAOrWYq1 Incoming community voting members will be selected based on the number of nominations they receive. The above form will close on 30 December 2018. If you play an organisational role (e.g. documentation lead, translation lead), please forward this email to your committers. A larger version of the diagram included in the form is also available here: https://drive.google.com/file/d/12qPHUjvPv5CMpZKSWHwr65DG-YOZsub1/view?usp=sharing If you have any questions about the process please do not hesitate to contact me. Thank you, Regards Marco -- Marco Bernasocchi QGIS.org Co-chair http://berna.io ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Marker line y offset
Really fun stuff arises when you then use the arrows to increase width (in steps of 0.2 *mm*) Explaining somebody why you are using a linewidth of 0.46 mm, well eh you know: 1/10th of an inch + 0.2 mm isn't that a natural width to choose :-) The used increments of 0.20 mm indicates by the way, that default width should be 0.20 mm and not 0.25 mm to give nicer looking values when incrementing like 1,0 mm and not 1.05 mm. - Regards Morten Currently using Qgis 2.18.23 (OSGeo4) and Qgis 3.4.2 in parallel Windows 7, 64bit -- Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] QGIS 3.4 preconfigured algorithm ?
Hi Nyall, I come back to the issue... I don't see how to make a model as full as a preconfigured algorithm. For example, how to introduce an input layer without the end user having to enter it? The case that was processed under QGIS 2.16 is a little more sophisticated. this is an example of epizootic crisis management. Attached an example with a project file (algo.qgs) to decompress directly under c:\ and an agorithm model to copy under .qgis2\processing|models and under \preconfigured for the algorithm. The condition for executing the preconfigured algorithm is the selection of one or more points of the "avicole" layer I don't see how to automate in the same way with the modeler? Regards Alain FERRATON Alain Ministère de la Transition écologique et solidaire (MTES) SG/SPSSI/CPII/DOO Chef du groupe Expertise Technique 02.40.12.84.08 Le 08/12/2018 à 03:22, > Nyall Dawson (par Internet) a écrit : On Fri, 7 Dec 2018 at 22:22, Andreas Neumann wrote: Hi Alain, Indeed - this feature seems to be missing in QGIS 3.x. Note that the whole processing tools had been completely rewritten in QGIS 3.x and ported from Python to C++ Maybe that part hadn't been ported over yet. I am cc'ing Nyall who did most of the work around the processing refactoring. Maybe he knows more why this functionality is missing in QGIS 3.x It'd take me a while to dig around and find the original conversations, but if I recall correctly this was dropped in the lead up to 3.0 as it was functionality which was seldom used and addressed use cases also covered in a nicer way by the graphical modeler. Nyall Greetings, Andreas On 2018-12-07 11:46, FERRATON Alain (Chef de groupe) - SG/SPSSI/CPII/DOO/ET wrote: Hi Andreas, it is a feature (little known?) that allows to create pre-configured algorithms by right-clicking on an algorithm (QGIS 2.16) Regards Alain FERRATON Alain Ministère de la Transition écologique et solidaire (MTES) SG/SPSSI/CPII/DOO Chef du groupe Expertise Technique 02.40.12.84.08 Le 07/12/2018 à 11:40, > Andreas Neumann (par Internet) a écrit : Hi Alain, Are you refering to "processing models"? The models defined in the processing model builder? I am not sure I correctly understand what "preconfigured algorithms" mean? Greetings, Andreas On 2018-12-07 11:16, FERRATON Alain (Chef de groupe) - SG/SPSSI/CPII/DOO/ET wrote: Hello, I put my request on the qgis-user list without success. So I'm taking my chances on the developer list. I can't find the possibility to make 'preconfigured algorithms' with QGIS 3.4? Has this feature been removed? how to do it? 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
[QGIS-Developer] Vertex tool and cache invalidation
Hi, I am facing some issues with the vertex tool of 3.x. In 2.18 the "node tool" was working by clicking first on a geometry to select it or its vertices and then displace them. With the new "vertex tool", there is no more first click involved and geometries are "selected" when the mouse position is close enough. This behaviour and ergonomic change (which I like !) implied an implementation that needs, for descent performances, to build a cache of geometries and maintain it. Problems arise when a modification on a layer may trigger modifications on others. For example when two layers have triggers in database (to maintain a correct network topology in database for instance), or even when the same layer is opened twice. QGIS has no way to know that the modification of a layer can modify another layer. So it easily leads to problems where "phantom" geometries are still selectable but actual (modified by side effect) geometries are not. I introduced in a previous version a way to express "data dependencies" between layers, with this issue in mind. For PostgreSQL databases, there is probably also a way to circumvent this by using the LISTEN/NOTIFY mechanism and some lines of Python. However I find these solutions very obscure and unfriendly. Open question: what about re-introducing the old "click first" behaviour of the vertex tool (and probably other tools) in a next version ? Not as a replacement, but as a possible alternative. ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
