Photogrammetry in the Cloud: Upload Drone Photos, Let CartaX Produce

Turning the 600 photos from a flight into products normally takes a powerful computer and someone to watch it for hours. Cloud production needs neither: you upload the photos, CartaX produces, and the outputs land in the project you chose and become layers on the map. This guide walks through the cloud route end to end; for the details of photo preparation see the photogrammetry guide.

Cloud production is part of the Professional plan; a single job carries up to 2,000 photos. For larger projects talk to us about the Enterprise plan.

Two ways to start

	Where	When it fits
Web	Upload data dialog → Photogrammetry card	When you want to send from the browser without installing Studio
CartaX Studio	Create wizard → Produce in the cloud	When Studio is already installed; GCP marking and advanced settings live here

Both routes end in the same place: you pick the photo folder (subfolders are scanned too), tick the outputs and add a GCP file if you have one. Production starts by itself once the upload finishes; there is no extra button to press. After the photos are uploaded you can shut your computer down — the job keeps running in the cloud.

What is produced?

Output	What you get on the map
Orthophoto	Produced in every job; a raster layer in the project
DSM / DTM	Comes with the orthophoto; the Measurement elevation: Surface / DSM / DTM selector in the layer settings, elevation readout and volume calculation
Point cloud	Optional; auto-classified (ground, vegetation, building, road, vehicle…) and opened in its own viewer
Classes	Objects recognised on the orthophoto (building, road, vehicle, water, farmland, power line…) — not a separate option, it comes with cloud production
Textured 3D model	Currently shown with a coming soon badge on the cloud route; cannot be selected

Production runs at a single quality: High. There is no lower tier — it was designed that way so measurements and imagery stay consistent. To shorten the run, drop the point cloud.

If you type object names such as greenhouse or silo into the Extra objects (optional) field, they are searched for on site as well and arrive in the Classes window as the Custom class. Details: Classes guide.

GCPs and "fit products to my points"

A GCP file is optional; if you provide one, positional accuracy is measured at the end of the job and the Accuracy report opens from Production history on the dashboard. The advanced settings of the Studio wizard also offer Fit products to my points (datum correction): the constant offset between your points and the products is measured and applied to the orthophoto, DSM/DTM and point cloud — no re-production needed. The options for using GCPs in the solution (report only, find automatically, mark manually) are explained in the photogrammetry guide.

Tokens: an estimate before the job starts

The charge follows the amount of imagery processed: photo count × resolution (megapixels). The number of outputs you tick does not change the price. As soon as you pick the photo folder, the dialog shows the photo count, the total megapixels and the estimated tokens on one line, with your available balance next to it. If the balance is short the job does not start: the "Insufficient balance; the upload will not start until tokens are purchased" notice appears with a link to buy tokens. No half-finished jobs, no wasted tokens. For the token rules see Plans and tokens.

Duration and tracking

Production usually takes 2–4 hours; depending on load it can stretch to 8. Waiting a few hours for a few hundred 45 MP photos is normal. You are notified when it finishes.

Follow progress live in the Running jobs section of the CartaX Studio card on the dashboard; if you sent the job from Studio it also appears on the Jobs screen. Finished jobs collect in Production history: the jobs of the last 90 days and the tokens spent.

Where do the outputs go?

Into the project you selected. The orthophoto becomes a layer on the map; the DSM/DTM unlocks the Measurement elevation selector in the layer settings; the point cloud opens in its own viewer; and the Classes button appears in the orthophoto row. There is nothing to download — measurement, sharing and analysis work directly on these layers.

Capture tips

The quality of the result comes from the photos:

• Overlap: 75–80% forward, at least 65% side. Too little overlap means holes in the model and drifting edges.
• Same altitude: fly the whole mission at one altitude; mixed altitudes make the resolution uneven.
• Oblique pass: if you want façades textured as well, add an angled pass to the nadir flight.
• Avoid: moving water, uniform snow or sand, harsh shadows, and mixing different lighting conditions in one job.
• Position data: the photos must carry GPS information; on RTK drones centimetre-level positions are picked up automatically.

How it differs from local production in Studio

	Cloud	Studio (local)
Cost	Tokens (by megapixels)	No tokens spent
Your computer	Stays free; shut it down after the upload	Busy for the whole run
Classes	Yes	No
Photo cap	2,000 per job	No hard cap; memory and disk decide
Raw photos	Uploaded to CartaX	Stay on your computer

For the local route see Local production with CartaX Studio.

Related guides

• Orthophoto from drone photos
• Classes: automatic object recognition
• Local production with CartaX Studio
• Plans and tokens
• DSM vs DTM: what is the difference?

Frequently asked questions

Question	Answer
Is it available on the Free plan?	No; it is part of the Professional plan.
How many photos can I send?	Up to 2,000 per job.
What is the price based on?	Photo count × megapixels; the number of outputs does not change it.
What if I do not have enough tokens?	The job does not start; you buy tokens first.
How long does it take?	Usually 2–4 hours; up to 8 under load.
Can I shut my computer down?	Yes, once the upload has finished.
Can I choose a quality?	One quality: High.
Do I get a 3D model?	Currently "coming soon" on the cloud route.
Do Classes cost extra?	No.