Platform
One pipeline from roadside radio to REST API
Every source passes through an adapter into one canonical model. Privacy rules are applied before analytics, and analytics run off the ingest path, so the platform stays fast, consistent and auditable.
Architecture
Sources in, answers out
Sources
- Roadside unitsV2X · SAE J2735
- Driver phonesInvited, consented
- Telematics unitsAPI or device keys
- OEM & fleet platformsISO 20078
01
Normalize
One canonical model · COVESA VSS · SI units · Deduplicated, time-fixed
02
Protect
Daily pseudonyms · Consent per category · k = 5 publication
03
Analyze
Speeds & hot spots · Signal performance · Trips & scores
Delivered to
REST API · Dashboard · Your systems
Sources
Anonymous and identified data, on the same pipeline
V2X data is pseudonymous by design and only ever feeds aggregates. Identified data belongs to the organization that collected it, and never feeds shared products.
Connected vehicles (V2X)
Basic Safety Messages, signal phase and timing, and intersection maps from roadside units, decoded by USDOT’s open-source ODE.
- Works with V2X Hub and direct RSU forwarding
- Several upstream ODEs per agency
- One message heard by two RSUs is one observation
Phones and telematics units
Identified telemetry uploaded by an organization’s backend or by enrolled devices, under that organization’s consent ledger.
- Batch API with per-record results
- Device keys: signed tokens or mTLS
- Up to 7 days of offline buffering
Automaker & fleet platforms
Pull adapters for consented automaker data (ISO 20078) and telematics platforms, feeding the same canonical model.
- OAuth 2.0 client to OEM platforms
- Bulk ingest through a queue
Canonical model
One model every product reads from
Adapters do the messy work once: unit scaling, sentinel values, clock reconstruction and deduplication. Everything downstream can trust the data.
- SI units, named in the field
- speed_mps, heading_deg, accel_long_mps2: no guessing what a number means.
- Vehicle signals by COVESA VSS
- Names, units and ranges from the open standard, cross-referenced to J2735.
- Event time, reconstructed
- V2X carries milliseconds within the minute; the true time is rebuilt and its quality recorded.
- Unavailable means null
- Every J2735 “unavailable” sentinel becomes null, never a fake zero.
- One vehicle, one second
- A second per pseudonym or device is the downsampling and the deduplication, enforced by the database.
- Events always kept
- Every reported event survives downsampling, so safety signals are never sampled away.
Analytics
Analytics that give the same answer however data arrives
Analytics jobs run every minute, behind a short safety lag, and each one recomputes what new data touched. Steady-state lag is about 40–90 seconds against a five-minute target.
Map matching
Each position goes to the nearest road within 20 m whose direction is within 45° of the vehicle’s heading.
15-minute aggregates
Every touched bucket is recomputed in full, with exact percentiles and distinct-vehicle counts, so late data gives the same answer.
Intersection passages
Lane-level matching against the MAP version valid at the time, with crossing times interpolated at the stop line.
Trip detection
Stops, gaps and changes of driver end trips. The same rules run in our test harness, so every change is checked against known ground truth.
Reliability
Outages are lag, never loss
When something downstream is unavailable, data waits upstream until it recovers. Nothing is skipped to keep up.
Replay-safe
Replaying the same data twice creates zero new rows.
Crash-safe
Killed mid-batch while draining 30,000 messages: all 30,000 stored, none twice.
Bad records isolated
Invalid records never fail a batch; they are set aside, redacted, with a reason.
Late data welcome
Late signal data completes held-back cells with exactly the values an uninterrupted run gives.
Enterprise-ready
Organizations, roles and access you can audit
Each customer is an organization with its own members, API clients and policies. Access to every data cell requires an entitlement for that product, place and time.
| Role | Can |
|---|---|
| Org admin | Everything an analyst can do, plus members, API clients, MFA policy, retention and the audit trail |
| Analyst | Every entitled product, CSV export, 31-day ranges |
| Viewer | Entitled products as GeoJSON, 24-hour ranges, no export |
Single sign-on
Connect your OIDC or SAML identity provider; people with your email domain sign in through it.
MFA your way
Members can add an authenticator or security key, and an org admin can require it for everyone.
API clients
Machine credentials with chosen product scopes; the secret is shown once and can be rotated.
Audit trail
Every admin change, every on-behalf action by Traffica staff and every read of identified data, append-only.
See the platform on your data
We’ll walk you through the pipeline, the dashboard and the API, and scope a deployment around what you need to measure.