Spatial data delivery
How do you deliver GIS, point cloud, and drone data?
Point clouds, orthomosaics, DEMs, and geodatabases can be large, and they rely on coordinate notes, indexes, and sidecar files. Keep the data and metadata in one delivery folder so the receiver can place and open the result correctly.
Organize raw capture, working data, final outputs, and documentation into separate folders. Confirm the coordinate reference and units, then transfer the complete folder so Shapefile sidecars, geodatabase contents, and image pyramids stay together.
Document the delivery
- State the coordinate reference system, vertical datum, units, and coverage.
- Record the capture date, equipment, processing software, and key settings.
- Explain the naming and version of LAS, LAZ, GeoTIFF, DEM, or geodatabase outputs.
- Include gaps, control points, accuracy reports, and usage limits.
Do not send only the largest file
A Shapefile needs several matching sidecar files, a file geodatabase is a folder, and a photogrammetry project may rely on camera data, control points, and caches. Folder mode preserves those paths. A single file can be up to 200 GB, and each folder can contain up to 20,000 files.
Move field data to the office while both sides are online
When the field crew and office team are available at the same time, direct transfer removes one full upload and download cycle. Keep the original field copy, and choose original-folder saving when interruption recovery matters more than bundling many small files into one ZIP.
When is it the wrong tool?
Long-term archives, multi-user collaboration, version control, and audited deliveries belong in the storage system required by your organization. 8ma Quick Transfer handles a live handoff while both sides are online; it does not replace a data repository.