DebugRaptor Data Type

Use this class to configure Raptor Event Debugging. There are two ways to debug:

  1. Add a list of stops, and Raptor will print all events for these stops. This can be a bit overwhelming so using the path option might be a better option.
  2. Add a path (also a list of stops), and Raptor will print all events on the path. So if you arrive at a stop listed, but have not followed the exact same path of stops, then the event is NOT listed. Note! there are events for dropping an accepted path. If an none matching path dominate a matching path, then both paths are logged as part of the event.

    You may also specify the first stop in the path to start logging events for. For example given the path [1010, 1183, 3211, 492], then you may know, that you can get to stop 2 without any problems. So, to avoid getting spammed by logging events at the first two stops, you set the stop index 3211 as the first stop to print events for. This is done by adding an * to the stop: [1010,1183,3211*,492].

    3. To list stops you need to know the Raptor stop index. Enable log level="debug" for the org.opentripplanner.transit.raptor package to list all paths found by Raptor. The paths will contain the stop index. For paths not listed you will have to do some research.

Properties
name data type description

Example

{ }