Troubleshooting
A download won't start, or looks smaller than expected
Raw 3D datasets are capped by design. An over-cap point cloud comes back thinned to fit, or — where it cannot be brought under the cap — not at all.
What's happening
A download stalls, or a raw 3D archive is smaller than you expected. Raw 3D datasets — the OBJ mesh and the LAZ point cloud — are capped in size. An over-cap point cloud is thinned to fit and labelled with its point spacing, and where it cannot be brought under the cap no raw point cloud is delivered at all. Either way it is a limit, not a truncated file.
What to check
- Check whether the file you want is a raw 3D file on a very large site.
- Read the point spacing recorded on the delivered cloud — a thinned cloud is named for its spacing.
- If no point-cloud download is listed at all, it could not be brought under the cap — nothing was lost in transfer.
- Retry the download once — links are generated fresh each time.
How to fix it
- Expect a thinned cloud on a very large site. It is the file that was produced; there is no larger copy to fetch.
- Where there is no cloud at all, retrying will not produce one — that is the cap, not a failed link.
- For everything else, retry. A fresh link is issued on each request.
Avoiding it next time
Nothing on your side. The cap exists because a browser download is a poor way to move a dataset of that size, not because anything is wrong with your project.
Note
If an ordinary deliverable — GeoTIFF, contours, the PDF report — will not download after a retry, contact us — and do the same if you need the full-density cloud from a capture whose point cloud could not be shipped.
Ready to try it on your own site?
Start a free trial — no credit card required.
Still stuck? Contact us and a human will help.