Skip to content

Visualizing Scheduled Service

Eddy Ionescu edited this page Mar 9, 2019 · 3 revisions

Concept:

  • Homepage for OpenTransit:
    • Choose one or more agencies + map type {connectivity, reliability}, about us, [in the news], slides
  • reliability:
    • same as what's there now - note: agencies other than ttc/muni are greyed out; only one of ttc/muni can be chosen
  • connectivity:
    • kinda coupled to transit.land (as that's now running)
    • relies only on the gtfs files to draw the map (backend generates geojsons, one for each service period, which it gives to the client to draw)
    • service periods are based on the frequency during an hour of the day, as to show a representative map for all agencies.

Phase 1:

This phase involves generating a map for each service period based on GTFS files. It also includes selecting a past GTFS from the list. An overall system map will be part of phase 2.

Weekdays:

- AM peak: 8-9am
- Midday: 12pm-1pm
- PM peak: 4-5pm
- Early evening: 7-8pm
- Late evening: 10pm-11pm
- Overnight: 3am-4am

Saturdays and Sundays:

- Morning: 10-11am
- Afternoon: 2-3pm
- Early evening: 7-8pm
- late evening: 10pm-11pm
- overnight: 3am-4am
  • Standards for each period:
    • Bolded red: 10 minutes or better
    • Medium red: 20 minutes or better
    • thin red: 30 minutes or better
    • dotted red: all others

Phase 2: Generate an overall system map, categorizing routes into one or more of the following:

  1. All day every day (AM, PM, and midday, or morning+afternoon on weekends, every day of the week)
  2. Limited Daytime Service (anything not in #1 that has service in at least one daytime period)
  3. Evening Service (weeknight early or late evening, some agencies might have special routes for this)
  4. Overnight (includes every weeknight and optionally weekends)

Phase 3: Overlay demographic data

Clone this wiki locally