SwissRailRaptor PT Configuration & Troubleshooting

Agents fail to board when the transit module isn't activated, SwissRailRaptor parameters are misconfigured, or stopAreaId consistency is broken across transfer stations. Validate transit module activation, verify SwissRailRaptor algorithm settings, and ensure all transfer stations share matching stopAreaId values for seamless boarding and transfers.

Set useIntermodalAccessEgress to true in your SwissRailRaptor configuration, define access and egress modes, and configure transfer penalties appropriately. Start with a PT-only scenario using false and zero penalties to validate core routing before enabling intermodal features.

Transfer failures occur when transfer stations lack consistent stopAreaId configuration or when transfer penalties are set too high, blocking agent movement between routes. Diagnose by validating that all stops in a transfer station share the same stopAreaId and adjusting transfer penalty parameters for your scenario.

Zero boarding events indicate configuration gaps: verify the transit module is activated, check that SwissRailRaptor is enabled, confirm useIntermodalAccessEgress matches your scenario design, and validate that stopAreaId consistency holds across all transfer stations using debugging and test-run validation.

Yes. SwissRailRaptor supports PT-only routing by setting useIntermodalAccessEgress to false and transfer penalties to zero for initial testing. This simplifies validation and allows you to verify core routing logic before enabling multimodal features.

SwissRailRaptor provides realistic network-based PT routing with boarding events and transfers; teleported modes skip network simulation. Use SwissRailRaptor when agents must follow actual transit schedules, stops, and transfer constraints; use teleported modes for rapid prototyping when PT detail isn't critical.