MobilityData/GTFS_Schedule_Best-Practices

Issues

• Update Best Practices with additional transfer types

  #51 opened 8 months ago by isabelle-dr
  1

• Proposed Best Practice: Update practice for publishing future service

  #48 opened 8 months ago by e-lo
  15

• Best Practice and spec alignment

  #45 opened 8 months ago by scmcca
  8

• Proposed Need: Articulating "redirects" from merged feeds

  #43 opened 8 months ago by e-lo
  1

• Versioning cadence

  #41 opened 8 months ago by scmcca
  5

• Proposed best practice: `shapes.txt` should be included

  #37 opened 8 months ago by e-lo
  5

• Proposed best practice: Include tts_stop_name when stop name is potentially unintelligible using TTS technology

  #34 opened 8 months ago by e-lo
  2

• Reliable wheelchair accessibility

  #32 opened 8 months ago by e-lo
  3

• calendar.txt and stop_id as stop_code

  #7 opened 8 months ago by RideSchedules
  1

• Should stop locations be required to be unique?

  #6 opened 8 months ago by antrim
  2

• Also reference in-seat (block) transfers recommendation under trips.txt?

  #4 opened 8 months ago by antrim
  1

• Remove best practices now merged into the spec

  #57 opened a year ago by emmambd
  2

• [Formatting] Consolidate Best Practices into single legible document

  #46 opened 3 years ago by scmcca
  0

• Versioning

  #35 opened 3 years ago by scmcca
  0

• FAQ and publishing recommendations pages have not been removed

  #18 opened 4 years ago by lionel-nj
  0

• Revert to original introduction.md text

  #16 opened 4 years ago by lionel-nj
  0

• Update content: add examples from Transit Partners

  #20 opened 4 years ago by lionel-nj
  0

• Prepare .md files to be fetched: add metadata

  #23 opened 4 years ago by lionel-nj
  0

• Change the gtfs@rmi.org to a MobilityData email

  #25 opened 4 years ago by antrim
  0