GeoPackage — Features Stored in Web Mercator (EPSG:3857)
The same five towns stored as projected metres rather than degrees, with EPSG:3857 registered in gpkg_spatial_ref_sys and stamped into every geometry blob's header. Unlike GeoJSON, GeoPackage genuinely supports this — so it is the clean way to test that your reader honours the declared SRS instead of assuming 4326.
| code | name | x (metres) | y (metres) |
|---|---|---|---|
| KB | Kestrel Bay | -1389489.884 | 5952526.765 |
| MR | Marram | -1379415.47 | 5960374.522 |
| HW | Holloway | -1397170.929 | 5945012.626 |
| NP | Ninepin | -1384836.729 | 5937586.527 |
| QC | Quillan Cross | -1404128.397 | 5956531.508 |
Specifications
- Format
- OGC GeoPackage 1.3 (SQLite)
- Feature Tables
- 1
- Features
- 5
- Srs Id
- 3857
- Units
- metre
- Srs Rows
- 4326, 3857, 0 and -1 (the two required undefined entries)
- Geometry Encoding
- GeoPackage binary header with srs_id 3857 + OGC WKB
- Last Change
- 2026-01-01T00:00:00.000Z (fixed for reproducibility)
Testing contract
Expected to pass- Scenario
- Load the layer and overlay it on the EPSG:4326 GeoPackage from this family.
- Expected result
- The towns land on top of each other once the declared SRS is honoured; a reader that assumes degrees plots them roughly 1.39 million units off the map.
What is a .gpkg file?
GeoPackage is an OGC standard that stores vector features, raster tiles, and their metadata inside a single SQLite database. Required tables such as gpkg_contents, gpkg_spatial_ref_sys, and gpkg_geometry_columns describe what the file holds, and feature geometries are stored in a standard binary header followed by Well-Known Binary. Being one self-contained file with real SQL indexing, it is the modern replacement for the multi-file shapefile.
How to use this file
Use an example .gpkg file to test GIS readers, SQLite-based spatial tooling, and shapefile-to-GeoPackage converters, checking the required metadata tables, the geometry header's SRS id and envelope flags, and attribute round-tripping.
How to use this file for testing
“GeoPackage — Features Stored in Web Mercator (EPSG:3857)” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, Metadata testing. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks — for testing map tools, route parsers, and geo importers.
Documented properties for this file: OGC GeoPackage 1.3 (SQLite). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.
Related files
- geojsonGeoJSON — Legacy 2008 `crs` Member (removed in RFC 7946)A FeatureCollection carrying the `crs` member from the 2008 GeoJSON specification. RFC 7946 removed it and fixed the CRS as WGS 84, so a modern reader should treat this as an ignorable foreign member — but plenty of exporters still write it and some readers still obey it.
- kmlKestrel Bay Territory — KML TwinThe same 14 features as KML Placemarks, with the multi-point buoys expressed as a MultiGeometry and the two holed polygons using innerBoundaryIs. KML orders coordinates longitude-first like GeoJSON, which makes it the least surprising twin in this group.
- kmlKML — ExtendedData Untyped Data ElementsAttributes carried in `ExtendedData/Data` elements, which have names and display names but no declared types — every value is a string. Importers must infer that population is a number, and this is where a silently wrong inference starts.
- kmlKML — extrude With Three Different altitudeMode ValuesFour extruded points whose third coordinate means three different things depending on the `altitudeMode` beside it: ignored when clamped, height above terrain when relative, height above the ellipsoid when absolute. Copying the number without the mode changes what the data says.
- kmlKML — Nested Folders (three levels)Eight Placemarks arranged in three levels of Folder, the hierarchy KML uses for layer trees. GeoJSON has nothing equivalent, so a converter must either flatten and record the path or lose the structure entirely — and this file makes which one it did obvious.
- kmlKML — Shared Styles and a normal/highlight StyleMapShared `Style` blocks referenced by `styleUrl`, plus a `StyleMap` pairing normal and highlight states. KML colours are written aabbggrr rather than the usual rrggbbaa, which is why converted maps so often come out with red and blue swapped.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.