Schools / Delhi

Road-environment audit · SSI v0.3

The road outsideVidya Bharati School

G Block, Sector 15, Sector 15G, Rohini, Delhi, 110089, India28.73303, 77.13000audited 2026-08-06

15/100

Critically unsafeprovisional band

Critically unsafe. Almost nothing on this road protects a child from traffic on the way to the gate.

Of the five things we check, 3 are missing entirely.

This road · 15

0 · no protectioncomplete protection · 100

Checked twice, independently

Two AI readers on separate accounts · corrections logged in public

Confirmed

Corrected

Unresolved

See how each was judged

Of 153 roads scored so far, this one ranks 105 (worst first). The others scored between 0 and 41.

11.25points earned

75.25points we could see (75%)

15.0%provision

1exposure — local

15.0provision × exposure

→

15SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (75% of the rubric here); the rest is left uncounted rather than guessed. A road with full protective infrastructure scores near 100.

The road in context · derived from public data

Where this road sits

Before the checks: what kind of road this is, how it meets other roads, and what passes it. These lines describe the road and its surroundings — they do not change the score.

Road layout around the gate, drawn from OpenStreetMap — Road layout · drawn from OpenStreetMap · blue dot = school coordinate

Satellite view of the same area — Satellite · © Google · retrieved 2026-08-13 (capture date not published by the imagery API)

FrontageThe gate opens onto a local street, on its SW side

Junctionthe gate area sits at a 4-leg junction

Street activityno bus stop or shops mapped within 150 m (OpenStreetMap)

Crash recordcrash-location data is not yet available for Delhi — this line will be added when a public source lands

Exposure contextModerate — 22/100 (partial: no crash component yet). Describes how much traffic and crash risk passes this road — context only, never part of the road score (method: exposure v1, Data page)

Road layout data © OpenStreetMap contributors (ODbL), retrieved 13 Aug 2026 · crash data: Jaipur Police · derivations: `exposure_v1` on the Data page.

What we found · five checks · IRC:SP:32-2023

Five things we checked — and the photo behind each

Each check was read once, then verified blind by a second reader on a separate account. The photo each finding came from sits right beside it. Tap “see how this was judged” for the full reasoning.

Slowing traffic downP1 · Physical speed control

Nothing slows traffic at the gate

No speed hump, table or rumble strip on the approach — vehicles reach the gate at full speed.

Absent

Also cited for this check

0 of 30 points

LevelNone (L0)

Points0 of 30

ConfidenceHigh

Coverage seen≈80%

VerificationConfirmed — both readers agreed

The full reasoning

No speed hump, table, rumble strip or raised crossing visible on either gate approach or along the observed frontage/zone; road surface flat where seen.

Getting across the roadP2 · Safe crossing

No safe place to cross

No marked or raised pedestrian crossing at or near the gate.

Absent

Also cited for this check

0 of 25 points

LevelNone (L0)

Points0 of 25

ConfidenceHigh

Coverage seen≈80%

VerificationConfirmed — both readers agreed

The full reasoning

No marked pedestrian crossing (zebra or table-top) visible at the gate, along the frontage, or at the observed zone extremities; only a faint longitudinal centre-line marking is present.

◑

Walking without stepping into trafficP3 · Footpath & separation

A broken walking edge

A walking edge exists but is broken or blocked for most of the frontage.

Partial⟳ Corrected in review

NoneMinimal

An independent second reader changed this — the two readings disagreed, and the evidence below settled it.

Also cited for this check

6.25 of 25 points

LevelMinimal (L1)

Points6.25 of 25

ConfidenceMed

Coverage seen≈65%

VerificationCorrected in the second reading

The full reasoning

Audit's L0 falls. A walkable edge does exist in parts: a permanent tiled apron at the gate (Fu9m3kBFK gate_wide/zoom) and an at-grade margin along the school-side boundary wall (sxbosX7R2K h190, nns h129), but it is broken by permanent large banyan trunks and by building/shop frontages meeting the carriageway along most of the frontage — the L1 condition, not 'none' (L0). The audit conflated 'no continuous distinguishable edge' (which correctly rules out L2) with 'no edge'. Its pedestrians-on-carriageway evidence (ZmMNYA7kcVu1 h227 2022; nns h129 2026) is equally consistent with a broken/blocked edge (L1). Not L2: no continuous usable edge on either side. Observability gap (blind 0.6 vs audit 0.85 = 0.25) is accounted for by continuous parked vehicles and dense tree canopy obscuring the permanent school-side edge condition, plus the oblique-only view of the opposite-side base — settled at 0.65; MED confidence as the level rests on partially obscured evidence.

Being seen and expectedP4 · Signage & zone identity

No school-zone signs

Drivers get no warning that a school gate is here.

Absent⟳ Corrected in review

MinimalNone

An independent second reader changed this — the two readings disagreed, and the evidence below settled it.

Also cited for this check

0 of 10 points

LevelNone (L0)

Points0 of 10

ConfidenceMed

Coverage seen≈65%

VerificationCorrected in the second reading

The full reasoning

Audit's L1 falls. Its sole basis — the yellow 'STOP / VIDYA BHARATI SCHOOL' board — is a freestanding A-frame barricade (two such portable boards stand on the forecourt on their own legs, not post- or wall-mounted; Fu9m3kBFK gate_wide/zoom), a movable/momentary object that procedure §6 forbids scoring. Struck. No installed school-warning traffic sign, no speed-limit sign or carriageway speed stamp, and no 2023 zone-identity asset appears on either approach; only the school's own name/notice boards on the wall. = L0. Confidence MED: tree canopy leaves some occlusion risk on the far approach.

◑

The gate itselfP5 · Gate environment

Space and a railing at the gate

A clear setback or railing gives room to gather off the carriageway.

Partial

Also cited for this check

5 of 10 points

LevelBasic (L2)

Points5 of 10

ConfidenceHigh

Coverage seen≈85%

VerificationConfirmed — both readers agreed

The full reasoning

Gate is recessed under a gatehouse porch with a paved apron, and a continuous boundary wall with railing runs along the frontage, giving off-carriageway assembly space (L2). No clearly separate pedestrian opening was confirmable at zoom and no continuous rail from gate to a crossing, so L3 is not awarded.

At the gate

On the frontage road

Along the street

Some captures sit on neighbouring lanes; older ones are shown greyed and were used only for context.

What must be fixed · 5 actions

What would make this road safe — and who owns each fix

Each action maps to a failing check, the relevant IRC:SP:32-2023 clause, and the responsible agency. Agency labels are provisional and correctable through the dispute channel.

01Lifts P1

Install a speed table or twin speed humps within 30 m of the gate

IRC:SP:32-2023 §5.13 · Table 5.1MCD / PWD · provisional

Speed humps near schools roughly halve child-pedestrian injury odds (Tester 2004); 30 km/h calmed zones ≈ 40% fewer casualties (Grundy 2009).

02Lifts P2

Mark a crossing within 20 m of the gate — table-top preferred

IRC:SP:32-2023 §5.4.3MCD / PWD · provisional

Raised crossings cut vehicle speeds at the exact conflict point.

03Lifts P3

Provide a continuous clear walking edge on the school side

IRC:SP:32-2023 §5.4.1MCD / PWD · provisional

A continuous footpath keeps children off the carriageway on the approach, not only at the gate.

04Lifts P4

School-zone warning signs on both approaches with the speed limit

IRC:SP:32-2023 §5.8MCD / PWD · provisional

The zone must announce itself to drivers before the gate.

05Lifts P5

Add space and a marked pick-up bay off the carriageway at the gate

IRC:SP:32-2023 §5.2MCD / PWD · provisional

Children should not step from the gate into a moving traffic lane.

Responsible-agency labels come from the CFI field instrument’s mapping and are correctable via the dispute channel.

Re-audit timeline

2026-08-06Audited

2027-02-06Re-audit due

Every published road is re-read every six months, or as soon as new Street View imagery lands, or on a sustained dispute.

Something wrong on this page?

The entrance, the imagery, a finding — if any of it is wrong, tell us. A dispute pauses this page while the audit is re-verified, and the correction is logged in the public record.

Dispute this audit