QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-15T13:34:16ZQGIS Issue Tracking
Redmine QGIS Application - Feature request #22085 (Feedback): Use Z and M values at vertex and/or Attribu...https://issues.qgis.org/issues/220852019-05-15T13:34:16ZTyler VeinotTylerKVeinot@gmail.com
<p>I would like to request the ability to use the Z and M values to render 3D features. Use case would be using Z and M values on a point to display a cylinder that starts at the Z value and extends down (or up) by the M value. Or displaying 3D lines based on their Z value at vertex, much like the options available in Qgis2threejs. Similar approach could be being able to use the attributes of a feature to identify the start and end elevation to display points or lines in much the same way.</p> QGIS Application - Feature request #21708 (Feedback): Fix Geometries be topologically aware/compl...https://issues.qgis.org/issues/217082019-03-29T18:57:41ZBrett CarlockSynper311@aol.com
<p>I'd love to see the Fix Geometries tool be made a bit more robust to help repair topological issues, such as psuedo-nodes as identified by the Topology Checker tool.</p>
<p>I had to turn to ArcMap to remove these topological issues as I was not able to in QGIS.</p> QGIS Application - Feature request #21564 (Feedback): since 2.18 was deprecated, the latest Mac v...https://issues.qgis.org/issues/215642019-03-12T07:55:38ZGavin Fleminggavin@kartoza.com
<p>on Kyngchaos, only 2.18.01 is available and <a class="external" href="http://download.osgeo.org/qgis/mac/">http://download.osgeo.org/qgis/mac/</a> only goes up to 1.0.</p>
<p>I would like to get the last 2.18 version as I still need 2.18 for many projects and plugins.</p> QGIS Application - Feature request #21549 (Feedback): Custom dash on polygon strokehttps://issues.qgis.org/issues/215492019-03-10T23:11:02ZAdam Oldadamold@gmail.com
<p>Allow custom dash patterns on the stroke of a polygon. Currently it seems to exist for line elements but not polygons.</p> QGIS Application - Feature request #21444 (Feedback): crop data to map extent when exporting to v...https://issues.qgis.org/issues/214442019-03-01T20:12:55ZCarolyn Krausecarolynkrause3@gmail.com
<p>When exporting to a vector pdf, the map layers are apparently not cropped to the map extent. So with a very detailed, world-wide vector layer, you can hit Adobe's 32,768 vertex limit. As a result, some features are (apparently randomly) excluded from the exported pdf.</p>
<p>That was the case in this question (<a class="external" href="https://gis.stackexchange.com/questions/314068/qgis-print-composer-incomplete-pdf-export">https://gis.stackexchange.com/questions/314068/qgis-print-composer-incomplete-pdf-export</a>) posted on GIS stackexchange, with a high-detail (10m) physical vector layer from Natural Earth. A pdf export of Northern Europe excluded certain islands, including Great Britain.</p>
<p>GIS SE user Juan (<a class="external" href="https://gis.stackexchange.com/users/137934/juan">https://gis.stackexchange.com/users/137934/juan</a>) commented: "When importing the "incomplete" map into Inkscape and using the path editing tool one can notice that there are many hidden vertices. Apparently what the print composer does is to add a mask to the part of the shp files that are not in the canvas. I suppose, then, that it prioritise certain polygons until it reaches the maximum allowable vertex count. Cropping the shp file seems to delete the unnecessary vertices, instead."</p>
<p><strong>Would it be possible to crop the vector data to the exported map extent, instead of just masking it?</strong></p> QGIS Application - Feature request #21423 (Feedback): Use more fcgi params for GetCapabilities re...https://issues.qgis.org/issues/214232019-02-28T12:36:04ZNikolay Lebedevnextstopsun@gmail.com
<p>In some cases QGIS services are exposed on multiple URL endpoints. <br />GetCapabilities response now takes into account fcgi params like SERVER_PORT and SERVER_NAME.<br />Unfortunately, neither SERVER_PROTOCOL nor REQUEST_URI are taken into account, so web server has to parse the backend response and replace it with appropriate values. <br />Could've been much better if QGIS used additional fcgi params to generate Capabilities.</p> QGIS Application - Feature request #21421 (Feedback): Option to clear cache for WMS/WMTS service ...https://issues.qgis.org/issues/214212019-02-28T11:04:18ZNikolay Lebedevnextstopsun@gmail.com
<p>When you add WMS/WMTS service to QGIS for the first time it's capabilities are fetched from the service and cached to QGIS folder. So if something changes on server side you have to clear cache manually. It'd be great to have an option to reread and re-cache capabilities response.</p> QGIS Application - Feature request #19832 (Reopened): Delete layers/files rather than removehttps://issues.qgis.org/issues/198322018-09-12T15:12:25Zna na
<p>There are some stackexchange questions about this with some code.</p>
<p>Rather than right clicking and removing layers, can we have the option to Delete them, so you don't have multiple duplicate/not needed files around.</p>
<p>I think this is more useful for commercial users, as it can be hard to determine what is still useful or junk data after the user who created the layers has finished his work.</p>
<p>Stackexchange tickets<br />[[<a class="external" href="https://gis.stackexchange.com/questions/190283/deleting-shapefiles-using-qgis">https://gis.stackexchange.com/questions/190283/deleting-shapefiles-using-qgis</a>]]<br />[[<a class="external" href="https://gis.stackexchange.com/questions/215673/deleting-shapefile-with-qgis?noredirect=1&lq=1">https://gis.stackexchange.com/questions/215673/deleting-shapefile-with-qgis?noredirect=1&lq=1</a>]]</p>
<p>The stackexchange tickets list how to delete shapefile but the scripts may need be converted in QGIS 3.0 as there has been an API break ect..</p> QGIS Application - Feature request #19106 (Reopened): snapping on hover when we want to rotate fe...https://issues.qgis.org/issues/191062018-06-04T12:22:40ZLéo Chevrierchevrierleo@gmail.com
<p>Hello,<br />One of usefull evolution for the rotate feature's function in qgis would be to snapp on hover on the anchor point that we want.</p>
<p>On my exemple : I want to rotate a segment with the anchor point on the end of the segment.</p>
<p>So I have to Use <em>Rotate Feature(s) to rotate one or multiple features in the map canvas. Press the rotateFeature Rotate Feature(s) icon and then click on the feature to rotate. Either click on the map to place the rotated feature or enter an angle in the user input widget. <br />If you enable the map tool with feature(s) selected, its (their) centroid appears and will be the rotation anchor point.</em> <strong>If you want to move the anchor point, hold the Ctrl button and click on the map to place it.</strong> (in this manipulation, i can't snapp my mouse pointers on the end of my segment, I have to manually zoom in on it and approximatively clickin on it)</p>
<p>What do you think about this evolution ?</p>
<p>Best regards</p>
<p>Léo</p> QGIS Application - Feature request #18444 (Feedback): Memory layer does not cast attribute typeshttps://issues.qgis.org/issues/184442018-03-14T21:27:54ZNorwin Roosenqgis@nroo.de
<p>Expected Behaviour:<br />Writing values of incorrect type to a memory layer field should cast them to the correct value or throw an error.</p>
<p>Actual behaviour:<br />In QGIS 2.18.16, writing a string into a double field of a memory layer writes the value unchanged.<br />Reading the attribute later returns the original value of type unicode.</p>
<p>The following python code illustrates this:<br /><pre>
from qgis.core import QgsVectorLayer, QgsFeature
layer = QgsVectorLayer("Point?field=floatfield:double", "poc", "memory")
feat = QgsFeature()
feat.setAttributes(['10'])
layer.dataProvider().addFeatures([feat])
QgsMapLayerRegistry.instance().addMapLayer(layer)
# in my usecase I actually loaded the layer from within another processing algo
for f in layer.getFeatures():
print f['floatfield'], type(f['floatfield'])
# prints
# 10 <type 'unicode'>
# should obviously be
# 10.0 <type 'float'>
</pre></p> QGIS Application - Feature request #13786 (Reopened): Include the closed source ESRI FileGeoDB li...https://issues.qgis.org/issues/137862015-11-07T11:38:31ZCorey Burgercorey.burger@gmail.com
<p>The default QGIS install (2.12) doesn't include R/W access to ESRI FileGBs (it used to and it go dropped about 2.8). Given the popularity of Arc* products, shipping this should be part of the basic functionality of QGIS.</p>
<p>Here is a great example of another user frustrated with the same issue:<br /><a class="external" href="http://gis.stackexchange.com/questions/167939/need-file-geodatabase-gdb-read-write-support-in-qgis">http://gis.stackexchange.com/questions/167939/need-file-geodatabase-gdb-read-write-support-in-qgis</a></p> QGIS Application - Feature request #10822 (Reopened): Print composer - allow tiled raster image e...https://issues.qgis.org/issues/108222014-07-05T14:29:49Zbaditaflorin -baditaflorin@gmail.com
<p>Please try a lower resolution papersize</p>
<p>I need to print 40000x35000 pixels images, i have 8 GB of RAM, and the image will need only 1.54 GB of Ram</p>
<p>How can i circumvent this warnign/error ?</p> QGIS Application - Feature request #8249 (Feedback): Warning before running analyses on too large...https://issues.qgis.org/issues/82492013-07-10T04:35:09ZPaolo Cavallinicavallini@faunalia.it
<p>If the user does not select an appropriate resolution for the resulting raster(s), it risks to get stuck with an excessive resolution, and too long processing time. I suggest to do a simple calculation of the resulting number of pixel before running analyses, and warn the user if this is too high.</p> QGIS Application - Feature request #7611 (Reopened): Title case option which also operates on upp...https://issues.qgis.org/issues/76112013-04-14T03:15:51ZNyall Dawson
<p>Setting a type case of "Title case" has no effect on the way labels are rendered when the text is already in upper case. For example, in the attached image "KNOX" is rendered as "KNOX", not "Knox". The other case settings (All uppercase/lowercase) work as expected.</p>
<p>EDIT<br />As discussed, "Title case" has been renamed "capitalize first letter", so this is now a feature request for a "Title case" feature, which would also lowercase subsequent letters.</p> QGIS Application - Feature request #4069 (Reopened): Enhancement: ability to search for a plugin ...https://issues.qgis.org/issues/40692011-07-10T19:12:15ZAlister Hood
<p><strong>Problem description</strong><br />Quoting from an old ticket: "With the explosion of QGIS plugins, people will eventually have so many plugins that it would get hard to find them in the Plugin menu or Plugin toolbar."</p>
<p>"eventually" is now!</p>
<p>This is particularly a problem when a plugin is not grouped into one of the categories (e.g. "analysis" or "vector"), and its name is different from the label of its menu entry e.g. "shaded relief" vs "DEM relief shader".</p>
<p>In the plugin manager and the plugin installer there is a "filter", which allows the user to search for a plugin to install/uninstall or enable/disable it. It would be good if there was also somewhere where the user could search for a plugin to <em>run</em> it.</p>
<strong>Possible Solutions</strong>
<ol>
<li>Add to the plugin manager the ability to start a plugin.</li>
<li>Implement something like <a class="issue tracker-2 status-1 priority-3 priority-" href="https://issues.qgis.org/issues/1734" title="Use a dockable tabbed window for plugins (Open)">#1734</a>: "Use a dockable tabbed window for plugins", and include a filter. Personally I don't like the idea of an array of buttons (a list like the plugin manager would be better), and rather than category tabs it may be better to have a single list of plugins, with the ability to filter by category.</li>
<li>Combine 1 and 2, i.e. modify the plugin manager to be a dockable modeless window with the ability to launch plugins.</li>
<li>?</li>
</ol>
<p>The need for this would probably be reduced significantly if <a class="issue tracker-2 status-5 priority-3 priority- closed" href="https://issues.qgis.org/issues/1602" title="Superfluous entries in the Plugin menu (Closed)">#1602</a>: "Grouping plugins in the menu" was implemented, i.e. if all plugin developers put their plugins into category submenus.</p>