See how DataTerra OS takes a mission from request to delivery

1 · Request

Turn an incoming request into controlled work

The Requests view uses four operational stages and offers both board and list views. Each card keeps the customer, product, country and age of the request visible.

Operator action

qualify the request, prepare the quote, update its status and review reminders.

Inputs

customer identity and contact, location or AOI, requested service, message, language and commercial context.

Output

a traceable sales record that can link to quote, payment, mission, processing and report.

Operational value

the team sees what needs quoting, what can be produced and what has been delivered without reconstructing the story from email.

Limit

the board structures decisions; it does not validate scope, pricing or flight feasibility.

2 · Preparation

Prepare the mission and regenerate the flight file

The mission sheet brings together date, coordinates, country, aircraft, job type, place and the linked customer request. Changing date, location or country refreshes weather and airspace data and regenerates the flight dossier.

Operator action

confirm the map point, select equipment and scenario, link the job and review warnings.

Inputs

coordinates, planned date, country, aircraft, mission type and customer AOI when available.

Output

a structured mission and an updated pre-flight dossier.

Operational value

weather and regulatory context stay attached to the job.

Verified detail

the screen suggests the two least-used batteries to balance fleet cycles; the actual battery is confirmed in the logbook.

Limit

airspace and weather data support preparation. They are not flight authorization.

What the flight file produces

The current document capture is Spanish or bilingual.

3 · Planning

Build a reviewable, exportable plan

The planner places waypoints, points of interest and obstacles on satellite mapping. Each point keeps settings such as altitude and speed; the lower panel shows elevation plus distance and duration estimates. Plans can be stored and exchanged as KMZ.

Operator action

draw or apply a template, order points, adjust parameters, inspect terrain, RTK bases and zones, and export the plan.

Inputs

site geometry, route type, waypoints, altitude, speed, orientation and identified obstacles.

Output

a reviewable plan and KMZ documenting flight intent.

Operational value

intent can later be compared with the actual flight.

Limit

the Spanish screenshot still contains some English controls. A plan does not replace field, radio-link or endurance checks.

4 · Preparation

Keep documentary compliance separate from authorization

The matrix cross-checks Mexico or Colombia context with the documents and certifications the operator has recorded. AFAC and Aerocivil references help review the file, and missing items stay visible before the mission.

Operator action

register documents and dates, review missing items and prepare the file.

Inputs

country, aircraft, operation type, insurance, registrations and certifications.

Output

a documentary attention list and expiry alerts.

Operational value

missing evidence can be found before arriving on site.

Mandatory limit

this is indicative assistance. It does not grant a permit, certify a mission as legal or replace the authority or specialist review.

5 · Flight

Compare planned and actual flight

The logbook imports DJI records and keeps coverage, battery, files and related reports together. Badges show whether a KMZ, technical report or final report exists and whether expected coverage was reached.

Operator action

import the log, link the mission, confirm equipment and battery, review coverage, GNSS, phases and notes.

Inputs

flight telemetry, KMZ when available, aircraft, battery and mission link.

Output

a traceable log entry and technical report with planned, covered and actual paths.

Operational value

execution evidence stays connected to preparation and delivery.

Limit

analysis depends on the fields present in the imported log.

Proof: the flight technical report

These two captures are currently rendered in French.

6 · Processing

Choose processing to match the job

The processing screen links photos, mission and customer request. The operator declares the job type and accuracy protocol, then runs compatible generators.

Operator action

add photos, confirm the mission, select job and accuracy, launch processing, review status and curate outputs.

Inputs

photographs, metadata, mission, declared accuracy and generator settings.

Output

depending on the job, orthomosaic, surface models, cloud or mesh, splat, volume and report files.

Operational value

production and delivery remain connected to the same CRM and mission chain.

Mandatory limit

not every generator applies to every job. The screenshot explicitly marks splat unavailable for Volume/stock. Accuracy also depends on capture and GPS, GCP or RTK protocol.

Technical proof: measure the change between two flights

A specific case from the Volume 2 mission — report rendered in French, not a universal performance promise.

7 · Delivery

Curate the report and client-visible files

The workbench groups requests and reports by status, product, country and language. The operator reviews results, generates or updates the report and selects client-visible files.

Inputs

request, mission context, processing results, language and validated observations.

Output

a variable-length final report and a curated deliverable set.

Operational value

delivery is reviewed, not an uncontrolled folder dump.

Limit

assisted narrative still needs professional review. The current Corasol sample has 13 pages; do not promise a fixed length.

A report that also exposes quality

Five panels from the Corasol report (public Spanish sample).

8 · Delivery

Let the client explore the deliverable

The following viewers demonstrate different deliverable types from different demo missions. Do not imply that every mission automatically creates all three. They are the same components the client sees in the portal.

2D orthomosaic

The georeferenced orthomosaic opens over a map. The client can switch the background, change opacity, zoom and download the authorized file. The output is a UTM COG; position and accuracy still depend on the field protocol.

Measurable 3D mesh

The textured mesh lets the client rotate the site, use the measurement tool and create an orbital view. It suits exploring reconstructed geometry; it is not a BIM or a certified inspection.

Photorealistic 3D visit

The gaussian splat offers a photorealistic walkthrough and can play or export an orbital sequence. Edge halos are normal artefacts of this representation seen up close, not a measuring surface.

9 · Operations

Distribute fleet wear

The fleet register tracks aircraft, equipment and batteries. The operator records inventory, maintenance, cycles and thresholds; the system exposes history and alerts.

Operational value

mission preparation and maintenance share the same usage history.

Limit

predictive alerts support but never replace physical inspection and manufacturer guidance.

10 · Operations

Find public opportunities in a dedicated workflow

The tender watch filters public notices and separates relevant, prospect and discarded items. The screenshot count is a snapshot, not a permanent claim.

Implemented connectors

SECOP II Colombia, PNCP Brazil, SAM.gov United States, DOF Mexico and OECE Peru. SECOP is enabled by default; other sources depend on admin configuration and SAM.gov requires an API key.

Limit

external-source uptime and commercial relevance are not guaranteed. The decision to bid belongs to the operator.

11 · Operations

Learn the workflow inside the product

Fourteen synchronized ES/EN/FR guides cover mission creation, cloud processing, maps and reports, volume, 3D visits and GCP/RTK workflows. The help starts from a task, not a module name.

Operator action

start from a task and open the matching recipe.

Output

a sequence of actions tied to the real product.

Verified availability

14 guides synchronized in ES/EN/FR.