Data export

Exports package data the platform already holds into a downloadable archive. Unlike an ingest, there is nothing to upload and no folder layout to meet — you choose a scope and a format, and the platform builds the archive.

Scope#

An export is requested against a dataset or a collection. Progress and any failures appear on the export's own page, with the step that failed and why.

Large exports are built asynchronously: the archive becomes available for download when the run finishes rather than streaming as you wait.

Point clouds#

Point-cloud tiling happens on the export path rather than at ingest. That means the tiling you get is decided when the data is requested, not when it arrived — so an export can be tiled to suit the consumer without re-ingesting anything.

Coordinate reference system#

Exported geometry is in the dataset's own coordinate reference system. See Coordinates for how a dataset's 2D and 3D SRIDs are used.