QGIS Application: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-22T10:12:55ZQGIS Issue Tracking
Redmine Feature request #22121 (Open): Sort inputs parameters in QGIS modelerhttps://issues.qgis.org/issues/221212019-05-22T10:12:55ZMaxime RIOUmaxime.riou@ymail.com
<p>This refers to a question on GIS Stack exchange (<a class="external" href="https://gis.stackexchange.com/questions/322831/sort-inputs-parameters-in-qgis-modeler">https://gis.stackexchange.com/questions/322831/sort-inputs-parameters-in-qgis-modeler</a>). <br />I created a model in QGIS 3.6 with three inputs parameters (two vector layer and one vector field). When I run the model, the inputs are not sorted in a correct way: the vector field is requested before the vector layer.</p>
<p>I searched on previous feature requests and I found this <a class="issue tracker-1 status-5 priority-5 priority- closed" href="https://issues.qgis.org/issues/11702" title="Support reordering the input fields in a Processing model GUI (Closed)">#11702</a> but it is closed now.</p>
<p>It would be nice to choose the order of the inputs parameters. For example, if the input parameters are sorted in alphabetical order, the user could name inputs "1_inputXX, 2_inputYY, etc.".</p>
<p>The proposed answer on GIS stackexchange is the following workaround :</p>
<p>Export Model as Python Algorithm to get a translated script of your model. Here you could order the parameters however you like in the <br /><pre>
initAlgorithm() function. E.g.:
def initAlgorithm(self, config=None):
self.addParameter(QgsProcessingParameterFeatureSource('1conduites', '1_Conduites', types=[QgsProcessing.TypeVectorLine], defaultValue=None))
self.addParameter(QgsProcessingParameterVectorLayer('2regard', '2_Regard', types=[QgsProcessing.TypeVectorPoint], defaultValue=None))
self.addParameter(QgsProcessingParameterFeatureSource('3idregard', '3_ID_regard', types=[QgsProcessing.TypeVector], defaultValue=None))
self.addParameter(QgsProcessingParameterFeatureSink('Result', 'result', type=QgsProcessing.TypeVectorPolygon, createByDefault=True, defaultValue=None))
</pre></p> Feature request #22112 (Open): Name of layout for exporthttps://issues.qgis.org/issues/221122019-05-21T07:36:00ZAndrew Shaninhedgestandart@gmail.com
<p>Need add field in page 'Property of Element' for naming exporting page.</p> Feature request #22108 (Open): In Print Layouts, allow spacing after groups and sub-groups in Leg...https://issues.qgis.org/issues/221082019-05-20T18:39:56ZMatthew Doveym.dovey@garsington.org.uk
<p>Consider the extract from a Legand in the image below:</p>
<p><img src="https://issues.qgis.org/attachments/download/14962/legend.png" alt="" /></p>
<p>There are three layers - Tree Preservation Orders, Priority Habitats and Woodland. The first two have sub-items (as subgroups) as they are using categorised symbology.</p>
<p>By adjusting the Spacing options under the Legend properties, you can create a space about Priority Habitats (as shown). However, it is not possible to create spacing after the subgroup (i.e. between last item of Priority Habitats, namely Traditional Orchard, and the Woodland layer).</p>
<p>As a result, it isn't possible to visually indicate that Woodland is a seperate item, and not a sub-item of Priority Habitats.</p>
<p>A solution to this would be to extend the Spacing properties to allow specifying spacing both before groups and subgroups, and also after groups and subgroups.</p> Feature request #22101 (Open): function as min, max, average is not availablehttps://issues.qgis.org/issues/221012019-05-18T20:33:11ZSC SC
<p>Hi but raster calculator is not able to solve function as min or max<br />if with 3 or more raster I want to create a new raster with matrix of min of other raster I have to use grass or gdal</p>
<p>and this is not coherent with powerful field calculator for vector</p> Feature request #22099 (Open): Make Designing forms in QGIS friendlyhttps://issues.qgis.org/issues/220992019-05-18T13:58:30ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<p>The current way of creating and editing forms in QGIS is not ideal. It has all the great tools/features to built the forms but it can be improved to be a but more user-friendly. Here are some of the areas to improve it:</p>
<ul>
<li>Having a preview in the form designer</li>
<li>Re-designing the current layout: it is confusing and all options are displayed. Some can be hidden away under advanced options.</li>
<li>Logic based forms: allow attribute to be visible/editable based on the logic from other attributes</li>
<li>Allow simple form design in Form view (when browsing data).</li>
</ul> Feature request #22081 (Open): Add option to zoom to extent of saved bookmark in Map composerhttps://issues.qgis.org/issues/220812019-05-15T08:20:26ZAdmire Nyakudya
<p>I am using map themes and saving the extent of each map theme as a bookmark. However, when I go to the map<br />composer I will still need to change the scale to align to the bookmark extent. This is cumbersome when I add multiple maps on the same page<br />corresponding to a theme. If there was an option to change the extent of a map to align to a bookmark it would make it easier.</p> Feature request #22061 (Open): Select visible layers (blocks) from tiffhttps://issues.qgis.org/issues/220612019-05-13T08:32:15ZAndrew Shaninhedgestandart@gmail.com
<p>Feature provide to choose visible blocks/layers in multilayered tiff / geo tiff file.</p> Feature request #22056 (Open): Consistent layer adding for serviceshttps://issues.qgis.org/issues/220562019-05-12T23:28:06ZJonathan Moules
<p>QGIS has progressed nicely and now has the Data Source Manager. This is nice, but there's still the issue of a lack of consistency in adding layers for services (WMS, WFS, WCS, ArcGIS MapServer, ArcGIS FeatureServer, GeoNode).</p>
<p>1) Filtering<br />Different data sources have different ways of searching for layers within a service.</p>
<p>I.e. WFS, ArcGIS MapServer/FeatureServer, and GeoNode all have a "filter".<br />WMS/WMTS, and WCS have nothing.<br />By comparison, the databases all seem to use a "search options" field and this appears consistent across database types.</p>
<p>2) The ordering of the name/title columns is inconsistent between service types</p>
<p>3) WMS, WCS include an "ID" column which doesn't represent anything that's in the getcap</p>
<p>4) CRS changing is represented differently for all of them</p>
<p>5) WFS allows you to specify the max version, the others don't.</p>
<p>6) Mechanism for specifying data format is different for the different services</p>
<p>7) WFS has "use title for layer name", but WCS doesn't. (WMS does it differently again, but WMS allows merging multiple layers together so...)</p>
<p>8) WFS and ArcGIS FeatureServer have the same settings but opposite defaults.</p>
<p>9) WMS and GeoNode include a "referer" field, but none of the others do.</p>
<p>There are probably more things, this isn't meant to be exhaustive, just a good starting place.</p> Feature request #22054 (Open): WFS - show and filter the keywords fieldhttps://issues.qgis.org/issues/220542019-05-12T23:06:20ZJonathan Moules
<p>Currently WFS only filters the Title field. There's a bug report/feature request for filtering name/abstract as well (<a class="issue tracker-1 status-1 priority-4 priority-" href="https://issues.qgis.org/issues/22053" title="Filter on WFS only filters on title field (Open)">#22053</a>).</p>
<p>Beyond that, OGC services also have a keywords field - this should be both shown, and filtered</p> Feature request #22032 (Open): Allow join fields to use expressionshttps://issues.qgis.org/issues/220322019-05-09T11:07:36ZAdmire Nyakudya
<p>I have two tables (Table A, Table B) with columns name. I needed to use these columns to create my join but once I join them I realize that they are no records that have joined because of the differences between title case for the two columns. Table A contains values in Uppercase and table B contains data in lowercase. It would be nice to include the option to use an expression on the target field/join field when doing a join ie<br />Table A has name = UpperCase<br />Table B has name = Lowercase so when we do the join we could use the expression Upper(name) on the target field.</p>
<p>This would prevent having to edit the raw data by updating it or creating a new virtual field or using SQL for people who are not good in SQL (virtual layers).</p> Feature request #22020 (Open): [processing][xyz tiles] append zoom levels to an existing mbtileshttps://issues.qgis.org/issues/220202019-05-08T11:44:58ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<p>If the mbtiles already existed, append the zoom levels instead of overwriting the file.</p> Feature request #22019 (Open): Add GRASS "turntable" parameters to v.net moduleshttps://issues.qgis.org/issues/220192019-05-08T11:39:37ZSergio Antonio
<p>The GUIs of the tools v.net.path, v.net.alloc, v.net.iso, v.net.salesman are not showing the possibility to configure the use of the turntable (parameter -t of each algorithm), according to the manual .<br />This parameter is indispensable for the good performance of the tools: v.net.path, v.net.alloc, v.net.iso, v.net.salesman.<br />The turntable is created by the v.net tool, which is not showing this function in "operation to be performed".<br />Please see attached texts with highlights.</p> Feature request #22012 (Open): Add "point on surface" to label placement optionshttps://issues.qgis.org/issues/220122019-05-07T21:03:09ZNathan Perry
<p>In addition to label placement around a polygon's centroid, it would be helpful to have the option to use a point calculated by the point_on_surface() algorithm.</p>
<p>See also previous feature request <a class="issue tracker-2 status-5 priority-3 priority- closed" href="https://issues.qgis.org/issues/3647" title="Add the choice "near to the pointOnSurface" (Closed)">#3647</a>. It was closed because of the option to "force point inside polygon". However, this option only takes effect if the centroid falls outside the polygon, whereas point_on_surface() actually calculates a point different than the centroid, even if located inside the polygon. This point appears more visually centered in certain polygons and is thus sometimes a better choice cartographically.</p> Feature request #21992 (Open): [processing][xyz tiles] mask layer instead of bboxhttps://issues.qgis.org/issues/219922019-05-03T12:39:06ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<p>The tool is processing tiles in the bounding box of a layer (or other rectangle extends). This is useful in overviews. But especially in higher zoom-levels(for example zoom (19) 20/21/…)) combined with non-rectangle-like areas of interest, there is there is a risk of time-consuming rendering time without usable content. (There is a workaround to subdivide the area of interest in smaller areas. But after that users have merge mbtiles-outputs…). So it may be useful to have the option /ability to render just the tiles covering non-rectangle contents.</p> Feature request #21990 (Open): [processing][xyz tiles] warn user when overwriting files/foldershttps://issues.qgis.org/issues/219902019-05-03T12:32:05ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<p>Warn users of overwriting data if the selected output folder is not empty.</p>