Farleda
EN

For infrastructure partners

Turn mobility data into traceable journey chains.

Context and provenance can be lost between timetables, transport hubs, services and traveller interfaces. Farleda aims to make these handovers visible and improve specific cases with infrastructure partners.

Farleda is software for journey planning and calculation records. The proposed infrastructure layer does not operate safety-critical signalling, interlocking or network control.

Farleda · Editorial review

Examine one data handover.

A pilot can start with a station, a cross-border journey or an exchange between two systems. The question is specific: which information is missing, when was it valid and how does that affect the journey option shown?

  • Map identifiers and interchange points across sources.
  • Make source timestamps, coverage and missing values visible for selected test cases.
  • Record failures and fallback values separately so an approximation cannot appear to be confirmed operating information.

An interface starts with a data agreement.

Format, meaning, rights and responsibilities must align before a technical connection is made. A supported data format alone does not establish an implemented Farleda integration or a suitable feed.

  • Format and semantics: sample data, schema, version and unambiguous field meanings.
  • Operation: refresh frequency, failure handling, fallback behaviour and an accountable contact.
  • Rights: use, retention, redistribution, attribution and deletion requirements.
  • Acceptance: agreed test cases, measurable criteria and documented limits.

An existing foundation and a scoped next step.

The implementation uses services including Transitous for available public-transport routes, alongside Farleda calculations and passport functions. A direct connection to your system, additional formats, guaranteed latency and contracted availability belong in the joint pilot scope.

  • An HMAC-signed calculation record protects the integrity of the stated content within Farleda.
  • It does not establish operational network safety or replace partner evidence that a journey occurred.
  • Independent public-key verification and complete reproducible source snapshots remain development objectives.

An outcome product and operations teams can use.

The pilot should deliver documented data mappings, reproducible test cases, an assessment of gaps and a reasoned integration approach. Ongoing operation, service levels and maintenance are agreed on that basis. Research partners may contribute an independent evaluation.

Common questions

Is every European network already connected?

No. Coverage depends on the sources and feeds actually available. A pilot checks the relevant region and use case explicitly.

Can Farleda guarantee real-time data?

Real-time information requires an appropriate feed, reliable timestamps and agreed operating conditions. Timetables, current observations and modelled values are assessed separately.

Where does Horizon Europe fit?

Farleda plans an application and is seeking use cases, research partners and consortium contributions. The call and consortium remain open; no funding is confirmed.

Next step

Where does the data handover break down today?

Describe the handover, participating systems and desired outcome. Together we can identify a bounded pilot scope.

Discuss an infrastructure pilot