跳到主要内容

服务

报告问题

此页面不是关于某个站点、线路、车站或车辆的。请打开其中一个，让报告写明它，或者使用完整报告。

发生了什么
完整报告 无需账户

Ward 21 · Ottawa · Councillor: David Brown

Rideau-Jock

为本选区采取行动

Rideau-Jock: 60.3% of predictions within five minutes.

Partial data · 2 days partly captured
五分钟内
60.3%
选区内的站点
160
途经的路线
8
已取消的班次
尚未提供
尚未按选区统计

最慢的地方

  • 80% 及以上 1
  • 60 至 80% 1
  • 低于 60% 0
  • 数据太少 6

途经该选区的线路,按预测误差在五分钟内的占比排列。每条线路的结果涵盖整条线路。

本选区内的线路

此选区内的线路，按可靠性从低到高排列
线路5 分钟内已取消拥挤程度
11071.6%未公布未公布
16882.7%未公布未公布

Cancellations and crowding are not published per route yet. 6 routes with too little data or a different service purpose are left out.

所有线路及其来源

一页简报

本选区的可打印摘要，供市议会和社区会议使用。内容包括相同的数字、通俗易懂的方法说明和注明日期的来源。

打开简报与另一个选区比较

What can be verified in Rideau-Jock?

包括到站预测、已导入的时刻表和列车通知。每项都会显示各自的来源。

提供方预测一致性

60.3%

的合格预测与时刻表相差不超过五分钟

对比情况
Rank 22 of 22 · median 78.4%

服务情况,依据已导入的时刻表

辖区站点的预定行程
尚未提供
线路
8
铁路线路
0

此边界内的当前服务

打开实时地图

此边界内的实时公交车在“地图”标签页上。

预测指标、时刻表清单和方法

服务运行情况 · 证据状态

2026年10月28日 – 2026年11月3日

本选区站点的取消次数

Not publishable

No zero or missed trip is inferred when exact stop calls cannot be published.

本选区内站点的预测

60.3% within five minutes of the timetable across 4,768 eligible final provider predictions and 20 weekdays. These are not verified physical arrivals.

Predictions do not prove physical arrival.

需要检查的路线

2026年10月28日 – 2026年11月3日

如有,这些是为该选区服务的线路的全线车辆位置匹配结果。它们不能确定漏掉的行程是否在此选区内,也不能证明行程已取消。每次比较都使用同一线路和同一时段的预定行程。

Scheduled calls, sources and limits

8 routes · 160 stops. 这是时刻表清单，不是已提供的行程。

本选区站点的取消次数

Local count cannot be published

Exact stop-call evidence could not be read for 2026年10月28日 – 2026年11月3日. No zero is assumed.

Dates, source versions and limits

Method: retained-pre-service-exact-trip-stop-call-v1. Cancellation-feed completeness and position coverage are unverified.

The retained timetables were fetched, imported and first activated before the service day. The archive does not prove they remained the active timetables throughout that period. Comparisons between places remain unavailable.

    结论

    What would fix transit here

    Worked out from the routes that serve this ward. Each item names the route, when it happens, and what would change it.

    2 of 2 show repeated provider predictions later than the timetable, consistent with a possible scheduled running-time shortfall. A scheduler should test that scenario against operations; labour, fleet, recovery and transfer impacts are not established here.

    Worst here: route 110, predictions later than timetable 15:00 to 18:00, 3.8 min late.

    Best here: route 168, observed-position lower bound, 100%.

    2 of 2 routes here had something measurable to report.

    Arrivals within five minutes, by hour of day, across the 2 routes graded here, last 14 days
    1. 00:00: 88.5% of final predictions within five minutes of the timetable, 871 predictions, typically 0.5 min late
    2. 01:00: not enough data
    3. 02:00: not enough data
    4. 03:00: not enough data
    5. 04:00: 79.4% of final predictions within five minutes of the timetable, 462 predictions, typically 2.8 min late
    6. 05:00: 76.5% of final predictions within five minutes of the timetable, 4,686 predictions, typically 1.2 min late
    7. 06:00: 89.2% of final predictions within five minutes of the timetable, 6,640 predictions, typically 0.4 min late
    8. 07:00: 84.5% of final predictions within five minutes of the timetable, 7,406 predictions, typically 1.4 min late
    9. 08:00: 75.8% of final predictions within five minutes of the timetable, 6,828 predictions, typically 2 min late
    10. 09:00: 79.2% of final predictions within five minutes of the timetable, 7,376 predictions, typically 1.8 min late
    11. 10:00: 82% of final predictions within five minutes of the timetable, 7,263 predictions, typically 1 min late
    12. 11:00: 78.7% of final predictions within five minutes of the timetable, 7,068 predictions, typically 1.6 min late
    13. 12:00: 78.4% of final predictions within five minutes of the timetable, 7,134 predictions, typically 1.6 min late
    14. 13:00: 79.2% of final predictions within five minutes of the timetable, 7,114 predictions, typically 2 min late
    15. 14:00: 82.2% of final predictions within five minutes of the timetable, 6,799 predictions, typically 0.9 min late
    16. 15:00: 70.3% of final predictions within five minutes of the timetable, 6,162 predictions, typically 2.7 min late
    17. 16:00: 63.2% of final predictions within five minutes of the timetable, 6,883 predictions, typically 3.2 min late
    18. 17:00: 56.8% of final predictions within five minutes of the timetable, 7,887 predictions, typically 3.6 min late
    19. 18:00: 64.5% of final predictions within five minutes of the timetable, 8,273 predictions, typically 2.6 min late
    20. 19:00: 82.3% of final predictions within five minutes of the timetable, 7,616 predictions, typically 1.4 min late
    21. 20:00: 80.7% of final predictions within five minutes of the timetable, 6,790 predictions, typically 1.4 min late
    22. 21:00: 82.5% of final predictions within five minutes of the timetable, 3,742 predictions, typically 0.9 min late
    23. 22:00: 87.2% of final predictions within five minutes of the timetable, 1,929 predictions, typically 0.8 min late
    24. 23:00: 94.1% of final predictions within five minutes of the timetable, 1,461 predictions, typically 0.7 min late
    • 90% or more of predictions within five minutes
    • 80 to 90% of predictions within five minutes
    • under 80% of predictions within five minutes
    • not enough data
    Findings
    What时间已测量Scenario or next investigation
    ProblemPredictions later than timetable1101682 routes15:00 to 18:00 · 17:003.8 min late · 4.3 min lateMore running time
    ProblemOne hour has a lower prediction match1681 routes17:0056%Operations, not the timetable
    ProblemPredictions earlier than timetable1101 routes21:001.6 min earlyLess running time, or holding points
    StrengthObserved-position lower bound1681 routesAll measured hours100%Keep what works
    CaveatCoverage gap1101 routesAll measured hours99%More observation, not a service change

    How RIDEAU-JOCK is doing

    这些指标把反复出现的延误与运营方到达预测的波动区分开来。它们可为规划人员和运营人员提供可探讨的问题，但不能确定原因，也不能证明公共汽车何时到达。每个数字都显示其线路时段样本。

    Measured over 38 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.

    排班

    如果多次出现预测晚点，可能说明时刻表值得检查。在决定是否调整运行时间之前，请先查看实际到达和发车记录。

    谁能解决
    服务规划人员
    费用
    在车队、人力、恢复和换乘的影响测试完成之前，成本暂不可知。

    与时刻表接近的预测

    86.8%

    线路小时中，符合条件的到站预测中位数早于实际不到一分钟，且晚于实际不到三分钟。

    多次预计晚点的线路时段

    4of 38

    路线小时数：符合条件的到达预测中位数至少晚点三分钟。请对照实际运营记录检查运行时间。

    有提前预测的线路小时数

    1of 38

    线路-小时中，符合条件的到站预测中位数至少提前一分钟的部分。这并不能证明公交车提前发车。

    典型预测延误

    3.8min

    在被标记的线路时段中，预测延误的典型中位数。这不是可直接加到时刻表上的经过验证的数值。

    运营

    到站预测差异很大，需要进行运营审查。交通状况、调度、上车和时刻表设计都可能有影响。仅凭这些预测，无法确定原因或解决办法。

    谁能解决
    运营部门，通常还有道路本身
    费用
    在查明运营原因并确定补救办法之前，费用暂不可用。

    预测间隔低于二十分钟

    100%

    第95百分位的合格预测值比中位数晚不到二十分钟的线路-小时。

    预测误差大的线路时段

    0of 38

    第95百分位的合格预测比中位数晚至少二十分钟的线路时段。需要调查原因。

    典型预测偏差

    本月数据不足，无法发布此指标。

    在被标记的线路时段中,第 95 百分位符合条件的预计值与中位数之间的典型差距。

    服务情况,依据已导入的时刻表

    本选区的按时刻表公共交通、服务商预测与时刻表的一致程度,以及公共服务。

    8
    线路
    160
    站点
    12
    洗手间
    3
    饮水点
    运营方预测指标60.3%运营方预测与时刻表相差五分钟以内

    提供方预测一致性

    60.3% of eligible provider predictions were within five minutes of the timetable. 2,874 of 4,768 settled trip-stop predictions at stops inside this ward matched that range across 20 weekdays with feed evidence, from 2026年10月3日 to 2026年11月3日. These are provider predictions, not independently observed arrivals.

    2 partial-capture days not counted.

    五分钟内的预测
    2,874
    符合条件的班次站点预测
    4,768
    已观察天数
    20 weekdays

    对比情况

    Ranked 22 of 22 measured wards. 18.1 points below the city median of 78.4%.

    Highest: ward 22 at 85.1%. Lowest: ward 21 at 60.3%.

    只有数据达到发布标准的选区才会参与排名。每个选区使用相同的时间范围和相同的方法。

    哪些线路需要进一步审查

    2 of the 8 routes serving this ward have enough provider-prediction evidence to compare. Lowest timetable agreement first.

    1. 110Open route
      71.6%五分钟内的预测

      113,377 eligible predictions across the whole route

    2. 168Open route
      82.7%五分钟内的预测

      110,481 eligible predictions across the whole route

    6 more routes here are not ranked: school, express, shopper or event service, whose schedule result does not compare the same way.

    需要调查的车辆可见性

    需要调查的车辆可见性

    当前摘要使用七天的数据。对于每条路线，您也可以打开昨天、最近 7 天或最近 30 天的数据，查看日期、预定班次、被排除的数据缺口，以及每个观察到的公共车辆编号。没有记录不能证明车辆故障，也不能证明是运营方的决定。

    需要调查的车辆可见性
    线路时刻表班次有位置没有匹配的位置覆盖范围历史
    30121150.0%
    2995049198.0%
    110346341598.6%
    168476474299.6%
    28335350100.0%
    27935350100.0%
    26335350100.0%
    305220100.0%

    服务该选区的线路

    8 scheduled routes

    Bus routes · 8

    Train lines · 0

    在已导入的时刻表中，没有任何轨道线路在本选区设有车站。

    Map & current service

    Current service inside this boundary

    Scheduled lines, stops, and observed buses share one map. Select a route or vehicle for details.

    Evidence & sources

    Imported municipal polygon · 153 boundary vertices · City of Ottawa ward boundaries · imported 2026年8月4日

    ━ 8 bus routes● 160 stops
    Loading live feed

    Public amenity record for this ward

    公共洗手间和饮用水

    Choose a category to check which location details are available.
    公共洗手间（市政数据） 12

    公开的选区快照只发布了该选区的数量,没有发布各个具体地点。我们没有编造任何地点。

    饮用水（市政府数据） 3

    公开的选区快照只发布了该选区的数量,没有发布各个具体地点。我们没有编造任何地点。

    评价或报告问题

    Rider evidence

    Community reports

    Signals below are moderated community aggregates, not official operator notices or reliability scores.

    You can report without signing in. Anonymous reports count a little less when we calculate public patterns. You can add an account after submitting.

    Report a specific problem

    Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.

    公共事务数据简报

    本选区报告背后的身份信息、边界、联系方式、服务范围和数据日期,汇集在一起,方便引用本页时不丢失相关说明。

    市
    安大略省渥太华市
    地理单位
    Official City of Ottawa municipal ward 21: RIDEAU-JOCK
    边界和版本时间
    City ward layer · effective 未公布 · imported 2026年8月4日
    官方市政联系方式
    相关的预定服务
    8 public route records with a stop inside this boundary · operators: OC Transpo
    公交数据的年份
    Timetable import: 未公布 · reliability window: 2026年10月3日 – 2026年11月3日

    选区边界、线路清单、目的地列表、人口数量或就业人数只能提供城市背景。这些数值单独都无法衡量乘客需求、家庭出行影响、换乘或每日到访人数。

    渥太华的选区是市政选区。它们不是加蒂诺的选区。两种边界体系的结果不能互换。

    本页的佐证数据打开定义、方法、来源、日期、覆盖范围和已知限制。

    这里显示的内容

    按选区列出的清单，包括预定的公交服务、公共洗手间、饮水点，以及选区内站点符合条件的 OC Transpo 最终运营方预测。

    How it was produced

    Current imported records are assigned by point-in-polygon to the sourced ward boundary. Reliability uses one eligible final provider prediction per trip, stop, and service date in the latest 28 completed service days. Within five minutes is measured against the timetable, not a physical arrival. Publication requires 20 weekdays with prediction evidence and 500 eligible predictions.

    数据日期

    已导入
    计算或汇总时间
    样本
    4,768 eligible settled provider predictions across 20 weekdays with prediction evidence support the reliability result.
    方法或数据版本
    ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
    来源校验和
    ward-reliability:cbcc59f93fa16c515ebdbe11b1cb3fcf802e1f4dc81bad5daab2b4e980728f69

    来源

    请注意的局限

    • 数量只反映边界内已发布的设施清单，不代表服务质量，也不代表每个地址都能使用。
    • 可靠性涵盖 OC Transpo 提供方在按地理位置划分的站点给出的最终预测。实际到达情况没有被独立测量。轨道交通以及没有合格预测数据的行程不包含在内。
    • 无法获得的数量会保持为无法获得。不会改成零。
    提出事实更正建议
    我们如何测量

    对于选区内各站点的每个班次、站点和服务日期，我们保留 OC Transpo 最后一条符合条件的预测，并与时刻表对比。两者相差不超过五分钟时，计为五分钟以内。这不代表实际到达。

    统计时段为最近 28 个已完成的运营日。只有在有 20 个工作日的预测数据和 500 条合格预测时，才会公布结果。路线结果涵盖整条路线，而不只是选区内的部分。

    Read the full method

    Contains information licensed under the Open Government Licence – City of Ottawa.