QGIS Application: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2018-11-06T15:24:40ZQGIS Issue Tracking
Redmine Bug report #20387 (Open): The call to matplotlib tricontour causes QGIS to crashhttps://issues.qgis.org/issues/203872018-11-06T15:24:40ZOndrej Lexalexa.ondrej@gmail.com
<p>Developing plugin, I found that QGIS 3.4 crashes during calculation of matplotlib.tri.Triangulation. The problem appears only running matplotlib.tri.Triangulation within the QGIS3 python environment. The problem has been reported already in QGIS 3.1 (<a class="external" href="https://github.com/ccrook/QGIS-Contour-Plugin/issues/23">https://github.com/ccrook/QGIS-Contour-Plugin/issues/23</a>) and the workaround is to calculate Triangulation in shell script, save the result to file and import back to QGIS python session. I'm using QGIS version 3.4.1-Madeira QGIS code revision 383851c, Python 3.6.6, matplotlib 2.1.1 on Ubuntu 18.04.</p>
<p>Example python code to crash QGIS</p>
<pre>
import matplotlib.pyplot as plt
import matplotlib.tri as tri
import numpy as np
radii = np.linspace(0.25, 0.95, 8)
angles = np.linspace(0, 2*np.pi, 36, endpoint=False)
angles = np.repeat(angles[..., np.newaxis], 8, axis=1)
angles[:, 1::2] += pi/n_angles
x = (radii*np.cos(angles)).flatten()
y = (radii*np.sin(angles)).flatten()
# This call crahes QGIS
triang = tri.Triangulation(x, y)
</pre> Bug report #20379 (Open): Attributes forms and problem with setting variables as defaults (QGIS 3...https://issues.qgis.org/issues/203792018-11-06T10:19:59ZJadwiga TrojakJadwiga.Trojak@gmail.com
<p>I have geopackage layer with two fields: user and data_mod. I'd like to set default value for user field with @user_account_name variable (widget type: Text Edit) and for data_mod field with function now() (widget type: Date/Time). In the first case, after clicking Apply button, this settings aren't save, and the default value changes automatically to 'NULL'. In the second case, default value changes automatically to exact date, not date from variable now().</p> Bug report #20367 (Open): "avoid intesection" cannot be enabled without activating snappinghttps://issues.qgis.org/issues/203672018-11-05T13:46:20ZAntonio Viscomiantoviscomi@gmail.com
<p><strong>New description:</strong></p>
<p>Subject says it all. This is NOT the case in 2.18.</p>
<p><strong>Old description:</strong></p>
<p>Hi all,<br />I noticed this bug:<br />- activate advanced snapping configuration enabling "Avoid Intersection" option on two layers;<br />- then I deactivate snap on one of two layers (but "Avoid Intersection" flag was not syncronized with layer flag);<br />- I tried to create a new polygon in my feature, but editing came out with error (geometry is collapsed);<br />- then I deactivated "Avoid Intersection" from unflagged layer;<br />- I created the new geometry and all works fine.</p>
<p>I attach a screencast that show this</p> Bug report #20327 (Open): Grass crashes when try to create mapsethttps://issues.qgis.org/issues/203272018-11-02T10:19:22ZVitor Silvavitordasilvaphotography@gmail.com
<p>Hi,</p>
<p>I can´t create a mpaset in QGIS, always crash at this moment.<br />The report is this:</p>
<p>Crash ID: f3b94088ad28fd40600a5d0e06b9c43ac6243e50</p>
<p>Stack Trace</p>
<p>RtlRaiseStatus :<br />memset :<br />setjmpex :<br />G_fatal_error :<br />G_getenv :<br />read_datum_table :<br />GPJ_osr_to_grass :<br />GPJ_wkt_to_grass :<br />version :<br />version :<br />QMetaObject::activate :<br />QWizard::subTitleFormat :<br />QWizard::next :<br />QMetaObject::activate :<br />QAbstractButton::clicked :<br />QAbstractButton::click :<br />QAbstractButton::mouseReleaseEvent :<br />QWidget::event :<br />QApplicationPrivate::notify_helper :<br />QApplication::notify :<br />QgsApplication::notify :<br />QCoreApplication::notifyInternal2 :<br />QApplicationPrivate::sendMouseEvent :<br />QSizePolicy::QSizePolicy :<br />QSizePolicy::QSizePolicy :<br />QApplicationPrivate::notify_helper :<br />QApplication::notify :<br />QgsApplication::notify :<br />QCoreApplication::notifyInternal2 :<br />QGuiApplicationPrivate::processMouseEvent :<br />QWindowSystemInterface::sendWindowSystemEvents :<br />QEventDispatcherWin32::processEvents :<br />CallWindowProcW :<br />DispatchMessageW :<br />QEventDispatcherWin32::processEvents :<br />qt_plugin_query_metadata :<br />QEventLoop::exec :<br />QCoreApplication::exec :<br />main :<br />BaseThreadInitThunk :<br />RtlUserThreadStart :</p>
<p>QGIS Info<br />QGIS Version: 3.4.0-Madeira<br />QGIS code revision: 4a4b62ed19<br />Compiled against Qt: 5.11.2<br />Running against Qt: 5.11.2<br />Compiled against GDAL: 2.3.2<br />Running against GDAL: 2.3.2</p>
<p>System Info<br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 10.0.17134</p> Bug report #20301 (Open): Off-Line editing should NOT ask to fill manually the PK fieldhttps://issues.qgis.org/issues/203012018-10-31T17:06:14ZGiovanni Manghigiovanni.manghi@gmail.com
<p>QGIS 2.18:</p>
<p>add a postgis layer<br />put it in off-line mode<br />edit it (add feature) > is NOT asked to fill (not mandatory) the field that represent the PK in pgsql<br />synchronize it back > all OK (the new feature is given a proper value for the PK field)</p>
<p>QGIS 3.4:</p>
<p>add a postgis layer<br />put it in off-line mode (spatialite or geopackage)<br />edit it (add feature) > the field that represent the PK is marked as mandatory and the user must fill it manually to be able to synchronize back. This of course can cause errors.</p>
<p>Also when using GPKG: <a class="issue tracker-1 status-5 priority-5 priority- closed" href="https://issues.qgis.org/issues/20276" title="Off-Line editing: attributes are shifted when using GPKG as off-line format (Closed)">#20276</a></p> Bug report #20071 (Open): "Show feature count" on a rule based renderer gives wrong result for th...https://issues.qgis.org/issues/200712018-10-10T13:47:18ZHarrissou Santanna
<p>This is a revival of <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/13999" title=""Show feature count" on a rule based gives wrong result for the "ELSE" statement. (Closed)">#13999</a>.<br />In the attached screenshots, I use the Else shortcut in one case and the full rule in the other. counted features are not the same:</p>
<p>1/ The "Route secondaire" level "instead of displaying 0" <a class="issue tracker-1 status-1 priority-5 priority-" href="https://issues.qgis.org/issues/20070" title="In rule based renderer, "Show feature count" returns 0 if no symbol is activated (Open)">#20070</a>, would return 296389 in one case (correct!) and, 304445 with the Else rule (corresponding to the whole layer).</p>
<p>2/ At the bottom of the rules, the <em>Autres</em> nature subclass should return 213037 features as of</p>
<p><code>select count(nature) from layer where importance not in ('1','2') and nature not in ('Bac auto', 'Escalier','Piste cyclable','Sentier','Chemin')</code></p>
but it instead returns the same value shown at its upper level:
<ul>
<li>296389 features which is the result of <code>select count(nature) from layer where importance not in ('1','2')</code></li>
<li>or 304445 features with the Else rule used for "Route secondaire".</li>
</ul> Bug report #20070 (Open): In rule based renderer, "Show feature count" returns 0 if no symbol is ...https://issues.qgis.org/issues/200702018-10-10T13:45:49ZHarrissou Santanna
<p>In rule based renderer, "show features count" does not return the count for any rule that has its symbol disabled. See screenshots.</p>
<p>Set the issue as high because it makes the feature unreliable. The count returned by the rule should not rely on whether a symbol is configured for the feature.</p> Bug report #19881 (Open): Impossible to choose several fields at the same time to drag and drop i...https://issues.qgis.org/issues/198812018-09-18T13:03:58ZAlain FERRATON
<p>In versions prior to 3.0, it was possible to choose several fields at the same time to drag and drop them into the designer.<br />It is no longer possible in the new design</p>
<p>(It also lacks the field assignment button and the up and down buttons).</p> Bug report #19793 (Open): MSSQL: Poor initial QGIS 3.2.2 starting performance when getting data f...https://issues.qgis.org/issues/197932018-09-07T10:02:28ZAlexander Zidekalexander.zidek@outlook.com
<p>Description:
============<br />Opening a .QGS which has a layer from a MS SQL Server view, takes drastically more startup<br />time than when the layer is connection directly with the underlying table/featureclass.<br />The difference in my testcase from ~1 sec. to ~157 sec. (see below), <br />and occurs at everyone QGIS start up! <br /> <br />Testcase & side conditions:
===========================<br />I did some evaluation and testing with the SQL Server Profiler and a <br />table/featureclass with ~ 1.7 millions rows/objects.<br /> <br />Here are the results of the profiling:<br /> <br />1. SQL Trace from starting qgis with the underlying table/featureclass its.dkm_gst => execution time ~1sec.<br /> <br />-----------------------------------------------------------------------------------------------<br />exec sp_datatype_info 11<br />go<br />SET QUOTED_IDENTIFIER ON<br />go<br />SELECT name FROM sys.columns WHERE is_computed = 1 AND object_id = OBJECT_ID('[its].[DKM_GST]')<br />go<br />exec sp_columns @table_name = N'DKM_GST', @table_owner = 'its'<br />go<br />exec sp_pkeys @table_name = N'DKM_GST', @table_owner = 'its' <br />go<br />SELECT min(bounding_box_xmin), min(bounding_box_ymin), max(bounding_box_xmax), max(bounding_box_ymax) FROM sys.spatial_index_tessellations WHERE object_id = OBJECT_ID('[its].[DKM_GST]')<br />go<br />SET QUOTED_IDENTIFIER ON<br />go<br />SELECT [OBJECTID],[SHAPE]FROM [its].[DKM_GST] where [SHAPE].STIsValid() = 1 AND [SHAPE].STIntersects([geometry]::STGeomFromText('<abbr title="(51135.43335196328553138 337616.30806105613010004, 54384.13471333117195172 337616.30806105613010004, 54384.13471333117195172 339607.60543165361741558, 51135.43335196328553138 339607.60543165361741558, 51135.43335196328553138 337616.30806105613010004">POLYGON</abbr>)',31255)) = 1<br />go<br />SET QUOTED_IDENTIFIER ON<br />go<br />SELECT [OBJECTID],[SHAPE]FROM [its].[DKM_GST] where [SHAPE].STIsValid() = 1 AND [SHAPE].STIntersects([geometry]::STGeomFromText('<abbr title="(51135.43335196328553138 337616.30806105613010004, 54384.13471333117195172 337616.30806105613010004, 54384.13471333117195172 339607.60543165361741558, 51135.43335196328553138 339607.60543165361741558, 51135.43335196328553138 337616.30806105613010004">POLYGON</abbr>)',31255)) = 1<br />go<br />-----------------------------------------------------------------------------------------------<br /> <br />2. SQL trace from starting qgis with the corresponding flat view its.v_dkm_gst (=> select * from [its].[DKM_GST]) => execution time ~157 sec.<br /> <br />-----------------------------------------------------------------------------------------------<br />exec sp_datatype_info 11<br />go<br />SET QUOTED_IDENTIFIER ON<br />go<br />SELECT name FROM sys.columns WHERE is_computed = 1 AND object_id = OBJECT_ID('[its].[v_DKM_GST]')<br />go<br />exec sp_columns @table_name = N'v_DKM_GST', @table_owner = 'its'<br />go<br />exec sp_pkeys @table_name = N'v_DKM_GST', @table_owner = 'its' <br />go<br />select count(distinct [OBJECTID]), count([OBJECTID]) from [its].[v_DKM_GST]<br />go<br />SELECT min(bounding_box_xmin), min(bounding_box_ymin), max(bounding_box_xmax), max(bounding_box_ymax) FROM sys.spatial_index_tessellations WHERE object_id = OBJECT_ID('[its].[v_DKM_GST]')<br />go<br />select min([SHAPE].MakeValid().STPointN(1).STX), min([SHAPE].MakeValid().STPointN(1).STY), max([SHAPE].MakeValid().STPointN(1).STX), max([SHAPE].MakeValid().STPointN(1).STY) from [its].[v_DKM_GST]<br />go<br />SET QUOTED_IDENTIFIER ON<br />go<br />SELECT [OBJECTID],[SHAPE]FROM [its].[v_DKM_GST] where [SHAPE].STIsValid() = 1 AND [SHAPE].STIntersects([geometry]::STGeomFromText('<abbr title="(51135.43335196328553138 337616.30806105613010004, 54384.13471333117195172 337616.30806105613010004, 54384.13471333117195172 339607.60543165361741558, 51135.43335196328553138 339607.60543165361741558, 51135.43335196328553138 337616.30806105613010004">POLYGON</abbr>)',31255)) = 1<br />go<br />SET QUOTED_IDENTIFIER ON<br />go<br />SELECT [OBJECTID],[SHAPE]FROM [its].[v_DKM_GST] where [SHAPE].STIsValid() = 1 AND [SHAPE].STIntersects([geometry]::STGeomFromText('<abbr title="(51135.43335196328553138 337616.30806105613010004, 54384.13471333117195172 337616.30806105613010004, 54384.13471333117195172 339607.60543165361741558, 51135.43335196328553138 339607.60543165361741558, 51135.43335196328553138 337616.30806105613010004">POLYGON</abbr>)',31255)) = 1<br />go<br />-----------------------------------------------------------------------------------------------<br /> <br />Reason:
=======</p>
<p>=> Detecting the bounding box of the layer! takes ~156 sec. (1.700.000 rows!!!)<br /> <br />select min([SHAPE].MakeValid().STPointN(1).STX), min([SHAPE].MakeValid().STPointN(1).STY), max([SHAPE].MakeValid().STPointN(1).STX), max([SHAPE].MakeValid().STPointN(1).STY) from [its].[v_DKM_GST]<br />go<br /> <br />In case of the layer directly connected to the table the query<br /> <br />SELECT min(bounding_box_xmin), min(bounding_box_ymin), max(bounding_box_xmax), max(bounding_box_ymax) FROM sys.spatial_index_tessellations WHERE object_id = OBJECT_ID('[its].[DKM_GST]')<br /> <br />returns the bounding box via the SQL Server Metatable,<br /> <br />In case of the view <br /> <br />SELECT min(bounding_box_xmin), min(bounding_box_ymin), max(bounding_box_xmax), max(bounding_box_ymax) FROM sys.spatial_index_tessellations WHERE object_id = OBJECT_ID('[its].[v_DKM_GST]')<br />go<br /> <br />returns Null (of course is not physical table)!<br /> <br />Solution Proposals:
===================<br />Extending the qgis metatable "dbo.geometry_columns" with 4 bounding box fields and also a field for the primary key,<br />than the detection of the bounding box and the primary key field goes to the responsibility of the project/db-administration!?! <br /> <br />Manually inserting into the "sys.spatial_index_tessellations" with a dummy record doesn't work, because<br />it's forbidden => Ad hoc updates to system catalogs are not allowed!<br /> <br />After the initial startup, any further action (Zooming, Panning, etc.) works with the same excellent performance as with the underlying table!<br /> <br />Hopefully I could describe the issue sharply, thanks in Advance!<br />Alex<br /> <br />PS: I assigned the priority to high, because under enterprise conditions often you have<br /> no direct access to the underlying tables and of course it occurs on each QGIS starting!<br /> I didn't test it under QGIS Server conditions.</p> Bug report #18917 (Open): QGIS 3 "Meters at Scale" incorrect behaviorhttps://issues.qgis.org/issues/189172018-05-06T19:32:22ZMark Newboldmark@dogfeathers.com
<p>I tried using "Meters at Scale" to set the sizes of symbols in layer styles. I don't find "Meters at Scale" documented, but what I think it "should" do is set a size in actual meters (on the earth), independent of latitude and independent of CRS. I am finding that "Meters at Scale" does not equal actual meters and its behavior changes depending on the Project CRS, with scaling depending on latitude.</p>
<p>Steps to duplicate:<br /> 1. Create a new QGIS project.<br /> 2. Set the project CRS to WGS 84, EPSG:4326.<br /> 3. Make a new temporary scratch layer with MultiLineString / MultiCurve geometry, with CRS of EPSG:4326 - WGS 84.<br /> 4. Add a horizontal line feature near 48 degrees north latitude. Style the line as "Simple line" with a "Stroke width" of 100 "Meters at Scale".<br /> 5. Zoom in on the line and measure its width with the Measure tool. It measures around 149.5 meters. Shouldn't it be 100 meters wide? The 149.5 meters width seems to be 100/cos(48°).<br /> 6. Now, just for fun, change the project CRS to WGS 84 / Pseudo Mercator, EPSG:3857. When you hit "Apply", the line snaps to a smaller width, which measures as 66.8 meters. It went from too large to too small. The 66.8 meters width seems to be 100*cos(48°) -- now multiplied by the cosine rather than divided. I can't imagine that this kind of CRS dependence is correct behavior.</p>
<p>If I follow the above steps, but draw the line at the equator instead at 48 degrees north latitude, its width measures 100 meters, independent of project CRS.</p>
<p>I also tried it with point geometry, styled with a Simple marker -- a square symbol, sized at 100 "Meters at Scale". Same result.</p>
<p>Regards,<br /> --Mark</p> Bug report #18668 (Open): integrated document viewer not workinghttps://issues.qgis.org/issues/186682018-04-09T10:07:59ZImaduddin Idriskwerta@gmail.com
<p>I'm using integrated document viewer in the attachment widget, the photo doesn't show up properly only showing small images.<br />But when I using photo widget on qgis 2.18 version, its working well</p> Bug report #18552 (Open): If make new systems in units=km, then scale in view is very wrong.. https://issues.qgis.org/issues/185522018-03-27T04:53:10ZTimur Aptikeev777-ata@rambler.ru
<p>If make new systems in units=km, like this - "EPSG:28410 Proj4: +proj=tmerc +lat_0=0 +lon_0=57 +k=1 +x_0=10500000 +y_0=0 +ellps=krass +towgs84=23.92,-141.27,-80.9,0,0.35,0.82,-0.12 +units=km +no_defs" <br />then scale in view is very wrong! <br />Necessary 1:1 000 showing 1:38 264<br />Necessary 1:2 500 showing 1:95 661<br />Necessary 1:10 000 showing 1:382 644<br />Necessary 1:100 000 showing 1:3 826 440</p> Bug report #18474 (Open): Layer style effects not supported by the legendhttps://issues.qgis.org/issues/184742018-03-18T13:06:42ZBorys Jurgiel
<p>They are included neither to the Layers panel nor to the printed legend.<br />Also they cause a "Warning: Unsupported blend" debug message.</p> Bug report #17124 (Open): Editing behavior of filtered layers is inconsistenthttps://issues.qgis.org/issues/171242017-09-12T07:29:15ZGiovanni Manghigiovanni.manghi@gmail.com
<p>Seen on 2.14, 2.18 and master.</p>
<p>Add a shapefile<br />Set a filter > vector continues editable<br />Save project, close project and reopen it > layer is not editable<br />Clear filter > still not editable<br />Save project, close project and reopen it > layer editable</p> Bug report #16942 (Open): WMS/WFS layers do not show in the OWS group of the QGIS browserhttps://issues.qgis.org/issues/169422017-07-28T14:26:21ZGiovanni Manghigiovanni.manghi@gmail.com
<p>Possibly also affects WFS and WCS.</p>
<p>The connection names show, they do not expand to show layers.</p>
<p>Tested with Geoserver, Mapserver and QGIS Server.</p>
<p>I believe is a regression.</p>