GNSS resilience
Preserves continuous navigation when GNSS is jammed, spoofed, unavailable, or untrusted by relying on fused inertial, visual, and terrain-referenced navigation.
ULTRAKINEMATICRequest briefing ↗Navigation sovereignty for unmanned systems
NavioTerra
Resilient visual-inertial and terrain-referenced navigation for unmanned vehicles.
GNSS-independentAnti-jammingAnti-spoofingMeaconing Proof
Discover NavioTerra →Scroll to explore
01 / Mission
Built for GNSS-denied environments.
When GNSS becomes unavailable or untrustworthy, NavioTerra continues navigating. It fuses inertial, visual, and terrain-referenced information to maintain a resilient navigation solution with a transparent solution-confidence estimate.
Terrain-referenced navigation
Provides terrain-referenced absolute position corrections without depending on visible-light imagery, supporting navigation beneath cloud cover, at night, and in very low-light conditions.
Visual navigation
Uses onboard vision for odometry and satellite-scene matching across a wide operational altitude envelope.
02 / System architecture
Multiple references.
One trusted solution.
NavioTerra continuously evaluates, weights, and fuses available navigation references according to their integrity, availability, and confidence.
INS / IMU
High-rate inertial propagation using calibrated accelerometer and gyroscope measurements.
GNSS
Global position and timing reference when available and trustworthy.
Visual odometry / VIO
Camera and inertial motion estimation used to constrain drift through tracked visual features.
NavioTerraFusion engineTerrain reference
Matches radar-altimeter terrain profiles against elevation data for absolute position correction.
Scene matching
Georeferenced satellite-image matching for absolute position correction without trusted GNSS.
Integrity monitoring
Monitors source health to identify, deweight, or reject anomalous references before fusion.
Fused outputNavigation Solution
01Position02Velocity03Attitude04Solution confidence05Source health
Solution confidence
Communicates the expected reliability of every navigation solution using covariance-based uncertainty estimates for position, velocity, and attitude.
Source health
Continuously reports the availability, consistency, and trust level of each navigation reference, including references that are active, deweighted, or rejected.
03 / GNSS-denied continuity
Engineered for navigation sovereignty.
NavioTerra detects GNSS degradation, limits the influence of unreliable measurements, and continues navigating with fused inertial, visual, and terrain-referenced information.
Conventional architecture
Navigation lostGNSS-dependent system
GNSS nominalSpoofing beginsGNSS deniedExtended denial
GNSS trustAccepted → Lost
INS errorDrift increasing
Position errorUnbounded
Spoofed position is followed; after denial, unaided INS drift accumulates.
Resilient architecture
Navigation maintainedNavioTerra
GNSS nominalSpoofing beginsGNSS deniedExtended denial
Anomaly scoreRising
GNSS weightDeweighted
Fused errorConstrained
INS propagation continues while visual and terrain references constrain drift.
Same environment. Different outcome.
04 / Capability comparison
Built for navigation when GNSS can no longer be trusted.
NavioTerra combines inertial, visual, DSMAC and TERCOM-style terrain-referenced navigation with explicit integrity logic, allowing the system to degrade intelligently instead of depending on a single positioning source.
| System | GNSS spoofing detection | GNSS-denied operation | Night + GNSS-denied | Above-cloud + GNSS-denied | Rain + GNSS-denied | Absolute position in GNSS-denied | High-rise urban canyon |
|---|---|---|---|---|---|---|---|
| NavioTerraINS + visual + DSMAC + TERCOM with integrity-managed fallback | ✓Cross-checks GNSS against inertial, visual and map-relative sources | ✓Designed for denied and degraded navigation modes | ✓TERCOM and inertial aiding do not depend on daylight | ✓Terrain-referenced aiding can continue without optical ground visibility | ✓TERCOM preserves operation when visual or LiDAR confidence drops | ✓Uses validated scene or terrain references when available | ✓Rejects GNSS and shifts to INS, VIO and urban scene matching |
| GNSS onlySatellite receiver as the sole positioning source | !Receiver dependent; no independent motion or scene cross-check | × | × | × | × | × | ×Multipath and signal blockage can corrupt or remove the fix |
| GNSS / INSGNSS-aided inertial navigation | !Can flag inconsistencies, but GNSS remains the absolute reference | !Dead reckoning continues for a limited time | !Light independent, but drift-limited without external updates | !Can coast inertially; uncertainty grows over time | !Weather independent only while inertial drift is acceptable | ×No new absolute fix after GNSS loss | !INS smooths urban GNSS errors, but absolute position still depends on GNSS |
| GNSS / INS / VIOInertial navigation aided by visual odometry | ✓Visual motion can challenge inconsistent GNSS updates | !Works while visual tracking remains valid; drift accumulates with route length | !Depends on illumination, camera type and visible texture | !Cloud scenes can be ambiguous or non-stationary | !Rain can reduce visual feature quality | ×VIO is primarily relative without map matching | !Helps in urban canyons, but long routes drift without map matching |
| GNSS / INS / VIO / DSMACDigital scene matching against satellite imagery | ✓Scene match provides an independent absolute cross-check | ✓Strong when the referenced ground scene is visible | !Depends on sensor band, image quality and reference data | ×Cloud cover blocks the ground scene for optical matching | !Rain can reduce scene clarity and match confidence | ✓Absolute correction from georeferenced imagery | ✓Urban imagery can provide corrections when the ground scene is visible |
| GNSS / INS / SLAMLiDAR or visual SLAM-aided navigation | ✓SLAM motion can reject inconsistent GNSS behavior | ✓Works when the environment supports SLAM tracking | !LiDAR can work at night; visual SLAM depends on light | !Cloud or open-sky scenes may not provide stable landmarks | !Rain can affect cameras and some range sensors | !Absolute only with a georeferenced prior map or known landmarks | !Strong with stable landmarks; absolute position needs a prior map |
✓Supported!Condition dependent×Not inherent
Technical notes
DSMAC means Digital Scene Matching: matching onboard imagery against georeferenced satellite or map imagery to obtain an absolute position correction.
NavioTerra's night, above-cloud and rain entries assume its TERCOM/terrain-referenced aiding path is active with suitable terrain reference coverage. Pure visual, LiDAR or optical scene-matching systems can still degrade in darkness, rain or cloud-obscured scenes.
In high-rise urban areas, NavioTerra prioritizes GNSS integrity checks and can shift toward INS, VIO and DSMAC-style urban scene matching.
05 / Key capabilities
One navigation core.
Every available reference.
NavioTerra combines resilient positioning, integrity monitoring, and platform-level geo-awareness in a single adaptive navigation system.
Real-time navigation
Continuously estimates position, velocity, and attitude with user-configurable navigation output rates.
Adaptive sensor fusion
Evaluates and combines GNSS, INS/IMU, visual, and terrain references for diverse UAV platforms and operating conditions.
Resilient GNSS
Supports dual-band, multi-constellation GNSS with jamming, spoofing, and meaconing detection and integrity-managed fallback.
Absolute position aiding
Combines RTK, terrain-referenced navigation, and vision-based map matching to constrain drift and restore absolute position.
Navigation integrity
Monitors source health, detects anomalies, adjusts measurement weighting, and reports solution confidence with every navigation solution.
Geo-awareness
Supports offline geofencing, water-body and urban-area awareness, no-fly zones, and real-time MAVLink proximity alerts.
06 / Integration
Mission-ready output.
Platform-ready interfaces.
The fused navigation solution output rate is user-configurable from 100 to 250 Hz. Individual perception and correction algorithms operate according to their own sensor and processing rates.
Developer SDK & API
Build on the navigation core
Integrate custom applications, stream telemetry, access sensor data, and configure NavioTerra for existing autonomy and mission software.
SDKAPINMEAMAVLinkDiagnosticsData logging
- Navigation state
- Position / Velocity / Attitude
- Solution integrity
- Solution Confidence / Source Health
- Navigation solution output rate
- User-configurable, 100–250 Hz
- GNSS constellations
- GPS / Galileo / GLONASS / BeiDou / QZSS
- GNSS frequency bands
- L1/L2 / E1/E5b / B1/B2
- Precision positioning
- RTK support*
- Geo-awareness
- Offline geofencing / MAVLink alerts
- Peak power draw
- 20 W
- Board mass
- 90 g — excluding enclosure and connectors
- Platform interfaces
- Ethernet / CAN / UART / USB
- Sensor integration
- Camera / Radar Altimeter / GNSS / IMU
- Output formats
- NMEA / MAVLink / Custom SDK
* RTK can provide centimeter-level positioning under suitable correction availability, antenna configuration, satellite geometry, and operating conditions.
Configurable I/O architecture
One core platform.
Two integration paths.
Communication interfaces, telemetry outputs, data formats, and control channels can be tailored to the customer’s UAV, mission computer, payload system, and software stack—without redesigning the core navigation hardware.
Development Kit
A flexible platform for evaluation, integration, and application development.
- Configure and calibrate the navigation system
- Run diagnostics, stream telemetry, and log sensor data
- Develop and validate SDK and API workflows
Fly-Ready Kit
A mission-ready configuration prepared for direct UAV integration.
- Preconfigured hardware and integration software
- Customer-aligned I/O, telemetry, and control formats
- Ready-to-integrate operational setup
07 / Technical briefing
Bring resilient navigation into your platform.
Tell us about your platform, operating environment, and integration stage. Our engineering team will assess the fit and arrange a focused technical discussion.
01
Share your mission profilePlatform, environment, and navigation constraints.
02
Review with engineeringA focused discussion around architecture and integration.
03
Define the next stepEvaluation kit, integration scope, or tailored configuration.