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

Allow to create an empty GeoPackage from the context menu of the top-level GeoPackage node (fix #25116) (Request in QGIS) #9150

Closed
qgis-bot opened this issue Jun 26, 2024 · 0 comments · Fixed by #9316
Labels
3.40 Managing Layer/Data Creating and loading layers as well as formats handling or specifics
Milestone

Comments

@qgis-bot
Copy link
Collaborator

Request for documentation

From pull request qgis/QGIS#57876
Author: @alexbruy
QGIS version: 3.40

Allow to create an empty GeoPackage from the context menu of the top-level GeoPackage node (fix #25116)

PR Description:

Description

There an inconsistency in behavior of the "Create Database" context menu item for SpatiaLite and GeoPackage nodes in the Browser. In case of SpatiaLite this action creates an empty database and adds a new connection while the same action for GeoPackage creates a new GeoPackage file with a layer and adds a new connection.

This is not only confusing but also not very convinient in some use cases when user needs an empty GeoPackage. Of course, it is possible to create an empty GeoPackage from the context menu of the directory nodes, but this again is not very intuitive and many users are not aware about this option.

This PR renames existing "Create Database" action to "Create Database and Layer" action and adds a new context menu action "Create Database" which creates an empty GeoPackage.

image

Fixes #25116.

Commits tagged with [need-docs] or [FEATURE]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.40 Managing Layer/Data Creating and loading layers as well as formats handling or specifics
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants