New-data corridor overview
A junction-only analysis of the Finch Avenue West monitoring area, calculated exclusively from the March–September 2026 exports.
Monitored corridor
Intersections are ordered west to east using coordinates derived from sampled 40-ft arrival points.
Current selection highlights
The strongest descriptive findings under the active filters.
Delay by intersection
Mean provider approach delay, in seconds.
Period comparison
Uses the selected dates, day group, intersection, approach and movement; compares all four periods.
Intersection performance
Compare all six intersections by local hour and switch among delay, travel time, stop rate, average speed and probe count.
Intersection performance ranking
Ranked by the selected heatmap metric under the current filters.
| Rank | Intersection | Probe count | Delay | 95% precision | Stop rate | Travel time | Average speed |
|---|
Time comparisons
Understand how the selected junction conditions change by Toronto local hour, operating period, month and day group.
Delay by time period
Period comparison ignores the global time-period/hour filters but respects the other selections.
Delay by day group
All-day comparison for the selected date range, intersection, approach and movement.
Monthly trend
Only months and dates available within the new source exports are shown.
Approaches and turning movements
Analyze eastbound, westbound, northbound and southbound approaches, then compare recognized through, left, right and U-turn movements.
Approach-direction comparison
Direction is derived from the provider approach name.
Movement comparison
Unknown/no-exit records are disclosed separately and excluded from the detailed recognized-movement table.
Detailed approach and movement performance
Each row is a recognized movement for one monitored approach under the active filters.
| Intersection | Approach | Direction | Movement | Probe count | Delay | Stop rate | Travel time | Average speed |
|---|
Route segment analysis
Explore the new Finch Avenue route-monitoring exports by travel direction, month, day group and operating period.
LowerHigher
Selection highlights
Operational findings for the selected route view.
Route travel time by hour
Mean end-to-end travel time in minutes, created by summing valid segment travel times for each observed date and hour.
Segment performance ranking
Ranked from greatest operational concern for the selected display metric. Posted-speed comparison is context only and is not a free-flow-delay calculation.
| Rank | Segment | Street | Length | Average speed | Speed % of limit | Travel time | TT variability | Provider samples |
|---|
Time series route analysis
Track end-to-end Finch Avenue travel time by exact date and any combination of Toronto local hours.
Exclude dates and times from this analysisAdd one or more exception windows. Matching date-hour observations are removed from the chart, summaries and daily table.
Select any Toronto local hours
How this chart is calculated: segment mean travel times are summed into an end-to-end route total for each date and hour. For Both directions, each date-hour value is (eastbound route time + westbound route time) ÷ 2. The daily line is the mean across the selected hours. The shaded band is the 5th–95th percentile of those selected hourly route totals; it is not an individual-trip percentile.
Selected-hour 5th–95th percentileDaily meanRolling trendReference
Monthly comparison
Mean of the filtered daily route values.
Interpretation
Descriptive findings under the active calendar, day and hour selections.
Daily values
Auditable daily results behind the chart. Missing source dates are not generated or interpolated.
| Date | Day | Selected hours | Mean route time | 5th percentile | 95th percentile | Corridor speed | Mean segment coverage | Provider samples |
|---|
Data quality and method
Transparent coverage, source-file dates, metric definitions and limitations for the new junction dataset.
Source isolation: this application reads only
1_Data\New_data_Junction_March_Sep_2026. No previous junction records are merged into the calculations.Interpretation: probe count is sample activity, not calibrated traffic volume. The results are descriptive provider-data measures and are not an HCM capacity or Level-of-Service analysis.
Field availability
Metric definitions
Approach delayProvider approach_delay ÷ 1,000Mean of valid records, reported in seconds.
Stop ratehas_stops=true ÷ selected probesPercentage of selected observations containing a stop.
Travel timeProvider travel_time ÷ 1,000Mean time represented by each junction observation.
95% precision1.96 × sample SD ÷ √nSampling precision around the mean; not overall data accuracy.
Raw-record integrity checks
Independent streaming checks performed across every source row before publication.
Source-file audit
Dates below come from record timestamps in Toronto local time, not from filenames. Exact duplicate rows are excluded from every analytical result.
| Source file | Raw rows | Analyzed rows | Duplicates | First local date | Last local date | Bad rows | Bad timestamps |
|---|