Upload a GeoPackage

A GeoPackage (.gpkg) is the quickest way into Waystones Cloud. Drop it on Projects → New project and Waystones builds a data model from it in your browser — nothing is uploaded until you confirm.

What gets detected

For every feature table in the file, Waystones reads:

From the GeoPackage	Becomes
Table name	Collection id (e.g. roads) and a readable title ("Roads")
Columns and their types	Fields — text, integer, number, boolean, date, date-time
NOT NULL columns	Required fields
Geometry column and type	Point, line or polygon (single or multi)
Primary key	Feature id
Coordinate system (srs_id)	The data's native CRS — EPSG:4326 if none is declared
Extent in gpkg_contents	The dataset's bounding box

Then you get to describe the service before uploading.

Preparing a good file

• One table per layer. Each feature table becomes its own collection.
• Give every table a primary key. An INTEGER PRIMARY KEY (QGIS names it fid) gives each feature a stable id.
• Declare a coordinate system. Files without one are treated as WGS 84 (EPSG:4326). Any EPSG code works; the API also serves CRS84.
• Use plain column names. Names are normalised to lowercase with underscores, so Road Name becomes road_name.
• Feature tables only. Raster tiles inside a GeoPackage are not supported yet.

Converting other formats

Shapefile, GeoJSON, FlatGeobuf, KML and others: open them in QGIS and use Export → Save Features As… → GeoPackage, or install the QGIS plugin, which bundles any vector layers into a GeoPackage for you. With GDAL:

ogr2ogr -f GPKG data.gpkg input.shp

Size and storage

Uploads count towards your plan's storage (2 GB on the free plan). After upload, Waystones converts the data to GeoParquet and FlatGeobuf for serving; that conversion counts as one processing job.

Updating the data

To publish a new version, use Replace on the project page or waystones-cloud replace <project-id> updated.gpkg. Your URL, slug and settings stay the same.