osplanning-data-standards/GTFS-PLUS

Issues

• Costs

  #6 opened 9 years ago by lmz
  4

• Same handling for bikes & wheelchairs in vehicles_ft?

  #54 opened 6 years ago by ddorinson
  2

• Add example script for reading in via Partridge

  #56 opened 6 years ago by e-lo
  0

• Add example network

  #55 opened 6 years ago by e-lo
  0

• max_speed occurs twice in vehicles_ft.md

  #44 opened 7 years ago by lmz
  2

• Be more explicit about what dwell time method is used

  #45 opened 7 years ago by e-lo
  0

• Dwell formula, acceleration, deceleration specification in vehicles_ft.txt

  #40 opened 7 years ago by lmz
  4

• Route type/mode dwell interaction coeffs

  #43 opened 7 years ago by sdrewc
  2

• Update `fares.md` to reflect current network specification

  #25 opened 8 years ago by e-lo
  0

• In README, add link to Technical Memo Documentation for v0.3.0 when static file is available

  #38 opened 8 years ago by ddorinson
  0

• including PNRs in transfers.txt causes the GTFS validator to fail

  #37 opened 8 years ago by e-lo
  0

• `walk_access_ft` should have have direction field like `drive_access_ft`

  #35 opened 8 years ago by sdrewc
  1

• transfers spec mentions PNR/KNR

  #7 opened 8 years ago by lmz
  3

• stops_ft and stop_times_ft

  #17 opened 8 years ago by sdrewc
  3

• Calendar.txt should also have start_date and end_date as required fields

  #18 opened 8 years ago by sdrewc
  0

• elevation_gain in walk_access_ft but what about egress?

  #20 opened 8 years ago by lmz
  6

• Rename `fare_class` to `fare_period`

  #23 opened 8 years ago by e-lo
  5

• Fare rules assumptions

  #28 opened 8 years ago by lmz
  2

• Clarify KNR / PNR Permissions in drive_access_points_ft.txt

  #32 opened 8 years ago by e-lo
  0

• Add doc about empty fare_attributes(_ft) transfers field

  #29 opened 8 years ago by lmz
  0

• start_time and end_times - Don't include end_time in time period

  #30 opened 8 years ago by lmz
  0

• Update fare_transfer_rules columns

  #31 opened 8 years ago by lmz
  21

• TAZ locations for access/egress visualization

  #4 opened 8 years ago by lmz
  1

• drive_access_ft and drive_access_points_ft clarification

  #21 opened 8 years ago by lmz
  0

• Update `fare_rules_ft` description of `fare_class`

  #24 opened 8 years ago by e-lo
  0

• Should drive access attributes include monetary costs?

  #26 opened 8 years ago by lmz
  1

• routes_ft -- can we add express_bus as a valid mode entry?

  #19 opened 8 years ago by sdrewc
  1

• Update for removal of fare_class from routes_ft

  #22 opened 8 years ago by lmz
  1

• Relation between lot_id and stop_id

  #14 opened 9 years ago by bhargavasana
  5

• null columns in transfers_ft.txt

  #15 opened 9 years ago by bhargavasana
  3

• How optional is drive_access_points_ft.txt ?

  #12 opened 9 years ago by bhargavasana
  1

• Column name change in drive_access_points_ft.txt

  #13 opened 9 years ago by bhargavasana
  1

• Clarify default value in transfers_ft for schedule_precedence variable

  #10 opened 9 years ago by e-lo
  0

• make transfers_ft.txt mandatory

  #11 opened 9 years ago by e-lo
  0

• Update fare_rules_ft.txt spec to be more clear about default times

  #9 opened 9 years ago by e-lo
  0

• Fare_class in routes_ft.txt is duplicative / conflicting

  #8 opened 9 years ago by e-lo
  0

• Consolidate pnr.txt and knr.txt

  #3 opened 9 years ago by lmz
  3

• PnR links in transfers_ft.txt

  #1 opened 9 years ago by dantischler
  8

• bike access/egress?

  #5 opened 9 years ago by lmz
  1

• add _ft to filenames that are not GTFS files.

  #2 opened 9 years ago by dantischler
  4