Route visibility

Every route in the Routes panel has a visibility toggle — the colour swatch. Click it to hide a route from the map. Hiding isn't an edit: the route stays in the feed and still exports. What it changes is the scope every analysis panel computes over — turn routes off and the Cost, Coverage, Title VI, and Stop analysis panels re-tabulate for just the routes still shown.

What it is

Service planning is comparative. You rarely ask "what does this network cost?" in isolation — you ask "what does coverage look like if I drop the two lowest-ridership routes?", or "how does the equity picture change for the rapid corridors only?". Route visibility lets you answer those questions without deleting anything: hide the routes you want to exclude, read the panels, then toggle them back on.

Hiding a route controls which routes are shown (and, by implication, which are excluded from analysis). Nothing is deleted — the hidden routes are still in the feed, still exportable, still one click from coming back. When no routes are hidden, every panel computes over the full feed unchanged.

Hiding and showing routes

Route visibility is controlled from the Routes panel, where each route row has a colour swatch on the left:

1. Open the Routes panel in the left sidebar.
2. Click a route's colour swatch to hide it from the map. The swatch hollows out to show the route is hidden; click it again to bring the route back.
3. Repeat until the map shows exactly the subset of the network you want to analyse.

The eye icon at the top of the list marks the swatch column as the map-visibility toggle. Hiding is per-route and lives only in your current view — it isn't saved with the feed and resets to "all routes visible" when you reopen a feed.

To explore a service change (not just which routes are shown) — say "what if we add a Saturday run on Route 5?" — use feed variants instead, which carry real, independent edits and a computed cost comparison against a baseline.

What re-scopes

Hiding routes changes the active set of visible routes, and everything downstream follows from that single source of truth:

• The map. Hidden routes — and the stops served only by hidden routes — drop out of view.
• Cost estimation. Revenue hours, peak vehicles, and weekly/annual cost are computed over the visible routes only.
• Demographic coverage. Population, households, and workers near service are measured against the visible network's stops.
• Title VI analysis. The equity comparison runs over the visible routes — useful for testing how a proposed cut shifts the burden across demographic groups.
• Stop analysis. Spacing, service intensity, and consolidation candidates reflect only the stops the visible routes serve.

The scoping cascades from routes through trips and stop times down to stops, so a stop served exclusively by a hidden route disappears from every panel — but a stop shared with a still-visible route stays. When no routes are hidden, the panels compute over the full feed unchanged.

Edge cases and gotchas

• Hiding a route doesn't change the exported feed. Hidden routes are still part of the feed and still export. To actually remove a route from a feed, delete it in the Routes panel; visibility is an analysis lens, not an editing operation.
• Visibility resets on reload. The set of hidden routes isn't saved with the feed — reopening a feed starts on "all routes visible".
• All routes hidden = nothing to analyse. If you hide every route, the analysis panels show an empty state prompting you to toggle a route back on.
• Want to keep and compare edited alternatives? Route visibility only shows or hides existing routes. To fork the feed into named, independently-editable alternatives and compare their cost, use feed variants.