Timeline for Saving duplicate geometry layers into a geopackage?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2018 at 16:44 | vote | accept | Ruslan | ||
| Jun 7, 2018 at 16:44 | answer | added | Ruslan | timeline score: 2 | |
| Jun 5, 2018 at 11:02 | comment | added | user30184 | This has nothing to do with GeoPackage. You can save however many tables you want into GeoPackage. The trouble you have is special for QGIS and especially the "duplicate layer" feature that you are using. Change your workflow and don't duplicate your layers. And the Import vector layer method in my answer works, haven't you tried it? | |
| Jun 4, 2018 at 15:54 | comment | added | Ruslan | So is that not a bug, but a feature of gpkg then? I'm just not sure whether the issue is my misinterpretation of gpkg, or that the gpkg should work in a different way and it is a bug? | |
| Jun 4, 2018 at 8:25 | comment | added | user30184 | Duplicated layer in QGIS seems not to be self-standing copy of the data but rather a shadow of the original layer. If you edit the shadow layer and save the edits the original layer is edited by the same. Or in other words, you can't really edit the shadow but you edit the real object behind it. I suppose that the reason of having duplicated layers is to make it possible to have different renderings from the same data. But they look like normal layers in user interface which is confusing. | |
| Jun 3, 2018 at 20:10 | comment | added | Ruslan | I will re-open it once I will try the workaround and can formulate my issue a bit more concisely/precisely. Thanks. | |
| Jun 3, 2018 at 19:57 | comment | added | user30184 | I consider also that issues.qgis.org/issues/16588 is a bug and it should be reopened. When it comes to the answer to gis.stackexchange.com/questions/281201/… I do not think it is was a workaround with the context of the question but it could be used as a workaround for your problem. | |
| Jun 3, 2018 at 19:41 | answer | added | user30184 | timeline score: 1 | |
| Jun 3, 2018 at 16:59 | comment | added | Stu Smith | Yeah, I agree, I should have used the term "workaround" instead of "solution". | |
| Jun 3, 2018 at 5:49 | comment | added | Ruslan | Not sure if you can count that as a solution, seems more like a workaround a bug. Will have to test it later. | |
| Jun 3, 2018 at 5:33 | comment | added | Stu Smith | According to this post, the problem has been solved with QGIS 3: gis.stackexchange.com/questions/281201/… | |
| Jun 2, 2018 at 10:53 | comment | added | Ian Turton | the bug report doesn't say it's expected, just that it looks that way to the program. reopen the bug report and make it clearer why this is an issue | |
| Jun 1, 2018 at 21:38 | comment | added | user30184 | GeoPackage does not set such limitations. Perhaps QGIS does. With ogr2ogr it is for sure possible. | |
| Jun 1, 2018 at 21:29 | comment | added | Ruslan | yes. Names are different. Otherwise they are identical (same geometry/attributes). | |
| Jun 1, 2018 at 21:28 | comment | added | user30184 | Do your layers have different names? | |
| Jun 1, 2018 at 19:39 | history | asked | Ruslan | CC BY-SA 4.0 |