FIT THE TOOLS YOUR TEAM ALREADY USES
Open the workflow. Keep the context.
Connect processing and field work to existing geospatial systems. Use supported open formats, configured GIS services and field-data integrations to make the next handoff practical.
FEATURE / 11
Formats & integrations
- Raster and terrain
- Vector and offline data
- Point clouds and scenes
- GIS services
CAPABILITIES
Choose the connection by the job.
Format support, service compatibility and deployment availability are different questions. Validate all three with a representative dataset and client.
Raster and terrain
Plan workflows around GeoTIFF and Cloud Optimized GeoTIFF where supported, preserving coordinate and numerical context.
Vector and offline data
Use GeoPackage, GeoJSON and other supported exchange formats. Field Sentinel also supports offline tile-package workflows.
Point clouds and scenes
The broader engine includes LAS, LAZ, COPC, 3D Tiles and I3S workflows, with support depending on the selected processing and viewing path.
GIS services
Evaluate configured OGC and Esri-compatible endpoints with the intended QGIS, ArcGIS or other consuming client.
Field collection backends
Field Sentinel documents QFieldCloud, ODK Central, KoBoToolbox and MAGE integration paths for existing collection environments.
Operational feeds
Connect supported TAK/CoT, receiver and sensor sources through the relevant platform interfaces and credentials.
Video and FMV sources
Connect supported streaming protocols and recorded KLV sources. Use configured FFmpeg relay and extraction paths where required.
MAVLink aircraft
Bring supported PX4/ArduPilot telemetry into the map and evaluate gated mission and payload paths for qualified configurations.
DJI mission files and media
Use WPML/KMZ and supported video/telemetry handoffs. Review the dedicated DJI page for the current SDK and controller-transfer scope.
THE WORKFLOW
A clear path through the work.
Identify
01
Name the source and consuming system.
Sample
02
Supply representative data and metadata.
Validate
03
Check the format, client and access path.
Connect
04
Document the supported handoff.
THE RESULT
Make compatibility a concrete conversation.
Bring a real file, service URL or field backend to the workflow review. A representative end-to-end example is more useful than a long list of extensions. Add GeoInsights for broader API integration, real-time event and movement-data workflows, and operational analytics; choose SaaS or self-hosted deployment.
WHAT YOUR TEAM TAKES FORWARD
- Processing and viewing paths matched to the source
- GIS delivery tailored to the consuming client
- Field connections that respect the existing system of record
AVAILABILITY & WORKFLOW SCOPE
This page describes product-family integration options, not universal format certification. Broader formats and service delivery in the private cloud pilot remain subject to qualification.
QUESTIONS, ANSWERED
A few useful details.
Can we connect our existing GIS?
The broader engine provides service and exchange-file workflows. Confirm the data type, client version, deployment and authentication requirements with a sample.
Are all listed formats enabled in the cloud pilot?
No. The cloud pilot supports selected profiles. Broader processing and viewer capabilities are available through other configured engine workflows.
BRING YOUR NEXT PROJECT
Let’s connect your workflow.
Start with a collection, an operational challenge or a deliverable. We’ll help map the path from capture to a useful result.
dronescoutCLOUD
From aerial collections to shared operational understanding.
By Tech Maven Geospatial
TMG Home ↗
Free companion apps
Contact the team
© 2026 Tech Maven Geospatial. Drone Scout Cloud.
Free companion apps; hosted services and enterprise editions are separate. Cloud workspace available for pilot evaluation.