Skip to content

Telemachus Core Specification

Welcome to the Telemachus Core documentation.
This project defines an open pivot format for B2B telematics data (GNSS, IMU, CAN, Events, Context).
It aims to unify fragmented data from providers (Geotab, Webfleet, Samsara, etc.) into a single, neutral schema.

❓ Why Telemachus?

  • Open: A transparent and accessible format for all stakeholders.
  • Extensible: Designed to accommodate evolving telematics data types and sources.
  • Interoperable: Bridges diverse providers and systems under a unified schema.
  • Bridging science and business: Facilitates both research innovation and practical applications.

👥 Who is it for?

  • Researchers: Access standardized data for analysis and modeling.
  • Developers/Integrators: Simplify integration with multiple telematics providers.
  • Fleet Operators/Insurers: Leverage consistent data for operations, monitoring, and risk assessment.

🚀 Quickstart

Validate provided examples against the schema:

# Install ajv-cli and ajv-formats
npm install -g ajv-cli ajv-formats

# Validate all example files
ajv validate -c ajv-formats -s schemas/telemachus.schema.json -d "examples/*.json"

🌍 Vision

Telemachus wants to do for telematics what GTFS did for public transport:
- Provide an open, simple standard.
- Enable interoperability across providers.
- Support both scientific research and business applications.

🔗 Data Flow Overview

graph TD Prov[Providers: Geotab · Webfleet · Samsara] --> Core[Telemachus Core · Open Pivot Schema] Core --> Fleet[Fleet Premium · Missions · KPIs · SLA] Core --> Research[Research · Data Science · Simulation] Fleet --> Apps[Business Apps · Fleet Mgmt · Insurance] Research --> Sci[Scientific Outputs · Publications · Models]

📖 Citation

If you use Telemachus in research or projects, please cite:

S. Edet (2025). Telemachus Core Specification (v0.1-alpha).
Zenodo. https://doi.org/10.5281/zenodo.17228092

DOI