TRANSIT long-distance multimodal trips model results - a Spanish case study

Open data API in a single place

Provided by Zenodo

Get early access to TRANSIT long-distance multimodal trips model results - a Spanish case study API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2022.12.24 00:00
Created
2022.01.01
Available languages
English
Keywords
timetable synchronisation, agent based modelling, J-TAP, long-distance trips, TRANSIT, intermodality
Quality scoring

Dataset description

The files downloaded present the results per scenario considered obtained with the agent-based model developed for the assessment of the Intermodal Timetable Synchronisation solution proposed in the scope of the TRANSIT project (https://www.transit-h2020.eu/). An agent-based modelling framework called J-TAP has been developed and put at work to implement a Spanish long-distance multimodal trips model. The enhanced version of J-TAP used in this work can be found on a github repository. The case study is focused on modelling the long-distance travel patterns of the residents in the Valencia (Spain) area. The destinations considered include the whole of Spain. The period under study is a full year from March 2019 to February 2020 (both inclusive).The files are structured in three different scenarios: CS01 - Baseline. The current state of the network is considered and the actual long-distance travel patterns are obtained. CS02 - HSR connection with Madrid-Barajas airport. The long-distance travel patterns are modelled with hard measures, the high-speed rail is connected to Madrid-Barajas airport. CS03 - HSR connection with Madrid-Barajas airport and timetable synchronisation. The effects of the timetable synchronisation are modelled. Each scenario includes the following files: ctapModelParameters. A folder containing all the information extracted from the neo4j graph database created to model the multimodal network and the agents. J-TAP contains packages that simplify network creation in the graph database. This information is stored in .json files (e.g., "Os2DsTravelCostParameter.json" contains the generalised cost for each OD pair and transport mode, "AttractivenessParameter.json" contains the attractiveness by destination, activity, time of the year and agent, etc.). The solver included in the J-TAP framework uses this information to calculate the agents plans. population.json. The result of the J-TAP optimisation. It includes the fitness value for each agent plan evaluated during the J-TAP execution. The best plan for each agent is selected as the plan performed by the agent. An agent plan includes: activities - Sequence of activities. locations - Sequence of locations ts - Initial time of the activity te - Final time of the activity LinkTimeFlow.csv. It is obtained after processing the previous file. It contains the number of agents using each link in the network (i.e., road, rail, air and cross links) in each time interval. The first column represents the link id and the rest of columns indicates the number of agents in each interval. The J-TAP simulation framework is explained in detail in TRANSIT's deliverable D5.1. TRANSIT Modelling and Simulation Framework and the complete description of the case studies and scenarios tested is included in TRANSIT's deliverable D6.1. Impact Assessment of New Intermodal Concepts and Passenger Information Services: Conclusions and Recommendations. Thank you for downloading the dataset! It would be very helpful if you share your view on the data show with us. 
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks