QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-22T07:16:59ZQGIS Issue Tracking
Redmine QGIS Application - Bug report #22120 (Open): Field_name in actionshttps://issues.qgis.org/issues/221202019-05-22T07:16:59ZAlessandro Peregoalsper78@gmail.com
<p>(tested on QGIS 3.4.8 on Windows 10)</p>
<p>Actions in field scope have three variables: field_index, field_name, field_value.<br />Field_name doesn’t work when actions run from attribute table.</p>
<p>For example the following python action (in field scope):</p>
<p>from qgis.PyQt import QtWidgets<br />expr = '"[% @field_name <span>]"' + ' = ' + "'[</span> @field_value <span>]'" <br />QtWidgets.QMessageBox.information(None, "[</span> @field_name %]", expr)</p>
<p>works good from Identify Result panel, but when the action run from the attribute table it doesn’t show the name of the field.</p>
<p>A workaround is using the field index:<br />layer = QgsProject.instance().mapLayer('[% @layer_id <span>]')<br />field_name = layer.fields().field([</span> @field_index %]).name()</p> QGIS Application - 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> QGIS Application - Feature request #21990 (Open): [processing][xyz tiles] warn user when overwrit...https://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> QGIS Application - Feature request #21989 (Open): [processing][xyz tiles]Allow option to export ...https://issues.qgis.org/issues/219892019-05-03T12:30:26ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<p>Currently, user can only choose one option</p> QGIS Application - Bug report #21988 (Open): [processing][xyz tiles] De-activate folder/file bas...https://issues.qgis.org/issues/219882019-05-03T12:29:11ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<p>Currently, if user selects director or MBTiles, both output paths are activated. Best, to deactivate the unused one.</p> QGIS Application - Bug report #21972 (Open): inside the Layer's panel, can't see if a layer is ch...https://issues.qgis.org/issues/219722019-05-02T08:29:22Zc mcle.ine@free.fr
<p>inside the layer's panel, at each beginning of line (1 line = 1 layer)<br />there's a checkbox, in black & white.<br />as the whole line can be highlighted (in dark blue) when you click on it, you can't see if this layer is checked or not any more.</p>
<p>see attached snapshot</p> QGIS Application - Bug report #21936 (Open): Snapping Settings window with Night Mapping, low rea...https://issues.qgis.org/issues/219362019-04-26T10:24:52ZNicklas Larssonn_larsson@yahoo.com
<p>The Snapping Settings window has an inconsistent layout and partly very difficult to read due to low contrast with Night Mapping theme (at least on macOS).</p>
<p>This is the present layout:<br /><img src="https://issues.qgis.org/attachments/download/14850/Screenshot.png" alt="" /></p>
<p>Suggested changes:</p>
<p>1. The checkboxes (Layer and Avoid intersection) should be dark grey not black<br />2. The checkmark in Layer should be light grey<br />3. The Layer name should be dark or light grey depending on checked or not</p>
<p><img src="https://issues.qgis.org/attachments/download/14851/Mockup.png" alt="" /></p> QGIS Application - Feature request #21904 (Open): Suggest update only if is available for the cur...https://issues.qgis.org/issues/219042019-04-23T00:20:06ZJorge Usechejorgenator2@yahoo.es
<p>I'm using QGIS Desktop in macOS, the software suggest me to update to a newest version, but It is not available for my platform.</p> QGIS Application - Feature request #21889 (Open): Save Layer As targeting PostGIS and scratch layershttps://issues.qgis.org/issues/218892019-04-20T00:57:44ZThomas Koskitk@nuevomidstream.com
<p>In the export menu there are many options for Save Layer As, but not included are a scratch layer or to a PostGIS database. Both of these would be helpful, and their omission is puzzling.</p> QGIS Application - Feature request #21800 (Open): Layer Order panel: support for groups?https://issues.qgis.org/issues/218002019-04-08T16:57:41ZGarth Fletchergarth@jacqcad.com
<p>When a project contains hundreds of layers, the Layer Order Panel becomes awkward to navigate. Moving a layer can involve dragging it over hundreds of other layers.</p>
<p>I wonder if a "group" feature might improve the interface. This would be similar to, but independent of, the grouping scheme used in the Layer Panel</p>
<p>For example, a large set of orthophoto tiles would all be moved together and there is never a need to insert some other layer into the middle of the set. If a Group could be defined to include just those tiles, when collapsed it would shorten the layer list and ease moving other layers past it. Similar groups could be used for other related sets of layers.</p>
<p>Support would be needed for creating a group, dragging layers into (or out of) a group, collapsing or expanding a group, and possibly for deleting an empty group.</p> QGIS Plugin Site - Bug report #21715 (Open): Add "Requirements" as optional field in metadata.txthttps://issues.qgis.org/issues/217152019-03-31T16:39:36ZSfkeller -sfkeller@gmail.com
<p>As a user when searching and browsing for a plugin in QGIS extension manager or on the website <a class="external" href="https://plugins.qgis.org/">https://plugins.qgis.org/</a> , users should be informed before hand about the requirements, dependencies and restrictions of a plugin.</p>
<p>There is currently a newly added text in the "Recommendation" chapter on <a class="external" href="https://plugins.qgis.org/publish/">https://plugins.qgis.org/publish/</a> to mention requirements, dependencies and restrictions in the About/Description field, if the plugin is running only on selected platforms, requires software to be installed separately or requires some user account.</p>
<p>My suggestion is to add an optional field - perhaps called "requirements" - in metadata.txt, to be filled in by the plugin maintainer. The field entry would be mandatory if there exist such requirements.</p>
<p>Some dependencies and restrictions could even be potentially validated automatically.</p> QGIS Application - Feature request #21695 (Open): Improve behavior of Geopackage Data Importhttps://issues.qgis.org/issues/216952019-03-28T19:57:29ZBrett CarlockSynper311@aol.com
<p>Related to <a class="issue tracker-1 status-1 priority-5 priority-" href="https://issues.qgis.org/issues/21694" title="Hang/Crash when attempting to drag&drop multiple layers into gpkg (Open)">#21694</a> :<br />I'd like to see the process of batch importing be easy for geopackages. A GUI dialog to load multiple layers would be great in addition to the current drag/drop method.</p>
<p>I'd also like to see the confirmation dialog not pop up for each and every layer imported one by one. A statusbar on a dialog showing currently importing layer, progress bar, and layer # out of total layer # would be far more helpful, with the option to confirm/close the dialog upon completion of the import.</p> QGIS Application - Feature request #21440 (Open): MDAL: improve the style of wind arrowshttps://issues.qgis.org/issues/214402019-03-01T13:43:11ZPaolo Cavallinicavallini@faunalia.it
<p>The standard representation of wind arrows is more complex that what is currently displayed for MDAL data (see e.g. <a class="external" href="http://ww2010.atmos.uiuc.edu/(Gh)/guides/maps/sfcobs/wnd.rxml">http://ww2010.atmos.uiuc.edu/(Gh)/guides/maps/sfcobs/wnd.rxml</a>). It would be good to add this style as default for wind.</p> QGIS Application - Bug report #17980 (Open): "resources/data/world_map.shp" should be only access...https://issues.qgis.org/issues/179802018-01-27T14:33:45ZJohannes Kroeger
<p>QGIS tells me<br /><pre>
Warning 4: Failed to open /opt/qgis-git/share/qgis/resources/data/world_map.shp, Permission denied.
</pre></p>
<p>The file exists and is world readable<br /><pre>
-rw-r--r-- 1 root root 528032 Jan 23 23:06 /opt/qgis-git/share/qgis/resources/data/world_map.shp
</pre></p>
<p>strace suggests that QGIS is trying to access the file with write access.<br /><pre>
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDONLY) = 76
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDWR) = -1 EACCES (Permission denied)
stat("/opt/qgis-git/share/qgis/resources/data/world_map.shp", {st_mode=S_IFREG|0644, st_size=528032, ...}) = 0
stat("/opt/qgis-git/share/qgis/resources/data/world_map.shp", {st_mode=S_IFREG|0644, st_size=528032, ...}) = 0
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDONLY) = 76
stat("/opt/qgis-git/share/qgis/resources/data/world_map.shp", {st_mode=S_IFREG|0644, st_size=528032, ...}) = 0
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDWR) = -1 EACCES (Permission denied)
</pre></p>
<p>As the file is used as source for the CRS display it does only require read access.</p>
<p>Opening it in read-only mode should get rid of the warning and be what was intended. :)</p> QGIS Application - Bug report #16317 (Open): Adding the same short_name option on multiple layers...https://issues.qgis.org/issues/163172017-03-08T03:49:40ZTudor Bărăscutudorbarascu@yahoo.com
<p>Adding the same short_name option on multiple layers is possible.<br />Accessing that short_name in a GetMap request results in only the first layer that was given that specific short_name to be called.<br />This could lead to confusion for big projects where by accident people use the same short_name for multiple layers.</p>
<p>How to reproduce:<br />Use the same short_name for at least two layers.<br />The GetMap request using the short_name point to the first layer that was given short_name.</p>