-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invisible topology #20898
Comments
Author Name: Sandro Santilli (@strk) can't reproduce, dunno what happened.
|
Author Name: Sandro Santilli (@strk) Actually, I'm still seeing it, on both 2.8 and master.
|
Author Name: Sandro Santilli (@strk) 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.
I confirm the table does contain data as I can load it as a single table (also via DBManager) and it is then visible.
|
Author Name: Sandro Santilli (@strk) LayerProperties->General->LayerSource is as follows: For the broken (not visible) layer:
For the working (visible) layer:
|
Author Name: Sandro Santilli (@strk) And this is another working version of the same table, this time loaded via "Add PostGIS Layer" dialog:
At this point the only different thing between the working and non-working versino is the srid=0 (working) vs. srid=-1 Did anything change in that reguard, Jurgen ? |
Author Name: Sandro Santilli (@strk) Filed a ticket in PostGIS to request it being nicer with clients: https://trac.osgeo.org/postgis/ticket/3192 |
Author Name: Sandro Santilli (@strk) NOTE: master branch is also affected by this. |
Author Name: Sandro Santilli (@strk) gah, the patch shows it still fails with this "LayerSource":
|
Author Name: Sandro Santilli (@strk) Sorry, the patch DOES work, only you need to zoom to the layer after loading the topology. |
Author Name: Sandro Santilli (@strk) Now trying patching postgresql provider instead, to assume it's not just SRID=0 that "does not constraint" but also SRID=-1. |
Author Name: Sandro Santilli (@strk) 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. |
Author Name: Sandro Santilli (@strk) There's no 2.8.3 choice in the "Target version", how should make sure the fix for this enters 2.8.3 ?
|
Author Name: Sandro Santilli (@strk) Fixed in changeset "a4e629b32afcb810a0d8b52b2cce6c3f0973fa61".
|
Author Name: Sandro Santilli (@strk) So I pushed the fix (for DBManager topoviewer plugin) in both 2.8 branch (target: 2.8.3) and master branch (target: 2.11?).
|
Author Name: Sandro Santilli (@strk) It turns out the canvas is back blank after saving and re-opening the project, so this is still not fully fixed :(
|
Author Name: Nyall Dawson (@nyalldawson) Not a blocker
|
Author Name: Sandro Santilli (@strk)
Original Redmine Issue: 12802
Affected QGIS version: 2.8.3
Redmine category:db_manager
Assignee: Sandro Santilli
The topology "city_data" as created by PostGIS topology regression test cannot be showed anymore by TopoViewer plugin of DBManager.
I'm not sure it has to do with the SRID=-1 or what else, but nothing is shown in the map.
Manually loading the "edge_data" table works.
But the "edge_data" table as loaded by the DBManager TopoViewer cannot be seen.
By saving the project I can see that the DBManager created layer has an empty extent, and hitting "Update Extents" in the layer properties (general tab) does not change things.
This happens in both 2.8 and master branches.
The text was updated successfully, but these errors were encountered: