Vehicle data
Connect vehicle data through a controlled adapter path.
Start with a local-supported connector shape. Add real endpoints, credentials, device tokens, retention rules, and monitoring only when a deployment owner is ready.
Choose One Starting Path
| Path | Use when | First safe check | Owner |
|---|---|---|---|
| CSV replay | You have synthetic or public-safe vehicle observations for evaluation. | Run a local dry-run before sending telemetry. | Administrator or integrator |
| HTTP polling | A deployment-owned endpoint exposes vehicle observations. | Review polling credentials and fail-closed behavior. | Deployment owner |
| Webhook sidecar | A source can push payloads to an adapter process. | Normalize and redact payloads before forwarding. | Integrator |
| Generic JSON transform | Source data maps cleanly into the telemetry event shape. | Run transform conformance with synthetic fixtures. | Integrator |
| Authenticated telemetry POST | The source already emits normalized events. | Use deployment-owned device tokens for /v1/telemetry. | Administrator |
What Operators Can Review
- Device bindingsWhich device is associated with which vehicle.
- FreshnessWhen the latest observation arrived and whether stale thresholds are crossed.
- Assignment confidenceWhether the matcher can safely associate a vehicle with a trip.
- Realtime feed effectWhether Vehicle Positions, Trip Updates, and Alerts reflect the current setup.
Limits
Local connector examples and synthetic checks do not prove real vendor compatibility, hardware certification, production AVL reliability, consumer acceptance, compliance, production readiness, SLA coverage, or ETA quality.