QGIS Application: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-04-03T18:25:03ZQGIS Issue Tracking
Redmine Feature request #21759 (Open): Changing rendering behavior on zoom to prevent flashes https://issues.qgis.org/issues/217592019-04-03T18:25:03ZAndrew Annexannex@jhu.edu
<p>On macOS with qgis 3.4.6 LTR. Unknown if this is on other systems</p>
<p>Zooming should disable rendering until the updated map view is completely rendered and then display. Currently with multiple raster and vector layers, with some wms layers, when a zoom event the canvas is cleared to white followed by various layers rendering and popping into view which causes eye strain and is visually distracting.</p>
<p>The behavior I want is closer to what happens when the render checkbox is deselected. The existing canvas should be in view until the new canvas has completely finished rendering and then it should replace the current canvas view on the screen. This behavior should probably be configurable</p> Feature request #20550 (Open): Add visualization of invalid geometry Errorhttps://issues.qgis.org/issues/205502018-11-19T10:41:58Zrohit singhrohitsinghsalyan@gmail.com
<p>It is very difficult to find the duplicate nodes and edit them to remove the invalid geometry error. During the edit option it should show in different color compared to correct nodes.</p> Feature request #19804 (Feedback): Change Legend Right to Left Reading in QGIShttps://issues.qgis.org/issues/198042018-09-10T08:26:15ZMostafa ELhalwagymustafa.alhalwagy@gmail.com
<p>Please follow this request on gis.stackexchange</p> Feature request #19609 (Open): Add color ramp item with tick and number label in print layouthttps://issues.qgis.org/issues/196092018-08-13T14:40:02ZZhe Fang1315479326@qq.com
<p>As shown in the picture attached, we usually use a color ramp rather than a legend to label a raster DEM layer, so we need a color ramp item that users get a certain gradient symbol based on the selected raster layer. Then users design its aspect(vertical or horizontal), width, height, interval of ticks, number of ticks, and font of number label.</p> Feature request #18771 (Open): 1:n relations: new entries in child layer when child has geometrieshttps://issues.qgis.org/issues/187712018-04-19T13:12:13ZGiovanni Manghigiovanni.manghi@gmail.com
<p><a class="external" href="https://docs.qgis.org/2.18/en/docs/user_manual/working_with_vector/attribute_table.html#id25">https://docs.qgis.org/2.18/en/docs/user_manual/working_with_vector/attribute_table.html#id25</a></p>
<p>If the child layer is a geometryless table then the actual (2.18/3) implementation has no problems.</p>
<p>The example referenced in the manual is about a scenario where the child is a table <strong>with</strong> geometries, so when the manual says</p>
<p>"The "+" button will add a new feature to the airport layer. And it will assign the new airport to the current region by default." this will effectively add a row in the child table but without the appropriate geometry, because in the relation form the possibility to digitize geometries for new child entries is not implemented.</p>
<p>This leave the data in a inconsistent state and is cause of confusion and data corruption. An similar example bases on geometry postgis tables shows that when saving edits for a new record in the child table, this new record is completely discarded with no message/warning/error whatsoever by QGIS.</p> Feature request #18478 (Open): Find and Replace in Layout makerhttps://issues.qgis.org/issues/184782018-03-19T07:41:58ZAndrew Shaninhedgestandart@gmail.com
<p>Ordinary function for replacing text in layer composer.<br />It could be very usefull.</p> Feature request #18436 (Open): ArcMap style clipping in QGIS 3.0https://issues.qgis.org/issues/184362018-03-14T06:49:38Zeino jaskarieino.jaskari@hotmail.com
<p>Hi,<br />I'd like to have ArcMap style clipping feature in QGIS 3.0. There is a plugin (<a class="external" href="https://github.com/demarcog/Clipper">https://github.com/demarcog/Clipper</a>) for QGIS 2.xx, but it does not work for 3.xx.<br />Basically the clipper cuts all intersecting shapes, like overlaying polygons, with the boundaries of a selected polygon. It also DOES NOT create a new file, like the clip-processing tool currently does in QGIS, but instead it manages to modify the layer itself. So if one layer has 5 polygons that overlap, I select one of the polygons and click "clipper -button", other polygons within the same layer are cut with the boundaries of a selected polygon directly within the layer and it does not even ask you to create a new layer. There is also a merger tool build in QGIS, so this just does the opposite - kind of.<br />Clipper plugin ( <a class="external" href="https://github.com/demarcog/Clipper">https://github.com/demarcog/Clipper</a> ) had some issues with PostGis functionality. It would be grate if QGIS 3.0 had build in clipper that supports all data formats that are supported by the program itself, including PostGis, Oracle, Shapefile, etc...</p> Feature request #17548 (Feedback): Automatically populate layer metadata for WMS layershttps://issues.qgis.org/issues/175482017-11-25T10:10:32ZJames Passmorejpass@bgs.ac.uk
<p>When right clicking on a WMS layer in the Layers Panel and selecting properties No information or metadata is provided about the service</p>
<p>===</p>
<p>QGIS version<br />2.99.0-Master<br />QGIS code revision<br />cd0ba91<br />Compiled against Qt<br />5.5.1<br />Running against Qt<br />5.5.1<br />Compiled against GDAL/OGR<br />2.2.2<br />Running against GDAL/OGR<br />2.2.2<br />Compiled against GEOS<br />3.5.1-CAPI-1.9.1<br />Running against GEOS<br />3.5.1-CAPI-1.9.1 r4246<br />PostgreSQL Client Version<br />9.5.2<br />SpatiaLite Version<br />4.3.0a<br />QWT Version<br />6.1.2<br />PROJ.4 Version<br />492<br />QScintilla2 Version<br />2.9.1<br />This copy of QGIS writes debugging output.</p> Feature request #15652 (Open): Add option for OGR data sources to be opened in read only modehttps://issues.qgis.org/issues/156522016-10-02T23:26:06ZAndreas Neumann
<p>Apparently some data formats (e.g. geopackage) load with better performance if they are opened in "read only" mode - esp. when loaded from a network share.</p>
<p>The add vector layer dialogue should therefore offer a "read only" flag for opening of vector formats that don't need to be edited.</p>
<p>See discussion at <a class="external" href="http://lists.opengeospatial.org/pipermail/geopackage/2016-October/000200.html">http://lists.opengeospatial.org/pipermail/geopackage/2016-October/000200.html</a></p> Feature request #13622 (Open): Create the possibility to make attribute queries with mapped value...https://issues.qgis.org/issues/136222015-10-16T04:13:57ZLuiz Andradelcoandrade@gmail.com
<p>Dear all, I'm a Brazilian Army Officer and our Geographic Service Bureau is adopting QGIS as our corporate GIS solution.<br />Brazil has a national vectorial geospatial data structure, called EDGV, and almost all features in that structure use mapped values. To deal with that the Brazilian Army has developed the plugin DSGTools (<a class="external" href="http://plugins.qgis.org/plugins/DsgTools/">http://plugins.qgis.org/plugins/DsgTools/</a>). The plugin uses QML files to map the values and make feature creation easier to our user but we need to make queries and the default QgsExpressionBuilderWidget doesn't allow us to use mapped values. We want the user to be able to build queries using the keys present in our QML files.</p>
<p>For instance, today we make the following query:<br />"geometriaaproximada" = 1</p>
<p>But we want to able to build this:<br />"geometriaaproximada" = Yes (easier to our user to understand what he/she is actually querying)</p> Feature request #12058 (Open): Function Editor in Expression widget : a button to delete a useles...https://issues.qgis.org/issues/120582015-01-26T03:00:27ZHarrissou Santanna
<p>Hi,<br />It could be nice to have a button that helps to delete wrong or useless custom functions in the function Editor tab in expression dialog.</p> Feature request #7706 (Open): Geometry constructors (EWKT/EWKB)https://issues.qgis.org/issues/77062013-04-25T06:35:55ZDenis Rouzauddenis.rouzaud@gmail.com
<p>Right now, only WKT/WKB can be used to import/export geometries.</p>
<p>It would be great to have EWKT and EWKB import/export methods, to avoid complex stuff as in [0]</p>
<p>[0] <a class="external" href="https://github.com/elpaso/quickwkt/blob/73870168d09589a9ab8d54f7d695e548c26e7751/QuickWKT.py#L144">https://github.com/elpaso/quickwkt/blob/73870168d09589a9ab8d54f7d695e548c26e7751/QuickWKT.py#L144</a></p> Feature request #7235 (Open): Add option to avoid users producing invalid topologies while digiti...https://issues.qgis.org/issues/72352013-02-25T07:27:11ZDuncan Golicherdgolicher@gmail.com
<p>Attempts to remove intersections when digitising over invalid topologies lead to unexpected behaviour. See bug <a class="issue tracker-1 status-5 priority-5 priority- closed" href="https://issues.qgis.org/issues/7225" title="QGIS crashes after failed intersect removal (Closed)">#7225</a> and related issues. The problem also extends to snapping and hole removal (bug <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/4880" title=""add feature" tool (for polygons) + "avoid intersection" is inconsistent when it is used to fill ... (Closed)">#4880</a>).<br />It would probably be safer overall if users were digitising with an option switched on that rejected all invalid polygons. If they do draw an invalid polygon they could be provided with a warning message, the invalid vertices marked, and the offending polygon would not be added to the layer until all the errors are fixed. This could be a default option as it would probably prevent users from forcing QGIS to run code that may have difficulty finding consistent ways of dealing with errors. The option to deactivate the checks should be provided, along with a clear warning of the possible consequences of doing so.</p> Feature request #6894 (In Progress): GRASS r.mapcalc cumbersome to use, issues on Windowshttps://issues.qgis.org/issues/68942012-12-18T08:56:38ZPedro VenĂ¢nciopedrongvenancio@gmail.com
<p>Hi,</p>
<p>I think it's very important to include GRASS r.mapcalc on Sextante. At this moment, is lacking on Sextante an advanced raster calculator, with the potential of r.mapcalc (with advanced operators and functions).<br /><a class="external" href="http://grass.osgeo.org/grass64/manuals/r.mapcalc.html">http://grass.osgeo.org/grass64/manuals/r.mapcalc.html</a></p>
<p>Is there any limitation that prevents the inclusion of this tool? Right now it seems to me the biggest absence on Sextante.</p>
<p>Thanks!</p> Feature request #6255 (Feedback): Add button to force recalculating stats of raster layershttps://issues.qgis.org/issues/62552012-08-27T04:27:53Zalobo -aloboaleu@gmail.com
<p>Currently QGIS relies on mean and sd values on the<br />GTif if present for stretching based on sd. Sometimes<br />this information can be wrong and gdalinfo -stats does<br />not force recalculating stats (see <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/5035" title="stretching with nb of standard deviation: always min = max = 0 (Closed)">#5035</a>).<br />The user should be able to force QGIS recalculating stats,<br />probably a button in Properties/Style would be a good option</p>