The Open Geospatial Consortium (OGC) defines GeoPackage (*.gpkg) an open, non-proprietary, platform- independent, standards-based data format for geographic information systems (GIS). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy-to-distribute and ready-to-use file. GeoPackage is natively supported by numerous software applications.
GeoPackage offer users the following benefits:
The single file is easy to transfer and offers a rich end-user experience.
Attribute names are not limited in length, making the format user friendly.
The file size limit is large at 140 TB.
A file size limit could be imposed by the file system to which the file is written.
It supports raster, vector, and database formats, making it a highly versatile solution.
It is an OGC standard.
In most cases, it is a plug-and-play format.
For information on how to open, use and understand a GeoPackage dataset, please refer to our Getting Started with GeoPackage guide. For further information on GeoPackage, please see the GeoPackage website.
OS Open Rivers is supplied as a national GeoPackage file.
The naming of attributes between GeoPackage and GML is very similar as both formats do not limit the number of characters for an attribute name. The following tables map the GML attribute name to its GeoPackage equivalent for the WatercourseLink and HydroNode features.
GML includes attributes which describes the geometry of the features; this is not applicable to GeoPackage files as they are separated by their geometry. The use of an asterisk symbol (*) in the following tables indicates that a particular attribute is not mapped in that format, for example, centrelineGeometry has no GeoPackage equivalent.
In April 2023 there were significant changes to the naming patterns in the GeoPackage format. These are outlined in GeoPackage format changes.
GML attribute | Esri shapefile attribute |
---|---|
GML attribute | GeoPackage attribute |
---|---|
In April 2023 there were significant changes to the naming patterns in the GeoPackage format. The formatting of most names changed from title case to snake case. The following tables map the previous names to those use after April 2023.
GeoPackage attribute name prior to April 2023 | GeoPackage attribute name after April 2023 |
---|---|
GeoPackage layer name prior to April 2023 | GeoPackage layer name after April 2023 |
---|---|
GeoPackage column name prior to April 2023 | GeoPackage column name after April 2023 |
---|---|
GeoPackage constraint name prior to April 2023 | GeoPackage constraint name after April 2023 |
---|---|
gml:identifier
id
hydroNodeCategory
hydro_node_category
geometry
*
gml:identifier
id
flowDirection
flow_direction
length
length
fictitious
fictitious
form
form
watercourseName
watercourse_name
watercourseNameAlternative
watercourse_name_alternative
startNode
start_node
endNode
end_node
centrelineGeometry
*
id
id
flowDirection
flow_direction
length
length
fictitious
fictitious
form
form
watercourseName
watercourse_name
watercourseNameAlternative
watercourse_name_alternative
startNode
start_node
endNode
end_node
hydroNodeCategory
hydro_node_category
HydroNode
hydro_node
WatercourseLink
watercourse_link
geom
geometry
HydroNode_pkey
hydro_node_pkey
WatercourseLink_pkey
watercourse_link_pkey