- ᐅᖃᓕᒫᕐᓂᖅ
- ᖃᓄᖅ ᑐᓴᒐᒃᓴᐃᑦ ᐱᓕᕆᐊᖑᓂᖏᑦ
- Confirmed current operator notices
The number of connected official notices classified for current display from the published timing or the disclosed source-presence policy. Notice display does not confirm physical service impact or restoration.
- Definition
- The number of connected official notices classified for current display from the published timing or the disclosed source-presence policy. Notice display does not confirm physical service impact or restoration.
- Formula
- COUNT(catalog notices classified current at the snapshot clock). STO communication/impact field presence supersedes legacy active_period; actual starts are inclusive and ends exclusive. Untimed display follows the disclosed source-presence policy.
- Units
- ᐱᓕᕆᕕᐅᑉ ᑐᓴᖅᑎᑦᑎᓂᖏᑦ
- Population
- Connected official operator notices after source parsing and catalogue deduplication.
- Measurement window
- Point-in-time notice display, evaluated against complete current timing lists or the disclosed source-presence policy.
- ᐃᓚᐅᔪᑦ
- OC Transpo and STO official notice sources, with each source’s availability and freshness attached.
- Publication eligibility
- Notices classified current by the shared timing method: inclusive starts, exclusive ends and explicitly disclosed untimed display. Planned, ended and unknown-timing notices remain separate.
- ᐊᑐᕐᕕᖓ
- The current connected OC Transpo official notice source and STO GTFS-Realtime alert source. Source availability and freshness are reported with the count.
- What this number can support
- Count of source records, not a standardized amount of service lost or rider impact. Regional completeness is withheld when a required source is stale or unavailable.
- Sources and identifiers
- Method · Official-notice timing method
operator-published-alert-periods-v2 - Current API · Current public alert catalogue
public-alert-catalog
- Method · Official-notice timing method
Implementation status
- Source candidate
- Implemented in this source candidate.
- Public production
- This metric version has not been independently verified in the public production deployment.
Read the status before citing this number.
The calculation is implemented in this source candidate. This record does not claim that the same version has been independently verified in the public production deployment.
Exclusions
Planned, expired, and unknown-timing notices are not counted as active. Detected operating conditions and rider reports remain separate.
The count is withheld when a required operator source is unavailable or stale, the latest read failed, or notice timing is unknown, incomplete or inconsistent. Missing physical-impact timing alone does not invalidate a confirmed notice.
Uncertainty and interpretation
Operators choose notice granularity and affected-entity detail, so one notice is not a standardized unit of rider impact or service lost.
Current evidence
No registered drill-down record is available for this metric. The public page remains the current presentation source.
Change history
No registered material change is recorded for this metric version.