CargoGauge
This page describes how a Customer exports its data from CargoGauge, under the switching section of the Terms of Service and Article 26 of the EU Data Act.
Requesting an export
The Customer's administrative contact asks for an export by writing to support@cargogauge.com. Our staff put the export together and send it to the Customer as files over an encrypted connection.
Formats
- The data is in JSON (RFC 8259), encoded as UTF-8.
- Each file is a JSON object with a section for each kind of record, such as the company, its users, drivers, vehicles, trips and stops. A section is a list of records, and each record holds the fields the platform stores for it, under the names the platform uses.
- Records refer to each other by identifier (UUID).
- Times are in ISO 8601 with their offset from UTC. Positions are in WGS 84: as latitude and longitude in decimal degrees, or, for a geometry, as hex-encoded Extended Well-Known Binary (EWKB).
- Photographs and document scans are provided as files in the format they are stored in (WebP for images, PDF for documents), each named by the key its record refers to.
Known limits
- An export comes as several files, because some kinds of record, such as the stops of trips, are put in files of their own.
- Passwords and API keys are stored only as hashes, and the hashes are not exported.
- Data deleted at the end of its retention period (Annex 1 of the Data Processing Agreement) can no longer be exported.