Skip to content
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

Objects queried by QuickOSM are not automatically saved in project file and lost when re-starting QGIS (3) #26868

Closed
qgib opened this issue May 27, 2018 · 6 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Vectors Related to general vector layer handling (not specific data formats)

Comments

@qgib
Copy link
Contributor

qgib commented May 27, 2018

Author Name: Sebastian Ernst (@s-m-e)
Original Redmine Issue: 19038
Affected QGIS version: 3.0.1
Redmine category:vectors


Reproducible in the following environments

  • QGIS 3.0.1 on openSUSE Leap 15 + QuickOSM 1.6.1
  • QGIS 3.0.3 on Linux Mint 18.3 + QuickOSM 1.6.1
  1. Steps to reproduce
  • Start QGIS 3
  • Menu: Project > New
  • Menu: Web > QuickMapServices > OSM > OSM Standart [optional step for OSM background tiles]
  • Menu: Vector > Quick OSM > QickOSM
  • Set query parameters to: {key: leisure, value: park, in: Leipzig}
  • Run query ...
  • Result so far: 3 new layers (with 599, 98 and 128 objects)
  • Menu: Project > Save as ... "test.qgs"
  • Menu: Project > Quit QGIS
  • At this point, QGIS will ask: "Save current project?" I chose "Save".
  • Start QGIS again
  • Open "test.qgs" - all three new layers exist, but they contain ZERO objects
  1. Workaround?

After saving the project and before closing QGIS, save every new layer as a geo package. This way, I at least do not loose the polygons although the layers created by QuickOSM will be empty after re-starting QGIS.

  1. Question

Is is a bug in QuickOSM or QGIS or both? Or is this some sort of new intended behavior in QGIS 3?

For reference, I also filed an issue against QuickOSM: 3liz/QuickOSM#115

@qgib
Copy link
Contributor Author

qgib commented May 28, 2018

Author Name: Etienne Trimaille (@Gustry)


This issue tracker is related to QGIS software, not for plugin. This issue can closed.

@qgib
Copy link
Contributor Author

qgib commented May 28, 2018

Author Name: Sebastian Ernst (@s-m-e)


Etienne Trimaille wrote:

This issue tracker is related to QGIS software, not for plugin. This issue can closed.

I understand that. Given the above description, I do not know who is at fault. Is it QGIS or is it the plugin? The plugin fetches the objects - only. QGIS fails to save them to disk.

@qgib
Copy link
Contributor Author

qgib commented May 28, 2018

Author Name: Etienne Trimaille (@Gustry)


The plugin creates memory layer. QGIS is not able to save memory layer. I agree QGIS should have a warning when we save this kind of layers.

@qgib
Copy link
Contributor Author

qgib commented Jun 4, 2018

Author Name: Alessandro Pasotti (@elpaso)


Lowering priority for now, I think it should be closed in favor of opening an issue against the plugin.


  • priority_id was changed from Normal to Low

@qgib
Copy link
Contributor Author

qgib commented Jul 24, 2018

Author Name: Etienne Trimaille (@Gustry)


It's not QuickOSM fault. It's stated in the UI, in the advanced panel, when you execute the query: "save to temporary files".
It's exactly the same behavior with QGIS Processing creating temporary layers.

QGIS should display a warning when we save a QGS project and:

  • layers are stored in the temporary folder (/tmp etc)
  • layers are in memory (source: Point?crs=EPSG:4326&field=full_id:.....&uid={2e18cdf3-f07b-42be-9911-e5d01584da57} )

@qgib
Copy link
Contributor Author

qgib commented Aug 4, 2018

Author Name: Nyall Dawson (@nyalldawson)


Fixed in master and 3.2.2


  • resolution was changed from to fixed/implemented
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Aug 4, 2018
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Vectors Related to general vector layer handling (not specific data formats) Crash/Data Corruption labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Vectors Related to general vector layer handling (not specific data formats)
Projects
None yet
Development

No branches or pull requests

1 participant