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

Manage Layers Toolbar - Add GeoPackage Layer #23012

Closed
qgib opened this issue Jun 18, 2016 · 11 comments
Closed

Manage Layers Toolbar - Add GeoPackage Layer #23012

qgib opened this issue Jun 18, 2016 · 11 comments
Labels
Feature Request Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@qgib
Copy link
Contributor

qgib commented Jun 18, 2016

Author Name: Reinhard Reiterer (Reinhard Reiterer)
Original Redmine Issue: 15069

Redmine category:browser


Pleas implement a button/dialog in the 'Manage Layers Toolbar' to add a GeoPackage layer.


@qgib
Copy link
Contributor Author

qgib commented Jun 18, 2016

Author Name: Matthias Kuhn (@m-kuhn)


What is the reasoning behind this?
You can use the "Add Vector Layer" button to add a GeoPackage layer.
For technical reasons, there is one button per provider.
Adding one button per supported GDAL/OGR source type would fill half the screen with icons.


  • resolution was changed from to wontfix
  • status_id was changed from Open to Closed

@qgib
Copy link
Contributor Author

qgib commented Jun 18, 2016

Author Name: Reinhard Reiterer (Reinhard Reiterer)


I don't understand why there is an 'Add SpatiaLite Layer' button but no 'Add GeoPackage Layer' button. It's also possible to add SpatiaLite layers in the 'Add Vector Layer' dialog. The buttons in the 'Manage Layers Toolbar' are not consistent and may confuse users. A grouped 'Add SpatiaLite Layer'/'Add GeoPackage Layer' button will not waste any space on the screen and both data providers can share the same dialog for adding a new layer.

Moreover using the 'Add Vector Layer' button, SpatiaLite/GeoPackage layers in the layers panel are named '' or if the database contains only a single layer ''. So I've to rename the layers all the time.

@qgib
Copy link
Contributor Author

qgib commented May 10, 2017

Author Name: Regis Haubourg (@haubourg)


I reopen this because will triaging feature requests it really appears as in inconsistency in UI. Geopackage can be seen either as ogr file datasource or DB connection, just as spatialite.
In DB manager, we have a geopackage entry. Other DB connection of DB manager are reused from QGIS connections.
I'd be in favor of having Geopackage in Browser and datasource toolbar too. That toolbar is overcrowded but should be replaced by the "One Button to rule them all":)

IMO we should push Geopackage as the new default format and be sure it's easily usable from everywhere. (why not add it as the default format for saving actions)


  • category_id was configured as Browser
  • status_id was changed from Closed to Open

@qgib
Copy link
Contributor Author

qgib commented May 10, 2017

Author Name: Regis Haubourg (@haubourg)


  • subject was changed from Mange Layers Toolbar - Add GeoPackage Layer to Manage Layers Toolbar - Add GeoPackage Layer

@qgib
Copy link
Contributor Author

qgib commented May 10, 2017

Author Name: Giovanni Manghi (@gioman)


Regis Haubourg wrote:

I reopen this because will triaging feature requests it really appears as in inconsistency in UI. Geopackage can be seen either as ogr file datasource or DB connection, just as spatialite.
In DB manager, we have a geopackage entry. Other DB connection of DB manager are reused from QGIS connections.
I'd be in favor of having Geopackage in Browser and datasource toolbar too. That toolbar is overcrowded but should be replaced by the "One Button to rule them all":)

IMO we should push Geopackage as the new default format and be sure it's easily usable from everywhere. (why not add it as the default format for saving actions)

Hi Regis, there is already somewhere a ticket about adding gpkg in browser and to fix all the inconsistencies around about this format. Not finding it at the moment.

@alexbruy
Copy link
Contributor

Closing as we now have everything in the Datasource Manager and Manager layers toolbar most likely will gone in next major release.

@m-kuhn
Copy link
Member

m-kuhn commented Apr 22, 2020

Closing as we now have everything in the Datasource Manager and Manager layers toolbar most likely will gone in next major release.

Did I miss something?

@alexbruy
Copy link
Contributor

Well, maybe I'm wrong, but I remember discussion about it. And now it is hidden by default.

@alexbruy alexbruy reopened this Apr 22, 2020
@m-kuhn
Copy link
Member

m-kuhn commented Apr 22, 2020

Yes, I also remember that there was a discussion about it. I was not sure about the outcome.
For me the gpkg button has no priority (I can very well live with drag and drop from file browser / QGIS browser / db manager / ds manager for this purpose), so I don't mind this issue being closed.

Does someone know where the discussion wrt dropping the toolbar was?
What are others opinions? @gioman @haubourg @elpaso @timlinux

@alexbruy alexbruy added the Feedback Waiting on the submitter for answers label Aug 12, 2020
@github-actions
Copy link

The QGIS 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.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Jul 14, 2021
@github-actions
Copy link

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

3 participants