JSON

One use-case is to run a routing search in debug-filter-mode and instead of removing itineraries from the result, the itineraries could be tagged instead. These notices are meant for system testers and developers and should not be used for end user notification or alerts.

Turn onto Broadway from W 57th St (coming from 7th Ave):
distance = 100 (say)
walkDirection = RIGHT
streetName = Broadway
everything else null/false

Now, turn from Broadway onto Central Park S via Columbus Circle
distance = 200 (say)
walkDirection = CIRCLE_COUNTERCLOCKWISE
streetName = Central Park S
exit = 1 (first exit)
immediately everything else false

Instead, go through the circle to continue on Broadway
distance = 100 (say)
walkDirection = CIRCLE_COUNTERCLOCKWISE
streetName = Broadway
exit = 3
stayOn = true
everything else false

These are parameters that when changed, necessitate a Graph rebuild. They are distinct from the RouterParameters which can be applied to a pre-built graph or on the fly at runtime. Eventually both classes may be initialized from the same config file so make sure there is no overlap in the JSON keys used.

These used to be command line parameters, but there were getting to be too many of them and besides, we want to allow different graph build configuration for each Graph.

TODO maybe have only one giant config file and just annotate the parameters to indicate which ones trigger a rebuild ...or just feed the same JSON tree to two different classes, one of which is the build configuration and the other is the router configuration.

• Store intermediate point in fixed floating points with fixed precision, using delta coding from the previous point, and variable length coding (most of the delta coordinates will thus fits in 1 or 2 bytes).

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].

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.

Fare is a set of fares for different classes of users.

1. id - All entities should have an id. The id should be unique within the context the entity live. For aggregates which live in a global space the id must be unique. This apply to all entities listed in the index service.
2. The hashCode()/equals() method is consistent and based on the id (identity). We frequently use this to index and lookup entities.

FareComponent is a sequence of routes for a particular fare.

1. id - All entities should have an id. The id should be unique within the context the entity live. For aggregates which live in a global space the id must be unique. This apply to all entities listed in the index service.
2. The hashCode()/equals() method is consistent and based on the id (identity). We frequently use this to index and lookup entities.

1. id - All entities should have an id. The id should be unique within the context the entity live. For aggregates which live in a global space the id must be unique. This apply to all entities listed in the index service.
2. The hashCode()/equals() method is consistent and based on the id (identity). We frequently use this to index and lookup entities.