Guides / Get your data ready
Get your data ready
Step 2 of 4 · what to export, and how to keep uploads small and quick.
What becomes what
Coordinate systems
Export in your projected grid (a UTM zone, a South African Lo system or another national grid), not "arbitrary" or local coordinates. The coordinate system travels inside GeoTIFF and LAS/LAZ files, or in the .prj next to a shapefile or world file. If a file has none, the console asks you to pick one before the upload starts.
The check before upload
When you drop a file into a delivery, it is read on your own computer before a single byte is uploaded. The header, the coordinate system and the extent are read, a preview is drawn on a map, and what we found is shown in plain words: where the data sits, how big the upload is and roughly how long it will take. Nothing is sent until you press the button.
It catches the things that otherwise come to light after an hour of uploading, or on the client's screen:
- No coordinate system, or one we can't read: you choose it from a list, and your choice is applied when the file is converted.
- The wrong hemisphere or zone: a southern site exported in a northern UTM zone, or the other way round, lands thousands of kilometres away. The preview shows it, the check says it.
- Data at 0°, 0° or off the planet, an image that is blank, a point cloud with no points, an export in latitude / longitude instead of your grid.
- Missing companions: a shapefile without its .prj, .shx or .dbf; a plain TIFF without its world file.
- Things that will look wrong: no transparency on the edge of an orthomosaic, an empty transparency band, no "nodata" value on an elevation model, a JPEG with an alpha channel.
- Size: a file over your plan's limit, or too big to prepare for the online view automatically, is said so up front (it is still offered to your client as a download).
You can still upload a file the check is unsure about; the notes travel with it, so if the conversion then fails we already know why. As far as we know, no other delivery service checks files before they are uploaded.
Smaller uploads, faster conversion
- Point clouds as LAZ, not LAS: typically 5 to 10 times smaller, nothing lost.
- One merged file per orthomosaic and per point cloud, not a folder of tiles.
- Compressed GeoTIFF for the aerial image: JPEG at about 90 quality is much smaller than LZW or none, with no visible difference on screen. Use BigTIFF if it's over 4 GB.
- Native resolution: exporting finer than the real ground resolution only makes the file bigger.
- Don't make web tiles first (MBTiles, Google tiles, Cesium, Potree): upload the originals and we make the web versions.
Step by step for your software
DJI Terra
L1, L2, L3 LiDAR and mapping.
Pix4D
Pix4Dmapper and PIX4Dmatic.
Agisoft Metashape
Orthomosaic, DEM and point cloud exports.
WebODM / ODM
Options and assets to download.
Global Mapper, QGIS, ArcGIS, Trimble Business Center, TerraSolid, LP360 and CloudCompare all export these same formats.
Size limits
The largest single file depends on your plan (see pricing). Uploads resume if your connection drops. For very large jobs, contact us for a quote.