{"id":6914,"date":"2018-11-09T06:34:01","date_gmt":"2018-11-09T05:34:01","guid":{"rendered":"http:\/\/www.sigterritoires.fr\/?p=6914"},"modified":"2023-06-22T10:03:17","modified_gmt":"2023-06-22T08:03:17","slug":"geopackage-format-and-qgis-3","status":"publish","type":"post","link":"https:\/\/www.sigterritoires.fr\/index.php\/en\/geopackage-format-and-qgis-3\/","title":{"rendered":"Geopackage format and QGis 3"},"content":{"rendered":"\n

An<\/strong> open<\/strong> format<\/strong> for geospatial<\/strong> information<\/strong><\/h2>\n\n\n\n
GeoPackage<\/a> is a compact, portable, self-descriptive and open,\nstandards-based, platform independent and allowing geospatial information transfer\nformat. <\/p>\n\n\n\n
The GeoPackage standard is composed of a set of conventions to store in\na SQLite database the following items: <\/p>\n\n\n\n
\n
vector entities <\/li>\n\n\n\n
matrixes from images and rasters tiles with different scales <\/li>\n\n\n\n
attributes (non-spatial data) <\/li>\n\n\n\n
extensions <\/li>\n<\/ul>\n\n\n\n
To put it clearly, a GeoPackage is the SQLite container and the encodingstandard, GeoPackage governs the rules and requirements of the content stored in a GeoPackage container. The GeoPackage standard defines the diagram of a GeoPackage including table definitions, assertions of integrity, format limitations and content constraints. Thecontent required and taken in charge of a GeoPackage is entirely defined in thestandard. These features are reframed on a common basis and the extension mechanism provides to the developers a way to include additional features in their GeoPackages. <\/p>\n\n\n\n\n\n\n\n
Since GeoPackage is a database container, it takes in charge its direct\nuse by different GIS software. This means that the GeoPackage data can be\nconsulted and updated in a \u201cnative\u201d storage format without intermediate format conversion.\nThe GeoPackages complies with the requirements of the standard without having\nto implement specific extensions from the seller are interoperable in all\nenvironments IT corporate and personal. The GeoPackages are particularly useful\nfor mobile devices such as mobile phones and tablets in the communication\nenvironments where connectivity and bandwidth are limited . <\/p>\n\n\n\n

Geopackage in QGis<\/strong><\/h2>\n\n\n\n
If you are, already, using data bases Spatialite in QGis you will wonder\nwhat novelty does Geopackage bring: basically the ability to store rasters in a\nSQLite database. <\/p>\n\n\n\n
If, on the other hand, you are used to work with shapefiles (SHP), we\nhave already published several articles that explain the benefits of working\nwith SQLite <\/p>\n\n\n\n
\n
Database Tutorial<\/a> SpatiaLite under QGis 2.8 Wien<\/a> <\/li>\n\n\n\n
Queries and views<\/a> of\n a SpatiaLite base<\/a> in QGis 2.8<\/a> <\/li>\n\n\n\n
SpatiaLite database table management database with\nQGis 2.8<\/li>\n\n\n\n
Import tables into<\/a> a <\/a> SpatiaLite database with QGis 2.8<\/a> <\/li>\n\n\n\n
Create<\/a> a <\/a> SpatiaLite database with QGis 2.8<\/a> <\/li>\n\n\n\n
Python Recipes to access<\/a> Postgis vector and Spatialite<\/a>\ndata <\/li>\n<\/ul>\n\n\n\n
The Geopackage format behaves exactly as Spatialite and QGis by giving you\nnew possibilities . <\/p>\n\n\n\n
Therefore, if you change from shapefiles to SQLite, opt for Geopackage rather\nthan Spatialite.<\/p>\n\n\n\n
<\/p>\n\n\n\n
How to<\/strong> create<\/strong> a<\/strong> Geopackage<\/strong> with QGis 3.4<\/strong><\/h2>\n\n\n\n
GeoPackage is a standard OGC data package that can store different types\nof spatial data types such as points, polylines and polygons. We can save\nseveral layers in just one GeoPackage ( .gpkg ) file. It is an excellent way to\nstore and organize your spatial data with QGIS. When you save your spatial files\nto GeoPackage format you can easily find them without having to browse and to\ndig in all your records. <\/p>\n\n\n\n
Using Geopackage to store our spatial data has many advantages. Our data\nwill be placed in a centralized location. By using this method we can reduce\nthe cluttering that occurs when we are dealing with hundreds of files. It is\neasier to transfer huge amounts of layers in a single geopackage . <\/p>\n\n\n\n
To create a g\u00e9opackage layer in QGIS it will do just to: \n\n1-Open QGIS
\n2-Go to Layer | Create a layer | New geopackage layer \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n3-\nType the name of the new GeoPackage layer, give a name to the table and\npossibly select a geometry in the list.   \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
If you expect to import existing layers in your Geopackage, you can\nclick OK. Your Geopackage will be created and empty, well, almost. You will have\nthis empty table but with the possibility of erasing it at any time. <\/p>\n\n\n\n
If, on the other hand, you want to start creating a true working layer,\nyou will use the block \u201cNew field\u201d from the window to define your table columns.\n\n\nYour Geopackage file is created. In order to use\nit in QGis you must connect to this new database: \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThe\nnew database appears in the explorer as follows: \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
<\/p>\n\n\n\n
How to<\/strong> fill<\/strong> a<\/strong> Geopackage database<\/strong><\/h2>\n\n\n\n
You have three methods for adding layers to a Geopackage file: <\/p>\n\n\n\n
Creation<\/strong> from<\/strong> scratch<\/strong>\n\nYou will add an empty table by defining the\nfields (columns) manually. You will repeat the steps described above when\ncreating the Geopackage (Layer menu> Create a layer -> New Geopackage layer).\nOnce the creation window opens, use the … button to point the geopackage file\nwhere you want to create a new layer: \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nFill\nin the necessary fields (table name, geometry , … ) as well as the definition\nof your columns . When you click OK you will get the following message:   \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nClick\nAdd a new layer, this layer will then added to the list of layers of your\ngeopackage file. \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n

<\/p>\n\n\n\n

Saving<\/strong> from<\/strong> an existing<\/strong> layer<\/strong><\/h2>\n\n\n\n
You can export to a geopackage file an alreadyexisting layer. You will select your layer in the panel \u201cLayers<\/strong>\u201d andExport ->SaveAs …entities<\/strong><\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nIn\nthe opening window, in the formats list, select Geopackage<\/strong><\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nIn\nFile Name, click the … button and point to your Geopackage file.   \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
Fill in the necessary fields and click OK.<\/strong> The layer is imported to\nyour Geopackage . <\/p>\n\n\n\n
Importing<\/strong> an<\/strong> existing<\/strong> layer<\/strong> with DB Manager<\/strong> <\/p>\n\n\n\n
The DB Manager allows you to totally manage your data and databases. \n\nTo open Database<\/strong>-> DB Manager<\/strong><\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
In the DB Manager window, to import an existing layer in your geopackage\nfile, <\/p>\n\n\n\n
\n
click in the panel Data<\/strong> providers<\/strong> on your Geopackage file<\/li>\n\n\n\n
click on the Layer<\/strong> \/<\/strong> file<\/strong> import<\/strong> tool<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nfill in the\nfields for Import<\/strong>a<\/strong>layer<\/strong>vector<\/strong> window \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
Important<\/strong>! Check the SRC<\/a> source and SCR target boxes and verify\nthat the CBC corresponds to what you wish . Check the Create a spatial index\nbox if you in want one. If you fail to add this information in this step , it\nwill be very , very complicated to catch up … <\/p>\n","protected":false},"excerpt":{"rendered":"
An open format for geospatial information GeoPackage is a compact, portable, self-descriptive and open, standards-based, platform independent and allowing geospatial information transfer format. The GeoPackage standard is composed of a set of conventions to store in…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1260],"tags":[],"class_list":["post-6914","post","type-post","status-publish","format-standard","hentry","category-non-classe-en"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-1Nw","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/6914","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=6914"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/6914\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=6914"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=6914"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=6914"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}