Ward 13 · Ottawa · Councillor: Rawlson King
Rideau-Rockcliffe
Rideau-Rockcliffe: 66.3% of predictions within five minutes.
- 五分鐘內
- 66.3%
- 選區內的站點
- 209
- 行經的路線
- 27
- 已取消的班次
- 暫時未有資料
- 尚未按選區計算
最慢的地方
- 80%及以上 4
- 60 至 80% 12
- 低於 60% 2
- 資料太少 8
服務該選區的路線，依五分鐘內預測的比例排列。每條路線的結果涵蓋整條路線。
此選區內的路線
| 路線 | 5 分鐘內 | 已取消 | 擁擠程度 |
|---|---|---|---|
| 23 | 42.8% | 未公布 | 未公布 |
| 17 | 47.3% | 未公布 | 未公布 |
| 7 | 63.2% | 未公布 | 未公布 |
| 12 | 63.9% | 未公布 | 未公布 |
| 19 | 64.2% | 未公布 | 未公布 |
| 20 | 65.1% | 未公布 | 未公布 |
| 18 | 65.8% | 未公布 | 未公布 |
| 15 | 67.1% | 未公布 | 未公布 |
Cancellations and crowding are not published per route yet. 8 routes with too little data or a different service purpose are left out.
所有路線及其來源一頁簡介
這個選區的可列印摘要，供市議會和社區會議使用。內容包含相同的數字、用簡單文字說明的方法，以及註明日期的來源。
What can be verified in Rideau-Rockcliffe?
到站預測、匯入的時刻表和列車通知。每項都會標示各自的來源。
供應商預測一致程度
66.3%
合格預測中，與時刻表相差五分鐘內的比例
- 比較情況
- Rank 20 of 22 · median 78.4%
服務,依已匯入的時刻表
- 選區站點的預定班次
- 暫時未有資料
- 路線
- 26
- 鐵路線
- 1
此範圍內目前的服務
此範圍內的即時公車在「地圖」分頁。
預測衡量方式、時刻表清單與方法
服務提供情況 · 證據狀態
此選區內站點的取消班次
Not publishableNo zero or missed trip is inferred when exact stop calls cannot be published.
選區內各站的預測
66.3% within five minutes of the timetable across 304,271 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
27 routes · 209 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.
17 of 18 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 12, predictions later than timetable 09:00 to 21:00, 4 min late.
Best here: route 40, observed-position lower bound, 100%.
18 of 18 routes here had something measurable to report.
- 00:00: 83.5% of final predictions within five minutes of the timetable, 18,381 predictions, typically 1.5 min late
- 01:00: 86.6% of final predictions within five minutes of the timetable, 9,168 predictions, typically 1.1 min late
- 02:00: 86.9% of final predictions within five minutes of the timetable, 3,904 predictions, typically 0.8 min late
- 03:00: 84.3% of final predictions within five minutes of the timetable, 3,166 predictions, typically 0.9 min late
- 04:00: 86.5% of final predictions within five minutes of the timetable, 7,890 predictions, typically 1.3 min late
- 05:00: 92.5% of final predictions within five minutes of the timetable, 17,600 predictions, typically 1 min late
- 06:00: 85.5% of final predictions within five minutes of the timetable, 39,294 predictions, typically 1.6 min late
- 07:00: 79.4% of final predictions within five minutes of the timetable, 50,560 predictions, typically 1.9 min late
- 08:00: 68.9% of final predictions within five minutes of the timetable, 56,340 predictions, typically 2.8 min late
- 09:00: 72.5% of final predictions within five minutes of the timetable, 55,732 predictions, typically 2.3 min late
- 10:00: 77.1% of final predictions within five minutes of the timetable, 53,987 predictions, typically 2.1 min late
- 11:00: 75% of final predictions within five minutes of the timetable, 53,474 predictions, typically 2.3 min late
- 12:00: 67.8% of final predictions within five minutes of the timetable, 53,848 predictions, typically 3 min late
- 13:00: 69.7% of final predictions within five minutes of the timetable, 53,996 predictions, typically 2.7 min late
- 14:00: 68.6% of final predictions within five minutes of the timetable, 51,857 predictions, typically 2.7 min late
- 15:00: 60.7% of final predictions within five minutes of the timetable, 52,771 predictions, typically 3.6 min late
- 16:00: 53.8% of final predictions within five minutes of the timetable, 56,037 predictions, typically 4.6 min late
- 17:00: 55.9% of final predictions within five minutes of the timetable, 60,366 predictions, typically 4.1 min late
- 18:00: 62.8% of final predictions within five minutes of the timetable, 56,516 predictions, typically 3.4 min late
- 19:00: 69.9% of final predictions within five minutes of the timetable, 45,653 predictions, typically 2.7 min late
- 20:00: 76.2% of final predictions within five minutes of the timetable, 41,287 predictions, typically 2.2 min late
- 21:00: 75.1% of final predictions within five minutes of the timetable, 37,821 predictions, typically 2.4 min late
- 22:00: 78% of final predictions within five minutes of the timetable, 34,063 predictions, typically 2.2 min late
- 23:00: 80.3% of final predictions within five minutes of the timetable, 28,147 predictions, typically 1.9 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
| What | 時間 | 已測量 | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable127624182014192515917413940472317 routes | 09:00 to 21:00 … 04:00 | 4 min late … 3.2 min late | More running time |
| ProblemWide prediction spread202419152310567 routes | 16:00 to 18:00 … 02:00 | 28.2 min swing … 37.9 min swing | Operations, not the timetable |
| ProblemOne hour has a lower prediction match6241225141820414019915171054715 routes | 17:00 … 06:00 | 46% … 65% | Operations, not the timetable |
| ProblemPredictions earlier than timetable23472 routes | 17:00 · 12:00 | 5.9 min early · 1.1 min early | Less running time, or holding points |
| StrengthObserved-position lower bound40181947235 routes | All measured hours | 100% | Keep what works |
| CaveatCoverage gap39105714126411525249201713 routes | All measured hours | 98% … 99% | More observation, not a service change |
O-Train 數據
我們對此處列車服務的了解
公開資料饋送中沒有列車
巴士準點報告是將已存檔的到站預測與已發布的時刻表相比較。報告並未計算獨立測得的實際到站情況。Otranspo 沒有可用於這些報告的同類公開列車位置資料集，因此這些巴士數據無法顯示列車在哪裡，也無法顯示 1、2 和 4 號線是否準點。
公開列車位置、時間戳記和量測方法，有助於建立另一份可查證的鐵路服務紀錄。缺少這項資料，無法確定列車的實際表現。
近期共享的列車觀察
這些是經審核員批准的乘客目擊紀錄。內容顯示所回報的時間和地點。這不是官方列車位置，也不是完整的列車數量，更不能證明成因。
過去 31 天內,沒有符合此地點或路線的已核准乘客觀察紀錄。這不代表沒有列車行駛,也不代表沒有發生問題。
How RIDEAU-ROCKCLIFFE is doing
這些指標可區分重複出現的延誤,以及營運單位到站預測的變動。它們可為規劃人員和營運人員提供問題方向,但不能確定原因,也不能證明公車實際何時到達。每項數字都會顯示其路線時段的樣本數。
Measured over 336 route-hours. 3 more were observed too thinly to count, and are excluded rather than assumed good.
排班
預測一再延遲，可能表示這個時刻表值得檢討。在決定是否要調整行駛時間之前，請先查核實際到達和發車的記錄。
- 誰能解決
- 服務規劃人員
- 費用
- 在車輛、人力、回收和轉乘影響經過測試前，成本無法提供。
與時刻表接近的預測
68.8%
路線時段中，符合資格的到站預測中位數，早到不足一分鐘，且晚到不足三分鐘。
多次預測late的路線時段
103of 336
符合條件的到站預測中位數至少晚三分鐘的路線時段。請對照實際營運記錄，檢視行車時間。
有提早預測的路線時數
2of 336
路線小時數中，符合條件的到站預測中位數至少提早一分鐘。這不能證明巴士提早發車。
一般預測延誤
3.8min
被標記路線時段中預測延誤的典型中位數;這不是可加到時刻表上的已驗證數值。
營運
到站預測差異很大，需要進行營運檢討。交通、調度、上下車和時刻表設計都可能有影響。光靠這些預測，無法找出原因或解決辦法。
- 誰能解決
- 營運部門，通常也包括道路本身
- 費用
- 在確定營運原因和補救方法之前,無法提供費用。
預測間隔不足二十分鐘
97.3%
第95百分位的合格預測，比中位數晚不到二十分鐘的路線時段。
預測落差大的路線時段
9of 336
第95百分位的合格預測時間比中位數晚至少二十分鐘的路線時段。需要調查原因。
一般預測差距
25.1min
在被標記的路線時段中，第 95 百分位的合格預測與中位數之間的一般差距。
服務,依已匯入的時刻表
此選區內的預定公共運輸、供應商預測與時刻表的吻合程度，以及公共服務。
供應商預測一致程度
66.3% of eligible provider predictions were within five minutes of the timetable. 201,629 of 304,271 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.
- 五分鐘內的預測
- 201,629
- 符合條件的班次停靠站預測
- 304,271
- 已觀察天數
- 20 weekdays
比較情況
Ranked 20 of 22 measured wards. 12.1 points below the city median of 78.4%.
Highest: ward 22 at 85.1%. Lowest: ward 21 at 60.3%.
只有證據達到公布門檻的選區才會列入排名。每個選區都使用相同的時間範圍和相同的方法。
哪些路線需要進一步檢視
18 of the 26 routes serving this ward have enough provider-prediction evidence to compare. Lowest timetable agreement first.
- 23Open route 42.8%五分鐘內的預測
5,797 eligible predictions across the whole route
- 17Open route 47.3%五分鐘內的預測
7,876 eligible predictions across the whole route
- 7Open route 63.2%五分鐘內的預測
211,314 eligible predictions across the whole route
- 12Open route 63.9%五分鐘內的預測
205,036 eligible predictions across the whole route
- 19Open route 64.2%五分鐘內的預測
78,053 eligible predictions across the whole route
- 20Open route 65.1%五分鐘內的預測
89,859 eligible predictions across the whole route
- 18Open route 65.8%五分鐘內的預測
96,916 eligible predictions across the whole route
- 15Open route 67.1%五分鐘內的預測
29,259 eligible predictions across the whole route
- 14Open route 69.2%五分鐘內的預測
147,871 eligible predictions across the whole route
- 6Open route 69.4%五分鐘內的預測
191,599 eligible predictions across the whole route
8 more routes here are not ranked: school, express, shopper or event service, whose schedule result does not compare the same way.
需要調查的車輛可見度
需要調查的車輛可見度
目前的摘要使用七天的資料。每條路線您也可以開啟昨天、最近 7 天或最近 30 天,查看日期、預定行程、已排除的資料缺口,以及每一個觀測到的公開車輛編號。沒有出現並不能證明車輛故障或營運商的決定。
服務該選區的路線
27 scheduled routesMap & 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 · 35 boundary vertices · City of Ottawa ward boundaries · imported 2026年8月4日
Public amenity record for this ward
公共洗手間和飲水設施
Choose a category to check which location details are available.公共洗手間（市政府資料） 3
公開的選區快照只發布此選區的數量,沒有提供個別地點。我們沒有自行編造任何地點。
飲用水(市府資料) 4
公開的選區快照只發布此選區的數量,沒有提供個別地點。我們沒有自行編造任何地點。
Prepare an email for City Hall
Choose one current office or enter one other recipient, edit the neutral draft, then review it in your own email app.
Otranspo never sends this message and cannot see whether it was sent, received, or answered.
Send only to the relevant office. Avoid mass email, harassment, report receipts, account details, health information, phone numbers, or an exact personal location. Remove anything you do not want the recipient or email provider to retain.
If no email app opens, copy the draft below and paste it into the email service you choose.
Evidence included with the draft
- Canonical Otranspo evidence link
- https://otranspo.ca/zh-Hant/city/wards/13
- Sources and time
- Sources and time: open the linked report for its source records and published or imported timestamps.
- Limitations
- Limitations: Otranspo is independent and may show unknown, suppressed, delayed, or corrected values. Confirm urgent or current service matters with the official agency.
評分或回報問題
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
- Graffiti
- Cleanliness
- Lighting
- Snow or ice
- Washroom unavailable
- Water unavailable
- Accessibility barrier
- Other issue
Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.
公民數據簡報
這份選區報告背後的身分、邊界、聯絡方式、服務範圍和資料日期都集中在這裡,方便引用此頁時不會漏掉相關限制說明。
- 市鎮
- 安大略省渥太華市
- 地理單位
- Official City of Ottawa municipal ward 13: RIDEAU-ROCKCLIFFE
- 邊界與版本年份
- City ward layer · effective 未發布 · imported 2026年8月4日
- 官方市政聯絡方式
- Rawlson King · 市議員 · 來源查核已超過公布門檻的時限 · source checked 2026年8月4日 · 市府官方聯絡資料來源
- Mark Sutcliffe · 市長 · 來源查核已超過公布門檻的時限 · source checked 2026年8月4日 · 市府官方聯絡資料來源
- 相關的預定服務
- 27 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.
證據日期
- 已匯入
- 計算或整合時間
- 樣本
- 304,271 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:14da2c1aa13eb98c4ef15b281dae67d21a67834398c7cc28c35526bff5e03dac
來源
請注意的限制
- 數量只代表範圍內已公布的設施清單，並不代表服務品質，也不代表每個地址都能使用。
- 可靠度涵蓋 OC Transpo 供應商在依地理位置劃分的站點所提供的最終預測。實際到站情況並未獨立量測。軌道交通,以及沒有合格預測數據的班次,不在此範圍內。
- 無法取得的數量會維持為無法取得，不會改為零。
我們如何衡量
對於該選區內各站的每個行程、站點和服務日期，我們保留 OC Transpo 最後一筆符合條件的預測，並與時刻表比較。兩者相差不超過五分鐘時，算作五分鐘內。這不是實際到站。
統計期間為最近 28 個已完成的服務日。必須有 20 個平日的預測數據，以及 500 筆合格預測，才會發布結果。路線結果涵蓋整條路線，而不只是選區內的部分。
Read the full methodContains information licensed under the Open Government Licence – City of Ottawa.