https://issues.qgis.org/https://issues.qgis.org/favicon.ico2015-06-23T07:18:17ZQGIS Issue TrackingQGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=626372015-06-23T07:18:17ZSandro Santillistrk@kbt.io
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>invalid</i></li></ul><p>can't reproduce, dunno what happened.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=626652015-06-25T05:36:17ZSandro Santillistrk@kbt.io
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li><li><strong>Resolution</strong> deleted (<del><i>invalid</i></del>)</li></ul><p>Actually, I'm still seeing it, on both 2.8 and master.<br />Pretty easy to reproduce. Just load POSTGIS_SOURCE_TREE/topology/test/load_topology.sql into a topology-enabled database and try to see it. Nothing is shown. Puzzling :/</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627312015-07-01T23:16:32ZSandro Santillistrk@kbt.io
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Severe/Regression</i></li></ul><p>Sorry but I'd call this a blocker. I hadn't tested 2.8.0 or 2.8.1 or 2.8.2 yet, but 2.8 branch has an unusable topoviewer.<br />I'm sure the plugin being used is the one from the build dir, as it's written in the console (debug build):</p>
<pre>
src/core/qgsmaplayer.cpp: 1084: (loadNamedStyle) [0ms] uri = /usr/src/qgis/build/2.8/output/python/plugins/db_manager/db_plugins/postgis/plugins/qgis_topoview/templates/next_right.qml myURI = dbname='postgis_reg' port=5493 sslmode=disable key='edge_id' srid=-1 type=LINESTRING table="city_data"."edge_data" (geom) sql=
</pre>
<p>I confirm the table does contain data as I can load it as a single table (also via DBManager) and it is then visible.<br />Only it it not visible when loaded by the topoviewer. I tried changing the style after load but it still doesn't get visible.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627322015-07-01T23:19:06ZSandro Santillistrk@kbt.io
<ul></ul><p>LayerProperties->General->LayerSource is as follows:</p>
<p>For the broken (not visible) layer:<br /><pre>
dbname='postgis_reg' port=5493 sslmode=disable key='edge_id' srid=-1 type=LINESTRING table="city_data"."edge_data" (geom) sql=
</pre></p>
<p>For the working (visible) layer:<br /><pre>
dbname='postgis_reg' port=5493 sslmode=disable key='edge_id' table="city_data"."edge_data" (geom) sql=
</pre></p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627332015-07-01T23:22:41ZSandro Santillistrk@kbt.io
<ul></ul><p>And this is another working version of the same table, this time loaded via "Add PostGIS Layer" dialog:</p>
<pre>
dbname='postgis_reg' port=5493 sslmode=disable key='edge_id' srid=0 type=LINESTRING table="city_data"."edge_data" (geom) sql=
</pre>
<p>At this point the only different thing between the working and non-working versino is the srid=0 (working) vs. srid=-1 <br />(not working)</p>
<p>Did anything change in that reguard, Jurgen ?</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627342015-07-01T23:27:41ZSandro Santillistrk@kbt.io
<ul></ul><p>Filed a ticket in PostGIS to request it being nicer with clients: <a class="external" href="https://trac.osgeo.org/postgis/ticket/3192">https://trac.osgeo.org/postgis/ticket/3192</a><br />But it's still nice for QGIS to cleanly handle this.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627352015-07-01T23:32:44ZSandro Santillistrk@kbt.io
<ul></ul><p>NOTE: master branch is also affected by this.<br />I'm testing a fix that only changes the DBManager plugin, reinterpreting SRID=-1 to SRID=0 but I would like it even better not to need this. Can I just omit the SRID and rely on the provider to figure it out for each table (would be easy by looking in geometry_columns)</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627362015-07-01T23:33:50ZSandro Santillistrk@kbt.io
<ul></ul><p>gah, the patch shows it still fails with this "LayerSource":<br /><pre>
dbname='postgis_reg' port=5493 sslmode=disable key='edge_id' srid=0 type=LINESTRING table="city_data"."edge_data" (geom) sql=
</pre></p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627372015-07-01T23:34:31ZSandro Santillistrk@kbt.io
<ul></ul><p>Sorry, the patch DOES work, only you need to zoom to the layer after loading the topology.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627382015-07-01T23:40:52ZSandro Santillistrk@kbt.io
<ul></ul><p>Now trying patching postgresql provider instead, to assume it's not just SRID=0 that "does not constraint" but also SRID=-1.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627392015-07-01T23:51:29ZSandro Santillistrk@kbt.io
<ul></ul><p>The provider patch didn't work, so for safety I'll just touch the dbmanager plugin, taking any SRID<=0 in topology.topology as if it was SRID=0. The topology support in postgis was only official starting with 2.0.0 so by that time SRID=0 is the official unknown value.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627402015-07-01T23:57:07ZSandro Santillistrk@kbt.io
<ul><li><strong>Assignee</strong> set to <i>Sandro Santilli</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>80</i></li></ul><p>There's no 2.8.3 choice in the "Target version", how should make sure the fix for this enters 2.8.3 ?</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627422015-07-02T00:01:13ZSandro Santillistrk@kbt.io
<ul><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li></ul><p>Fixed in changeset <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/a4e629b32afcb810a0d8b52b2cce6c3f0973fa61" title="DBManager topoviewer: don't be fooled by srid=-1 in topology.topology Fixes #12802">a4e629b32afcb810a0d8b52b2cce6c3f0973fa61</a>.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=627432015-07-02T00:05:55ZSandro Santillistrk@kbt.io
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li></ul><p>So I pushed the fix (for DBManager topoviewer plugin) in both 2.8 branch (target: 2.8.3) and master branch (target: 2.11?).<br />But other than writing this note I see it would not be easy to tell which version got the fix from just reading this ticket.<br />I think we should improve this.</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=632922015-08-20T01:24:16ZSandro Santillistrk@kbt.io
<ul><li><strong>Affected QGIS version</strong> changed from <i>2.8.2</i> to <i>2.8.3</i></li></ul><p>It turns out the canvas is back blank after saving and re-opening the project, so this is still not fully fixed :(</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=647782015-10-21T16:21:02ZNyall Dawson
<ul><li><strong>Priority</strong> changed from <i>Severe/Regression</i> to <i>High</i></li></ul><p>Not a blocker</p> QGIS Application - Bug report #12802: invisible topologyhttps://issues.qgis.org/issues/12802?journal_id=673582016-01-19T00:28:42ZSandro Santillistrk@kbt.io
<ul><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>fixed/implemented</i></li></ul><p>I cannot reproduce with current master (b2a12735c5e75d28f452545591374b16a62f937c)</p>