Include Slow Zone data

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
data, frontend

Research direction

Start by locating the shutdown details page and its existing top-level metrics. Trace how shutdown data is loaded, then determine how to represent slow-zone counts, affected stops, added time, and post-shutdown changes; done means all requested slow-zone values and changes appear on each details page.

Written by the indexing model from the issue text.

Description

feature frontend

We should include slow zone data in the details page for each shutdown as a top-level metric:

  1. How many slow zones are there
  2. What stops are they between?
  3. How much time are they adding?

After shutdown:

  1. Show change in number to slow zones
  2. Show the change in time added due to slow zones
Dominant language
TypeScript
Stars
6
Forks
3
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from transitmatters/shutdown-tracker

All issues in transitmatters/shutdown-tracker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.