|
FareExamples
Illustrates how to implement different fare structures with the GTFS
Featured IntroductionThe fare_attributes.txt and fare_rules.txt files in the Google Transit Feed Specification can be confusing. The following examples work through different kinds of fare structures and show how to represent them in a Google transit feed. Fare Examples
Example 1: All trips have the same fare, unlimited transfersSuppose Demo Transit Agency has the following fare structure:
Since all trips have the same fare, Demo Transit can omit fare_rules.txt. fare_attributes.txt
Calculating an adult fareThe trip planner calculates a fare of $1 for each leg of the itinerary that includes a change of vehicle. However, unlimited transfers are permitted, so the trip planner only displays the lowest charge. Adult fare: $1 Example 2: All trips have the same fare, no transfersSuppose Demo Transit Agency has the following fare structure:
Since all trips have the same fare, Demo Transit can omit fare_rules.txt. fare_attributes.txt
Calculating an adult fareThe trip planner calculates a fare of $1 for each leg of the itinerary that includes a change of vehicle. So an itinerary that requires a change of buses would be $2. Example 3: All trips have the same fare, transfers allowedSuppose Demo Transit Agency has the following fare structure:
Since all trips have the same fare, Demo Transit can omit fare_rules.txt. fare_attributes.txt
Calculating an adult fareThe trip planner calculates a fare of $1 for each leg of the itinerary that includes a change of vehicle. Then it calculates the time for the itinerary. If the itinerary time is less than 90 minutes, the fare is $1. Example 4: Different pricing for local and express routesSuppose Demo Transit Agency has the following fare structure:
Since some trips cost more than others, Demo Transit must include fare_rules.txt, and each route must have an entry to associate it with a fare. fare_attributes.txt
fare_rules.txt
Calculating an adult fareThe $5.00 fare is only applicable if you ride routes 2 or 3. The $1.75 fare only applies on route 1. If an itinerary uses routes 1 and 2, the fare is $6.75. Example 5: Buying a transfer increases the fareSuppose Demo Transit Agency has the following fare structure:
Since these rules apply to all trips, Demo Transit can omit fare_rules.txt. fare_attributes.txt
Calculating an adult fareTechnically, both fares apply on itinerary that has no transfers. However, the trip planner always chooses the least expensive applicable fare:
Example 6: Fare depends on station pairs, how you get there doesn't matterIn this example only the entry and exit points from the system matter. To define this fare structure for the feed, each station must have its own unique zone ID defined in stops.txt. Each station is considered a single zone.
fare_attributes.txt
fare_rules.txt
Calculating an adult fareThe trip planner calculates an itinerary, and then looks up the fare rules until it finds a matching origin/destination station pair. The public feed from SF Bay Area BART provides a real-world illustration of this type of fare structure. Example 7: Fare depends on zonesSuppose Demo Transit Agency has a concentric three-zone system, where fares depend on which zones a rider passes through during an itinerary. To define this fare structure for the feed, fare_attributes.txt and fare_rules.txt must contain a line for each possible combination of zones. For very complex cross-zone fare structures, it may be simpler to programmatically output fare_rules.txt using origin and destination to define fares. fare_attributes.txt
fare_rules.txt
Calculating an adult fareLet's look more closely at the definitions in fare_rules.txt.
The trip planner calculates an itinerary, and then looks up the fare rules to determine the fares that apply based on zone. Since F1 also includes travel in zone 1, only F4 ($2.95) applies to a trip from zone 2 to zone 3. A fare rule only applies when the set of zones passed through in an itinerary exactly matches the set specified by the fare rule. For a trip between zones 2 and 3, the trip planner reports $2.95 as the adult fare. The public feed from Portland TriMet provides a real-world illustration of this type of fare structure. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
► Sign in to add a comment
Hi I'm wondering if anyone has advise for the following transit structure: We have 2 bus types, express and regular. Regular cost 2$ and express cost 2.50. If you get on an express then move to a regular, the cost is 2.50 total because you can get a transfer. If you go from a regular to an express however, you must pay the extra 50 cents, for a total trip cost of 2.50. Any suggestions on how to code this?
If your system has multiple fare structures i.e. Full fare $1.50, all day $3.00, elderly and handicapped $.50 ect... How would you set up the codes, or is it possible? I'm thinking it would be easier to just leave out the fares and to just explain the fare structure on the website. Thanks.
Is it possible to specify that a fare applies only for a particular route on travel between two zones by including the route_id, origin_id, and destination_id fields?
Can one record include the route_id and contains_id fields? What happens?
Can one record include the contains_id, origin_id, and destination_id fields? What happens?
Yes, we have a situation similar to tristan (first comment). We have a shuttle route that is $.75 but regular fare is $1.50. They can transfer to a regular route within 2 hours but have to pay the additional $.75 Is there a way to show this?
For train service in between point a and b they got a station in between. the formaula of fare and pax boarding train at different station to a different station. the fomulau above show only for a journey of point a to b & transit.