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

DB-Manager: incorrect srs_id in table gpkg_contents when creating new GeoPackage spatial table #24087

Closed
qgib opened this issue Feb 10, 2017 · 6 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! DB Manager Relating to the DB Manager core plugin

Comments

@qgib
Copy link
Contributor

qgib commented Feb 10, 2017

Author Name: Jérôme Guélat (Jérôme Guélat)
Original Redmine Issue: 16177
Affected QGIS version: 2.18.14
Redmine category:db_manager
Assignee: Even Rouault


When creating a new spatial table inside a GeoPackage with DB-Manager, the srs_id is incorrect in the gpkg_contents table...

  1. In DB-Manager, create a connection to an existing GeoPackage
  2. Table -> Create table
  3. Give a name, add some fields and check "Create geometry column", use a valid EPSG value as SRID, click "Create"
  4. SQL command "SELECT * from gpkg_contents"
  5. The field srs_id has a value of 0 (undefined) instead of the SRID I specified
@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Nov 9, 2017

Author Name: Even Rouault (@rouault)


Works on latest 2.18, provided you specify a valid EPSG code


  • resolution was changed from to worksforme
  • description was changed from When creating a new spatial table inside a GeoPackage with DB-Manager, the srs_id is incorrect in the gpkg_contents table...
  1. In DB-Manager, create a connection to an existing GeoPackage

  2. Table -> Create table

  3. Give a name, add some fields and check "Create geometry column", use a valid EPSG value as SRID, click "Create"

  4. SQL command "SELECT * from gpkg_contents"

  5. The field srs_id has a value of 0 (undefined) instead of the SRID I specified
    to When creating a new spatial table inside a GeoPackage with DB-Manager, the srs_id is incorrect in the gpkg_contents table...

  6. In DB-Manager, create a connection to an existing GeoPackage

  7. Table -> Create table

  8. Give a name, add some fields and check "Create geometry column", use a valid EPSG value as SRID, click "Create"

  9. SQL command "SELECT * from gpkg_contents"

  10. The field srs_id has a value of 0 (undefined) instead of the SRID I specified

@qgib
Copy link
Contributor Author

qgib commented Nov 9, 2017

Author Name: Even Rouault (@rouault)


  • status_id was changed from Open to Closed

@qgib
Copy link
Contributor Author

qgib commented Nov 13, 2017

Author Name: Jérôme Guélat (Jérôme Guélat)


Thanks for having a look at it... I tried with QGIS 2.18.14 and I unfortunately still get the same behaviour when using valid EPSG codes like 2056 or 21781. This doesn't happen if I create the GeoPackage in the main interface using Layer menu -> Create Layer -> New GeoPackage Layer.

QGIS 2.18.14 installed using OSGeo4W
GDAL 2.2.2


  • status_id was changed from Closed to Reopened

@qgib
Copy link
Contributor Author

qgib commented Nov 13, 2017

Author Name: Giovanni Manghi (@gioman)


  • version was changed from 2.18.3 to 2.18.14
  • resolution was changed from worksforme to

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2019

Author Name: Giovanni Manghi (@gioman)


End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.


  • resolution was changed from to end of life
  • status_id was changed from Reopened to Closed

@qgib qgib closed this as completed Mar 9, 2019
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! DB Manager Relating to the DB Manager core plugin 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! DB Manager Relating to the DB Manager core plugin
Projects
None yet
Development

No branches or pull requests

1 participant