org.transitime.custom.missionBay

Class MissionBayConfig

java.lang.Object

org.transitime.custom.missionBay.MissionBayConfig

public class MissionBayConfig
extends java.lang.Object

Contains GTFS config information of stop and paths for the directions. Wanted this info to be automatically generated from the NextBus API but there simply is not sufficient information in the API. This is especially true given the many different trip patterns there are for Mission Bay. For example, the caltrain route has many variations.

Author:

SkiBu Smith

Constructor Summary

Constructors

Constructor and Description
MissionBayConfig()

Method Summary

Modifier and Type	Method and Description
static java.util.Map<java.lang.String,java.util.List<java.lang.String>>	getPathData() Defines the path data for all routes and puts it into the shapeIdsMap.
static java.util.List<GtfsFromNextBus.Dir>	getSpecialCaseDirections(java.lang.String routeId) Provides list of stops for each possible direction/trip pattern.

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

MissionBayConfig

public MissionBayConfig()

Method Detail

getSpecialCaseDirections

public static java.util.List<GtfsFromNextBus.Dir> getSpecialCaseDirections(java.lang.String routeId)

Provides list of stops for each possible direction/trip pattern. Turns out this is rather complicated because of the variations in the trips so resorted to hard coding the stops.

Good way to determine which stops are part of a direction/trip is to look at the schedule API such as http://webservices.nextbus.com/s/xmlFeed?command=schedule&a=sf-mission-bay&r=west Then list the stops for each trip pattern below.

Parameters:

routeId -

Returns:

getPathData

public static java.util.Map<java.lang.String,java.util.List<java.lang.String>> getPathData()

Defines the path data for all routes and puts it into the shapeIdsMap. Of course would have preferred to automatically determine the paths for each trip pattern using only the NextBus API but the naming conventions were far too haphazard. Only way to really make it work is to list the path IDs here manually by looking at data in (for route west for example) http://webservices .nextbus.com/service/publicXMLFeed?command=routeConfig&a =sf-mission-bay&verbose=true&r=west From the URL you can see all of the paths. Then for each trip pattern defined in the above method getSpecialCaseDirections() you need to include all the paths between the stops, including the "_d" departure paths, to get the full shape.

Returns:

Map containing all the shape information for the agency