PT Network Mapping with pt2matsim

Mapping GTFS transit schedules onto road networks is automated using pt2matsim, which takes a transitSchedule.xml file and network.xml.gz, then outputs network-with-pt.xml.gz and transitSchedule-mapped.xml.gz by matching transit routes to road geometry. This Skill handles the entire process from setup to parameter tuning.

Key tuning parameters for pt2matsim include maxLinkCandidateDistance, nLinkThreshold, maxTravelCostFactor, candidateDistanceMultiplier, networkRouter, and numOfThreads. Adjusting these resolves common issues like stuck processes, excessive artificial links, or route failures in metro, bus, and mixed transit networks.

Yes, pt2matsim supports multimodal public transit mapping across metro, bus, and mixed networks. This Skill optimizes parameters for different scenario types, allowing you to map complex transit schedules regardless of transit mode or network configuration.

You need a cleaned MATSim network file (network.xml.gz) and a GTFS-derived transitSchedule.xml. Prerequisites include verifying Java dependencies and ensuring your network is preprocessed and cleaned before pt2matsim processes it into network-with-pt.xml.gz and transitSchedule-mapped.xml.gz outputs.

Excessive artificial links typically result from overly permissive parameters like high maxLinkCandidateDistance or low nLinkThreshold. This Skill diagnoses and resolves such issues by tuning candidateDistanceMultiplier and other constraints to reduce unnecessary link creation while maintaining route accuracy.

Artificial link mode creates new network links where transit routes don't align with existing roads, useful for quick testing. Real link mapping constrains routes to existing network geometry. This Skill supports both modes, letting you choose based on your simulation needs and network detail level.