NORMALIZE
Translate source-specific observations into a common model.
Understand
PILOT / INTEGRATETraffic Data Fusion
Multiple traffic sources. One reliable operational picture.
Flyvercity develops provider-agnostic traffic-data technology for Fleet Management, UTM/U-space and operational platforms that need to reconcile heterogeneous surveillance sources.
PROVIDER-AGNOSTIC DATA LAYER
ADS-BMode SMLATFLARMRemote IDProvider APIs
COMMON DATA MODELTraffic
Data Fusion
Data Fusion
Fused tracksQuality / healthFleet / UTM / Operational system
The integration problem
More feeds do not automatically create better traffic awareness.
Low-altitude operational systems increasingly consume traffic information from several technologies and providers.
The same aircraft can appear through multiple identities. Sources may update at different rates, disagree on state, become stale or disappear.
Without a dedicated fusion and quality layer, this complexity moves into the Fleet Management or UTM application itself.
DUPLICATE IDENTITIESUNEQUAL UPDATE RATESSTALE TRACKSSOURCE DISAGREEMENT
The product
A common layer between traffic sources and the operational system.
Flyvercity Traffic Data Fusion normalizes heterogeneous observations, associates reports belonging to the same trajectory, combines them into a common representation and exposes information about source and track quality.
01Traffic sources
02Common model
03Association
04Track fusion
05Operational system
ASSOCIATE
Determine when observations from different sources represent the same aircraft.
FUSE
Combine observations into coherent tracks.
QUALIFY
Expose stale, inconsistent or degraded information.
REPLAY
Reconstruct data and decisions for testing and analysis.
Architecture
Keep source complexity out of the consuming system.
Traffic inputs remain replaceable. The operational platform receives a consistent interface, fused tracks and explicit quality signals.
Provider-agnosticAPI-readyQuality-awareReplayable
PROVIDER-AGNOSTIC DATA LAYER
ADS-BMode SMLATFLARMRemote IDProvider APIs
COMMON DATA MODELTraffic
Data Fusion
Data Fusion
Fused tracksQuality / healthFleet / UTM / Operational system
Regulatory context
Traffic information becomes a data-assurance problem.
Regulation (EU) 2021/664 makes traffic information a mandatory U-space service and requires interoperable exchange with defined data quality, latency and protection.
EASA AMC and GM describe composite traffic information elaborated from several sources, uniqueness of delivery, timeliness and monitoring. Flyvercity provides a fusion layer that can support those technical workflows; it is not itself a claim of USSP certification.
EU / 2021/664U-space regulatory framework
Articles 5, 7 and 11 establish interoperability, data-quality and traffic-information requirements for the U-space context.
OPEN SOURCE ↗EASA / AMC + GMEasy Access Rules for U-spaceConsolidated AMC and GM explain traffic-information sources, uniqueness, timeliness, monitoring and operator responsibility.
OPEN SOURCE ↗EASA / ARTICLE 11Traffic information serviceThe service includes known manned and UAS traffic, position, report time, speed/direction and emergency status when known.
OPEN SOURCE ↗EASA / U-SPACEU-space implementation overviewOfficial overview of the services, certified actors and operating context for U-space airspace.
OPEN SOURCE ↗The relevant obligations depend on whether the consuming organisation is a UAS operator, USSP, CIS provider, ATSP, fleet platform or integrator. System responsibility remains with the regulated actor and its approved service context.
Who it is for
Built for systems that must combine several traffic sources.
UTM / U-SPACE PROVIDERS
Integrating surveillance sources into a common traffic service.
FLEET MANAGEMENT SYSTEMS
Giving operators a coherent picture without embedding source logic in the fleet application.
C2C PLATFORMS
Adding consistent traffic context to command-and-control environments.
SYSTEM INTEGRATORS
Connecting multiple providers through one quality-aware data layer.
Market + compliance trajectory
From connected feeds to an assured traffic layer.
The market is moving from source-by-source display integration toward traffic information that can be reconciled, qualified and tested as part of an operational system.
EVOLUTION
TODAYCONNECT
INTEROPERABLENORMALISE
MULTI-SOURCEFUSE
AT SCALEASSURE
MARKET
01
Operational platforms ingest individual surveillance feeds and provider APIs through source-specific integrations.
02
UTM, U-space and fleet platforms need a common representation across heterogeneous providers and technologies.
03
Systems must prevent duplicate traffic, manage disagreement and detect stale or disappearing observations.
04
Fleet automation increasingly depends on traffic information that is observable, testable and resilient to source change.
COMPLIANCE
01
Define the service context, authoritative inputs and the operational responsibility attached to the resulting traffic picture.
02
Support interoperable exchange, traceability and the data-quality, latency and protection expectations applicable to the service context.
03
Demonstrate how traffic is elaborated from several sources and how uniqueness, timeliness and degraded inputs are handled.
04
Maintain service evidence, records, monitoring and change impact as providers, airspace requirements and interfaces evolve.
FLYVERCITY
01
Source assessment: inventory formats, identities, timing, quality signals and consuming-system decisions.
02
Pilot: build the common model, adapters, provenance and repeatable replay environment.
03
Integration: association, fused tracks and explicit source/track quality delivered through one interface.
04
Operational layer: health signals, anomaly detection, replay, performance evaluation and controlled change.
PILOT / INTEGRATE
PILOT / INTEGRATEStart with a bounded integration problem.
A useful pilot begins with the sources, consuming system and operational decisions that the traffic picture needs to support.
Discuss a Data Fusion pilotDEFINE
Sources, identities, interfaces, update rates and expected operating conditions.
INTEGRATE
A common observation model and a controlled output interface.
REPLAY
Representative datasets for repeatable testing and tuning.
EVALUATE
Track coherence, quality behaviour and integration fit.
REAL PROGRAMME CONTEXT
Developed around operational integrations.
Flyvercity contributes positioning data fusion for the Helicus Command-and-Control Center in SAFIR-Ready, alongside work in European UAS research programmes.
Programme participation is evidence of applied work, not an authority endorsement.
Start with the operation
Combining traffic sources for a fleet or UTM system?
Show us the input feeds, consuming platform and operational decisions the traffic picture needs to support.
Discuss a Data Fusion pilot ↗