search

opengisch / qfieldsync

Sync your projects to QField
https://qfield.org/
GNU Lesser General Public License v3.0
53 stars 26 forks source link

Wrong handling of layers' groups #587

Closed spono closed 1 month ago

spono commented 2 months ago

Hi, I think there's something going wrong with the handling of layer groups. In the example picture below (screenshot from QGIS), the two layers included into the group "RASTER BASE" are used to create a basemap through the Map Theme option.

qfield_project

Once packed up and sent to the device, the layer group is retained even if the contained layers are removed (with the setting Remove from project).

Screenshot_2024-06-05-10-47-12-58_2e601d870d31f598a7096b1e53961eb8

Another weird beviour appears with the layer "schema_campionamento":

Tested on 4.6.4 and 4.9.1, on W10.

The project is a thinned version of the main one, due to other issues happening during the export (related to the creation of a basemap which includes OSM)

suricactus commented 2 months ago

Can you please upload the minimal project here, so we can confirm and identify the issue. Also, based on your writing I assume you used the cable export of QFieldSync, not QFieldCloud. If my assumption is correct, can you please confirm that opening the packaged version appear incorrect also in QGIS, or it is only a QField issue?

spono commented 2 months ago

you're right for both things: I used the cable export and opening the zipped project in QGIS appears incorrect (i.e. with an empty group named "RASTER BASE").

BTW, trying to pack up a minimal project with the same settings and -partly- data, now I get an error saying "No basemap layer selected. Check configuration"...even though basemap is set to use a style merging the two layers within the RASTER BASE group.

At this point, the idea is to do a total reinstall of QGIS but, before doing it, I ask you: shall I or you prefer to keep the system like this to find the bug?

suricactus commented 2 months ago

Please provide us a sample project, so we can confirm your issue.

Two things you can check before reinstalling: 1) create a new QGIS profile (don't delete the old "broken" one) and see if you experience the same. 2) if you are a Windows user, you can install multiple QGIS versions in parallel and see if you experience the same.

spono commented 2 months ago

OK, I'll do in the next days. In the meantime I attach here the minimal project for the second issue (no basemap)

[Uploading minimal_project_NoBasemap_Selected.zip…]()

github-actions[bot] commented 2 months ago

The QFieldSync project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.

spono commented 2 months ago

Please provide us a sample project, so we can confirm your issue.

Two things you can check before reinstalling:

1. create a new QGIS profile (don't delete the old "broken" one) and see if you experience the same.

2. if you are a Windows user, you can install multiple QGIS versions in parallel and see if you experience the same.

my experience remained the same and I'm not able to create a smaller project for testing this issue...I guess it's related to the project itself. In the meantime I opened a new issue for the other problem.

github-actions[bot] commented 1 month ago

The QFieldSync project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.