Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

networks.txt and route_networks.txt update #247

Merged
merged 2 commits into from
Dec 15, 2023
Merged

networks.txt and route_networks.txt update #247

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
88cc5e2
Add networks.network_id as foreign ID
tzujenchanmbd Dec 5, 2023
2501221
Add networks files for Hudson Line example
tzujenchanmbd Dec 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions docs/schedule/examples/fares-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,7 +283,7 @@ For this example, based on WMATA fares, the fare depends only on the leg's depar
| 1 | peak_fare | weekday_peak | |
| 1 | regular_fare | weekday_offpeak | |

Note that `network_id` references the foreign ID `routes.network_id`, and that the selection of the correct fare product for each trip will be a combination of arrival and departure times from `stop_times.txt` along with the times defined in `timeframes.txt`.
Note that `network_id` references the foreign ID `networks.network_id` or `routes.network_id`, and that the selection of the correct fare product for each trip will be a combination of arrival and departure times from `stop_times.txt` along with the times defined in `timeframes.txt`.

In this case, a user paying for a trip that departs at 7:30 AM would have to pay 5.00 USD (Peak fare) while another user departing at 11:30 AM would only have to pay a 3.00 USD fare (Off-peak fare).

Expand All @@ -310,7 +310,7 @@ This example is based on a <a href="https://docs.google.com/spreadsheets/d/1-cD-
| ITO2383 | Grand Central | 40.752823 | -73.977196 |


[**stops_areas.txt**](../../reference/#stops_areastxt)
[**stop_areas.txt**](../../reference/#stop_areastxt)

| area_id | stop_id |
|-----------|---------|
Expand All @@ -326,6 +326,19 @@ This example is based on a <a href="https://docs.google.com/spreadsheets/d/1-cD-
| mnr_HUD-9 | ITO2096 |


[**route_networks.txt**](../../reference/#route_networkstxt)

| network_id | route_id |
|------------|----------|
| mnr_hudson | 669 |


[**networks.txt**](../../reference/#networkstxt)

| network_id | network_name |
|------------|-----------------|
| mnr_hudson | MNR Hudson Line |

Service days for train services 3 and 13 are defined using `calendar.txt`. Notably, other records with generic days (i.e. weekdays, weekends, and anyday) that aren't associated with any trips are defined, and these will be associated with timeframes in order to model `time-variable fares`.

[**calendar.txt**](../../reference/#calendartxt)
Expand Down