OGC GeoPackage implementation - 3.3 #317
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://tracker.deegree.org/deegree-services/ticket/613
"The GeoPackage specification describes an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. It is a set of conventions for SQLite to store interoperable Features and/or Tiles on a common base" (opengis/geopackage GitHub repository).
In order to access a Geopackage file, you need to create a JDBC connection which points to the Geopackage file.
User and Password can just to be set to "null", given that GeoPackage is based on SQLite.
For the feature part, the user needs to configure in Deegree:
an SQL feature store;
a WFS service;
a Feature Layer.
For the tile part, the user needs to configure:
a WMTS service;
a Gpkg Tile Store;
a Tile Layer.
Configuration of a Gpkg Tile Store (example):