Skip to content

Use case

Moving drone, LiDAR and photogrammetry data from the field

Boita for drone, survey and GIS is a way to push days of LiDAR captures, orthomosaics and GeoTIFF tiles from a field office to the processing team overnight from the desktop app, resuming over unreliable links, so processing starts before a drive would have arrived — one use of Boita, the large-file transfer workspace for anyone who moves a lot of data.

A survey week produces terabytes on a laptop in a site office with a mediocre connection. Boita is built to push that data out overnight, survive the link dropping, and let the processing team start before the drive would have reached them.

A Boita upload portal as a client sees it: “Field footage drop — north basin” from Meridian Labs, a short instruction, and the upload area, with nothing to install.
An upload portal: a client’s page that lands files straight in your folder.

The courier is the bottleneck

Drone, LiDAR and photogrammetry projects produce point clouds, raw captures and orthomosaic tiles by the hundred gigabytes per day. Posting a drive works until it is lost, delayed or arrives corrupt, and browser uploads over a site connection tend to fail halfway through and start again.

Boita’s accelerated transfer engine runs over UDP with its own rate control, so it holds your line rate regardless of the distance to the server. In the desktop app, transfers resume by themselves from where they stopped after a network drop, sleep or reboot, and completed files are never re-sent. From a browser or the phone app, an interrupted transfer starts again, so run field uploads from the desktop app.

Point a watch folder at the capture drive

Install the desktop app on the field laptop and point a watch folder at the folder where captures are offloaded. New files upload as they appear, once they have stopped changing, and the queue keeps running from the menu bar or tray with the window closed. State is kept locally, so a restart does not re-upload the week.

Allowed hours per watch folder and a workspace bandwidth window, enforced by the transfer server, let the site connection be used only after hours. Include and exclude patterns are coming.

A 400 GB week of captures on Pro, over a 100 Mbps site line, takes about nine hours, line-limited, which is an overnight window. Back at the office on a 1 Gbps line the same 400 GB takes about two hours, plan-limited at 450 Mbps. The calculator on the home page models your own line and distance.

Share results with clients who have no account

Processed orthomosaics and models go out as share links with an expiry, an optional password and a download limit. Clients open a page, see the files and sizes, and download; no account or plan of their own. Receiving raw data from a subcontractor works the same way in reverse through an upload portal that drops each delivery into its own inbox folder.

Intact, and you can check

Every file shows the checksum the server recorded when it arrived, so a corrupt tile is caught at ingest rather than in the deliverable. Numbered tile sets show as one row with a gap warning. Storage usage is shown on every page with an email before you reach your quota, and there are no per-GB transfer fees, so a heavy capture month does not produce a surprise bill.

Projects that must be kept but rarely opened can move to the archive tier with a manifest and restore on demand (Scale and above).

  • Line-rate transfers from field connections, resumable in the desktop app
  • Watch folders on the offload laptop; allowed hours and bandwidth windows
  • Share links and upload portals with no accounts for the other side
  • Checksums on every file; storage usage always visible
  • Flat plans, no per-GB fees

Questions people ask

Boita for drone, survey and GIS, in answers.

Written the way people ask an assistant, and published the same way in products.json and llms.txt. More in the full FAQ.

How do we get a survey week off a laptop in a site office?

A watch folder in the desktop app on the laptop pushes captures overnight; it resumes each time the link drops and never re-sends finished files. The processing team pulls from the workspace at their own line rate.

Does Boita handle thousands of tiles?

Yes. Numbered sets show as one row with the range and gap warnings, and every tile has a checksum.

Can the client receive deliverables straight into their own bucket?

Yes, with a bucket destination or Enterprise auto-delivery.

What happens when the site connection drops overnight?

In the desktop app, the transfer waits and resumes from its checkpoint when the link is back, and nothing already uploaded is sent again. A browser upload starts again.

Can we limit how much of the site connection Boita uses?

Yes. A watch folder can send only between chosen hours, and the workspace can cap transfers during office hours; the transfer server enforces the cap. You can also lower the rate from the app during a transfer.

Do LAS, LAZ or GeoTIFF files need special handling?

No. Boita moves any file type as is. Images and PDFs get previews; point-cloud viewers are not planned.

Is there a Linux client for a field server?

Yes. The desktop app ships as an AppImage, and the headless boita-agent runs watch folders on a server under systemd, with the boita CLI for scripts.

Next step

Try it, or ask first.

Start free with 10 GB and no card, book a demo, or talk to a person on WhatsApp. Leads from this page reach us with the page name attached, so the reply already knows what you read.

Tell us what you move

Sizes, where it goes, and what is slow today. A person replies with the plan and the setup that fit — no drip sequence.

Or write to hello@boita.io. Your details go to our team only; see the privacy policy.

Try it on your next transfer.

Create a free workspace with 10 GB, move one thing and watch it fill your line. Plans are flat and in your currency.

Chat on WhatsApp