Survey and geospatial
Datasets that outgrow every other route
A survey deliverable is measured in tens of gigabytes, arrives as a directory tree, and goes to a client who has no interest in installing anything.
A clearer transfer
Fast to send. Simple to receive.
Up to 300GB per transfer
Plus covers deliverables that would otherwise go on a disk in the post.
Resumable uploads
A multi-hour upload survives a dropped connection: reselect the same files and it continues.
Structure preserved
Directory trees arrive as trees, so a project opens rather than asking for missing components.
What is in a deliverable
Formats and sizes that break tooling
Point clouds are the heavy part
LAS and LAZ from LiDAR, E57 from terrestrial scanning. A single corridor survey runs to tens of gigabytes before imagery is added.
Shapefiles are not one file
A shapefile is at least three files sharing a name, and it stops working when they are separated. Send the folder and they stay together.
Rasters carry sidecars
GeoTIFF, ECW and JP2 come with world files, pyramids and metadata beside them. Those belong in the same directory, and they arrive there.
Deliverables often go to several parties at once
The client, the engineer and the planning authority may all need the same dataset. One transfer with one link avoids three copies drifting apart.
Processing outputs are bigger than the raw capture
A classified point cloud, a mesh and derived rasters together typically exceed the flight data they came from, so plan the transfer around the deliverable rather than the capture.
Why sneakernet persists
The industry still posts hard drives, and it should not have to
Couriering a disk is slow, easy to lose and impossible to audit. It survives because most transfer services fall over somewhere between ten and a hundred gigabytes.
Quick answers
Before you send
The essentials, without another wall of feature cards.
How large can one transfer be?
Free covers 5GB. Plus raises it to 300GB per transfer.
Will a shapefile still open?
Yes, provided its components travel together, which is what folder transfers are for.
Can the client download in parts?
They download over HTTPS in a browser and can pause and resume like any other download.
Can I send a dataset larger than 300GB?
Not in one transfer. Split it along a boundary that makes sense for the project, such as by tile or by phase, and send each as its own delivery.
Do you alter coordinate systems or metadata?
No. Files including projection and metadata sidecars are delivered exactly as uploaded.
Can the client download only part of it?
They download the transfer as delivered. If partial delivery matters, send tiles as separate transfers.
Try it with the next thing you have to send
Choose the files, share one link, and see what happens after it lands.
Send a datasetKeep reading
