QGIS Application: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-20T10:17:52ZQGIS Issue Tracking
Redmine Bug report #22105 (Closed): $length return bad valuehttps://issues.qgis.org/issues/221052019-05-20T10:17:52ZLudovic JACQUETludovic.jacquet@correlane.com
<p>On QGIS 3.6.1 when I use $length for obtain the length value, QGIS return a bad value.<br />After a return of a customer who is surprise by the length I test my SHP with QGIS 2.8 and FME workbench 2016. I have the same length whith FME, QGIS 2.8 and customer software.</p> Bug report #22077 (Rejected): Priority in labelling not greyed out when data defined settings are...https://issues.qgis.org/issues/220772019-05-14T15:06:44Zmatteo ghettamatteo.ghetta@gmail.com
<p>If a default field or expression is used to overwrite the default behavior of `Placement -> Priority` option, the slider is still movable by the user. The final behavior is still that from field/expression, but it could be lead to some confusion.</p> Bug report #22071 (Closed): Relation reference widget wrong feature when "on map identification"https://issues.qgis.org/issues/220712019-05-14T07:51:13Zmatteo ghettamatteo.ghetta@gmail.com
<p>If confirmed I think something is really weird. In attach the complete project.</p>
<ul>
<li>line layer with ID field</li>
<li>table layer with FK field</li>
<li>1:N relation between line ID (parent) and table FK (child)</li>
<li>table FK widget type set (automatically) as "relation reference" and the "On map identification" checkbox checked</li>
<li>adding a line in the table layer and clicking on the "identify on map" button</li>
<li>the FK field of the table layer is set to line layer ID - 1 (so when the line ID is 2 the FK of the table is 1)</li>
</ul>
<p>Verified with the same project in QGIS 3.4.6 and master</p> Bug report #22035 (Closed): "Export to PostgreSQL" python error if rather schema has an uppercase...https://issues.qgis.org/issues/220352019-05-09T11:59:55ZGiovanni Manghigiovanni.manghi@gmail.com
<p>QGIS version: 3.6.2-Noosa<br />QGIS code revision: 656500e<br />Qt version: 5.9.5<br />GDAL version: 2.2.3<br />GEOS version: 3.6.2-CAPI-1.10.2 4d2925d6<br />PROJ version: 493<br />Processing algorithm…<br />Algorithm 'Export to PostgreSQL' starting…<br />Input parameters:
{ 'CREATEINDEX' : True, 'DATABASE' : 'locale', 'DROP_STRING_LENGTH' : False, 'ENCODING' : 'UTF-8', 'FORCE_SINGLEPART' : False, 'GEOMETRY_COLUMN' : 'geom', 'INPUT' : '/media/giovanni/DATA/training/data/portugal_3763/areas_protegidas.shp', 'LOWERCASE_NAMES' : True, 'OVERWRITE' : True, 'PRIMARY_KEY' : None, 'SCHEMA' : 'Teste1', 'TABLENAME' : '' }</p>
<p>Traceback (most recent call last):<br />File "/usr/share/qgis/python/plugins/processing/tools/postgis.py", line 826, in _exec_sql<br />cursor.execute(sql)<br />psycopg2.ProgrammingError: relation "teste1.areas_protegidas" does not exist</p>
<p>During handling of the above exception, another exception occurred:</p>
<p>Traceback (most recent call last):<br />File "/usr/share/qgis/python/plugins/processing/tools/postgis.py", line 838, in _exec_sql_and_commit<br />self._exec_sql(c, sql)<br />File "/usr/share/qgis/python/plugins/processing/tools/postgis.py", line 829, in _exec_sql<br />e.cursor.query.decode(e.cursor.connection.encoding))<br />_core.QgsProcessingException: relation "teste1.areas_protegidas" does not exist<br />QUERY: CREATE INDEX sidx_areas_protegidas_geom ON Teste1.areas_protegidas USING <abbr title="geom">GIST</abbr></p>
<p>During handling of the above exception, another exception occurred:</p>
<p>Traceback (most recent call last):<br />File "/usr/share/qgis/python/plugins/processing/algs/qgis/ImportIntoPostGIS.py", line 204, in processAlgorithm<br />db.create_spatial_index(table, schema, geomColumn)<br />File "/usr/share/qgis/python/plugins/processing/tools/postgis.py", line 727, in create_spatial_index<br />self._exec_sql_and_commit(sql)<br />File "/usr/share/qgis/python/plugins/processing/tools/postgis.py", line 840, in _exec_sql_and_commit<br />except DbError:<br />NameError: name 'DbError' is not defined</p> Bug report #22033 (Closed): DB Manger imports the wrong datahttps://issues.qgis.org/issues/220332019-05-09T11:45:59ZGiovanni Manghigiovanni.manghi@gmail.com
<p>Create a project</p>
<p>add a shapefile, suppose is named "layer1"</p>
<p>open db manager</p>
<p>select "import layer/file", the input layer shown by default will be "layer1"</p>
<p>click on the "..." button to go pick another shapefile (i.e. "layer2") from the file system</p>
<p>import it (after eventually having changed its name and import parameters)</p>
<p>actually the layer that will be imported is "layer1"</p> Bug report #21917 (Closed): QGIS server ignores custom rendering order when loading parent grouphttps://issues.qgis.org/issues/219172019-04-24T09:48:57ZAndreas Neumann
<p>When a project has custom layer rendering order (checkbox "control rendering order" enabled in the "layer order" panel), and the user loads the root layer as a single WMS layer in a WMS client (e.g. QGIS), the custom layer rendering order is not correctly taken into account.</p>
<p>Here is an example service, served with QGIS server 3.6.x (recent build) and attached are three screenshots: one with the connection parameters, the other two with the rendering as it should appear (original project files) and the other with the invalid rendering order when loading the service with the root layer. Note in the screenshot that point symbols (circles) should always be rendered on top, and also other layers are mixed up.</p>
<p><a class="external" href="https://services.geo.zg.ch/ows/rp">https://services.geo.zg.ch/ows/rp</a></p>
<p>The data source is Postgis. A Postgis dump-file and the project file will be provided to the person working on fixing the issue.</p> Bug report #21871 (Closed): LAYERFONTCOLOR ignored in GetLegendGraphic WMShttps://issues.qgis.org/issues/218712019-04-17T09:23:56ZAlessandro Pasotti
<p>It's not implemented in QGIS 3</p> Bug report #21870 (Closed): ITEMFONTCOLOR ignored in GetLegendGraphic WMShttps://issues.qgis.org/issues/218702019-04-17T08:23:50ZAlessandro Pasotti
<pre>
http://localhost:8000/ows/?map=TestSVGSymbols.qgs&SERVICE=WMS&VERSION=1.3.0&ITEMFONTCOLOR=%23ff0000&REQUEST=GetLegendGraphic&LAYER=zg.haltestellen&FORMAT=image/png&STYLE=default&SLD_VERSION=1.1.0&TRANSPARENT=true
</pre>
<p>Apparently it was not implemented in 3.x.</p> Bug report #21856 (Closed): QGIS crashed while using QgsVectorFileWriterhttps://issues.qgis.org/issues/218562019-04-15T20:04:35ZBill Mitchellwjm@ufl.edu
<p>QGIS consistently crashes when I run the following script in the Python console.</p>
<pre>
from qgis.core import (
QgsVectorLayer,
QgsField, QgsFields,
# QgsFeatureSource,
# QgsFeatureSink,
# QgsProject,
QgsWkbTypes,
QgsVectorFileWriter,
)
baseDir = "/Users/mitchell/Dropbox/python/import_gpx"
gpxFile = f"{baseDir}/../gps/Waypoints_01-MAR-18.gpx"
sourceLayer = QgsVectorLayer(gpxFile, "testFile", "GPX")
error, errormsg = QgsVectorFileWriter.writeAsVectorFormat(
layer=sourceLayer,
fileName="test.gpkg",
fileEncoding="utf-8",
destCRS=QgsCoordinateReferenceSystem('EPSG:4326'),
driverName="GPKG",
)
if error:
print(f"{error} --- {errormsg}")
</pre>
<p>I have attached the crash report.</p> Bug report #8729 (Closed): Microsoft visual C++ Runtime Library Errorhttps://issues.qgis.org/issues/87292013-10-01T00:22:39ZAbdelilah ADIBAabdelilahadiba@gmail.com
<p>this error occurs when launching Qgis 2.0.1 64bit version , you can see the error in the attached picture. but Qgis is working properly</p> Bug report #811 (Closed): selectionChanged() SIGNAL getting connected and disconnected on raster ...https://issues.qgis.org/issues/8112007-11-15T10:38:26ZAaron Racicot -aaronr@z-pulley.com
<p>In qgsmapcanvas.cpp in <a class="wiki-page new" href="https://issues.qgis.org/projects/qgis/wiki/QgsMapCanvas">QgsMapCanvas</a>::setLayerSet a disconnect and connect call to selectionChanged signal are being made on the map layer set, but some of those layers can be raster layers. selectionChanged() is a signal that only vector layers can emit.</p>
<p>This bug causes warning messages to appear when calling setLayerSet via the python bindings with a layer set that contains rasters.</p>
<p>The solution is to wrap the disconnect and connect calls with logic to test if the layer is a vector layer.</p> Bug report #800 (Closed): 'Search' in on the fly projection dialogue missplacedhttps://issues.qgis.org/issues/8002007-11-10T23:57:48ZMaciej Sieczka -tutey@o2.pl
<p>See the attached screendump. SVN 7373, built and running against QT 4.3.1.</p> Bug report #722 (Closed): LCC projection not recognized (EPSG 3358)https://issues.qgis.org/issues/7222007-06-03T12:32:21ZMarkus Neteler
<p>Hi,</p>
<p>it appears that QGIS fails to recognize <abbr title="HARN">NAD83</abbr> / North Carolina LCC:</p>
<pre>
Warning: [[QgsSpatialRefSys]]::getRecord failed : select * from tbl_srs where parameters='+proj=lcc +lat_1=34.33333333333334 +lat_2=36.16666666666666 +lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +ellps=GRS80 +datum=NAD83 +units=m +no_defs'
Warning: [[QgsSpatialRefSys]]::findMatchingProj -------> no match found in user db
Warning: QPainter::begin: Painter already active
Warning: QPainter::begin: Painter already active
Warning: [[QgsSpatialRefSys]]::createFromSrsId failed : select srs_id,description,projection_acronym,ellipsoid_acronym,parameters,srid,epsg,is_geo from tbl_srs where srs_id='-1223020544'
</pre>
<p>The reason will be that the EPSG definition in PROJ4 is this:</p>
<pre>
# NAD83(HARN) / North Carolina
<3358> +proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334 +lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +ellps=GRS80 +units=m +no_defs <>
</pre>
<p>Note that the values of lat_1 and lat_2 are reverted. I was told by Frank W. that this is legal (to my shame I already submitted a bug report to EPSG). It would be good if QGIS accepted the reverted lat_1 and lat_2, too.</p>
<p>Best,<br />Markus</p> Bug report #572 (Closed): change any property of a vector layer (transparency, labels etc.) = the...https://issues.qgis.org/issues/5722007-02-05T23:38:16ZRedmine Admin
<p>This is not necessary, and happens to be diturbing - I have to re-collapse the layer each time I change it's transparency percentage, or any other property.</p>
<p>Maciek</p> Bug report #556 (Closed): Field should be Layer in GRASS lingohttps://issues.qgis.org/issues/5562007-01-30T00:47:07ZRedmine Admin
<p>0.8 SVN 6453</p>
<p>Please update all the occurences of "Field" term in relation to GRASS vectors to "Layer". These are two same things, but Field has been replaced by Layer many months ago in GRASS.</p>
<p>Things to update are, AFAIK:</p>
<p>1. GRASS Edit's attribute editor still mentions "Field"</p>
<p>2. GRASS Edit's "Table" tab mentions "Field (layer)"</p>
<p>Maciek</p>