QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2018-11-01T19:00:52ZQGIS Issue Tracking
Redmine QGIS Application - Feature request #20322 (Open): save path of menu when right clicking on a men...https://issues.qgis.org/issues/203222018-11-01T19:00:52ZNicolas Cadieux
<p>It would be nice to have a "save path of menu" in the clipboard when we right click in the menu or and icons. As an example, a right click on CRS layer in the Project Properties would save "Project/Properties/CRS" in the clip board. This could be pasted when responding to a help email in the mailing list. Don't know if this can be done? Could also help identify what icon belongs to what plugin...</p> QGIS Application - Bug report #19072 (Open): saving a virtual layer makes qgis crashhttps://issues.qgis.org/issues/190722018-05-31T08:02:47ZLee Hanmathias.cunault@inrap.fr
<a name="User-Feedback"></a>
<h2 >User Feedback<a href="#User-Feedback" class="wiki-anchor">¶</a></h2>
<p>I was trying to "save as" on my computer, a virtual layer created from 2 shp in my project.<br />I tried 2 times and qgis crashed 2 times.</p>
<a name="Report-Details"></a>
<h2 >Report Details<a href="#Report-Details" class="wiki-anchor">¶</a></h2>
<p><strong>Crash ID</strong>: b1b732ff546db928598cc22bddeb086807097248</p>
<p><strong>Stack Trace</strong><br /><pre>
RaiseException :
_FrameUnwindFilter :
RtlRestoreContext :
QThreadPoolPrivate::reset :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :
</pre></p>
<p><strong>QGIS Info</strong><br />QGIS Version: 3.0.3-Girona<br />QGIS code revision: <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/8a899c8758b30adc3f8d6df682a5702dd3bfe6f0" title="Release of 3.0.3">8a899c8758</a><br />Compiled against Qt: 5.9.2<br />Running against Qt: 5.9.2<br />Compiled against GDAL: 2.2.4<br />Running against GDAL: 2.2.4</p>
<p><strong>System Info</strong><br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 6.1.7601</p> QGIS Application - Feature request #14027 (Open): save as KML data source options should use fiel...https://issues.qgis.org/issues/140272015-12-22T16:46:32ZMathieu Pellerin - nIRVnirvn.asia@gmail.com
<p>It'd be nice for the DescriptionField and NameField data source options (in the "Save as..." dialog) to make use of the fields list dropdown widget instead of a text box.</p>
<p><img src="http://i.imgur.com/Xk8P3pS.png" alt="" /></p> QGIS Application - Feature request #5740 (Open): reclassify grid values - optionshttps://issues.qgis.org/issues/57402012-06-04T12:39:46Zstefano campusskampus@gmail.com
<p>original saga module has the possibility of using external lookout table for reclassification</p> QGIS Application - Feature request #3128 (Open): support for vertical datumhttps://issues.qgis.org/issues/31282010-10-16T22:19:29Zhamish -hamish_b@yahoo.com
<p>Hi,</p>
<p>vertical datum support has recently been added to the trunk versions of most of the PROJ.4/GDAL/libLAS/etc toolchain. it would be great if qgis also could incorporate that newly available metadata, if present. (even if it is just on the layer preferences metadata report tab.</p>
<p>thanks,<br />Hamish</p> QGIS Application - Feature request #3127 (Open): support GRASS color ruleshttps://issues.qgis.org/issues/31272010-10-16T22:15:28Zhamish -hamish_b@yahoo.com
<p>I see qgis has just got some better graduated symbol/color improvements,<br />great! that's been lacking for a long time. Compared to that GRASS's<br />r.colors and v.colors modules are so much more powerful, so until qgis<br />has better raster+vector color support I'd like to set those in GRASS<br />and have QGIS be able to read the color rules from GRASS exported geotiffs<br />and shapefiles. (the people I deliver maps to often run qgis but not grass)</p>
<p>vector: (mostly shapefiles)<br />- it would be great if the point icon's or line's color could be read from<br />an attribute column containing a R:G:B string (0-255). In GRASS see d.vect<br />+ GRASSRGB column (but the column can be called anything). that way you<br />could use v.colors (qgis grass toolbox) to set more powerful color<br />gradients.</p>
<p>- When a <a class="wiki-page new" href="https://issues.qgis.org/projects/qgis/wiki/GeoTiff">GeoTiff</a> is exported from GRASS with r.out.gdal, the first 1000<br />lines of the color rules file (usually there is less than 10) is written<br />to the <a class="wiki-page new" href="https://issues.qgis.org/projects/qgis/wiki/GeoTiff">GeoTiff</a> metadata as "COLOR_TABLE_RULE_RGB_n" where "n" starts at<br />1 and goes up. the rest of the line looks like:<br /> min max R1 G1 B1 R2 G2 B2<br />with RGB values for the min and max within that range. colors for values<br />in between that step are linearly interpolated between R1,R2 etc.<br />Also the new GDAL version seems to be making filename.tif.aux.xml too,<br />which contains those COLOR_TABLE_RULE_RGB_1,2,3,... rules.</p>
<p>the long term idea would be for many OSGeo projects to share a common<br />color formats for these things, so data can be more easily shared.<br />(for what it's worth, GMT and GRASS already are very similar for some<br />things like this, I think it has to do with common code ancestry 15+ years<br />ago, and partly ending up with common solutions after years of trying<br />different methods)</p>
<p>(working on a common .svg icon/symbol pool is another idea along these lines.)</p>
<p>thanks,<br />Hamish</p> QGIS Application - Feature request #2758 (Open): split v.generalize GRASS module in twohttps://issues.qgis.org/issues/27582010-05-28T06:51:23ZPaolo Cavallinicavallini@faunalia.it
<p>As it stans, the v.generalize GRASS module in QGIS is too complex. It would be better to split it in two:</p>
<p>- one for simplification</p>
<p>- one for smoothing</p>
<p>leaving only the options that are relevant for each case.</p> QGIS Application - Feature request #2606 (Open): target field shall be selected automaticallyhttps://issues.qgis.org/issues/26062010-03-29T12:51:30Ztimmie -timmie@foo.bar
<p>Hello,<br />when editing attribute tables, I would prefer that a selected field will automatically be the target of the field calculator results.</p> QGIS Application - Feature request #2577 (Open): r.mapcalculator: variable number of input mapshttps://issues.qgis.org/issues/25772010-03-21T09:57:57ZPaolo Cavallinicavallini@faunalia.it
<p>It would be good to have a variable number of input maps for r.mapcalculator GRASS module. See r.buffer as an example (this approach cannot be used directly, as the underlying GRASS commands are different).</p> QGIS Application - Feature request #2576 (Feedback): reference to dtd wronghttps://issues.qgis.org/issues/25762010-03-21T09:46:46ZPaolo Cavallinicavallini@faunalia.it
<p>In GRASS modules, there is a reference to a dtd:</p>
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE qgisgrassmodule SYSTEM "http://mrcc.com/qgisgrassmodule.dtd">
</pre>
<p>but the URL is non existing. This should be replaced with a valid one.</p> QGIS Application - Feature request #2575 (Open): r.proj unusable?https://issues.qgis.org/issues/25752010-03-21T09:20:57ZPaolo Cavallinicavallini@faunalia.it
<p>Currently, r.proj GRASS module seems unusable. Loaded layers from other locations (to be reprojected) do not appear in the dropdown list, and not even on the map canvas.<br />Furthermore, we suggest to simplify the input layout, using the same approach suggested for v.proj (see <a class="issue tracker-2 status-1 priority-3 priority-" href="https://issues.qgis.org/issues/2573" title="v.proj difficult to use (Open)">#2573</a>)</p> QGIS Application - Feature request #2573 (Open): v.proj difficult to usehttps://issues.qgis.org/issues/25732010-03-21T09:09:58ZPaolo Cavallinicavallini@faunalia.it
<p>Currently, vproj GRASS module is difficult to use: the user has to manually enter layer, mapset, location and gisdbase for the origin layer. We suggest to change this, allowing only loaded layers to be reprojected; in this way no user input is required.<br />The current problem preventing us to implement this is that loaded vectors do not appear in the dropdown menu</p> QGIS Application - Bug report #1893 (Reopened): opening data tables widens the main windowhttps://issues.qgis.org/issues/18932009-08-25T05:20:54ZPaolo Cavallinicavallini@faunalia.it
<p>When opening >=3 tables while in docked mode, the main window becomes very wide, instead of shrinking the space allocated to each table</p> QGIS Application - Feature request #1630 (Open): v.db.addcol: checkbox for data typehttps://issues.qgis.org/issues/16302009-04-05T08:52:47ZPaolo Cavallinicavallini@faunalia.it
<p>In current v.db.addcol, the user has to insert the type (integer, double precision, varchar) of the column by hand. Please replace this with a checkbox</p> QGIS Application - Feature request #1627 (Open): v.distance, v.to.db: add data to vector table as...https://issues.qgis.org/issues/16272009-04-04T23:45:14ZPaolo Cavallinicavallini@faunalia.it
<p>For modules that add data to a table (e.g. v.distance, v.to.db), it would be useful to add data to a new column (incorporating db.addcol), instead of overwriting an existing column.</p>