Schools / Jaipur

Road-environment audit · SSI v0.3

The road outsideLiberty Child Public School

VPH7+JWF, 1-Chha-13, Kamla Nehru Nagar, Jaipur, Rajasthan 302021, India26.87907, 75.71480audited 2026-08-09

8/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, 4 are missing entirely.

This road · 8

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 65 (worst first). The others scored between 0 and 41.

5points earned

61.5points we could see (62%)

8.1%provision

1exposure — local

8.1provision × exposure

→

8SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (62% 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 · red = fatal-crash points (Jaipur Police)

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 S side

Junctionthe gate area sits at a 9-leg junction

Street activity1 bus stop within 150 m (OpenStreetMap)

Crash record7 road deaths within 500 m of the gate; 6 of the recorded crashes fell on school days, 7 am–6 pm (Jaipur Police crash data)

Exposure contextElevated — 49/100. 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

ConfidenceMed

Coverage seen≈60%

VerificationConfirmed — both readers agreed

The full reasoning

No speed humps, tables, rumble strips or table-top markings visible on the frontage or on either near approach (both directions to ~50 m) in 2022-08 imagery. The 2026-03 views are heavily tree-occluded and the far zone (>100 m) reaches a different arterial road, so the full corridor is not fully assessed. No device present in the seen stretches.

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

ConfidenceMed

Coverage seen≈55%

VerificationConfirmed — both readers agreed

The full reasoning

No marked pedestrian crossing on the local frontage or near the gate in any seen view. A zebra crossing exists on a divided arterial ~148 m away at the far zone edge (wMwXvWGMwv1y_h238), which is a separate road and far outside 20 m of the gate — not scored. Frontage is an undivided single-lane local street, so no refuge would be required. Some far/occluded segments not assessed.

Walking without stepping into trafficP3 · Footpath & separation

No footpath — children share the road

No usable walking edge; children walk in the traffic lane.

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 25 points

LevelNone (L0)

Points0 of 25

ConfidenceHigh

Coverage seen≈65%

VerificationCorrected in the second reading

The full reasoning

Corrected to L0; audit's L1 fell. Frontage and near approaches (both directions, ~50 m, both dates) show property walls meeting the carriageway, an open drain and level changes; no usable walkable edge exists to be merely broken. Shared surface.

Being seen and expectedP4 · Signage & zone identity

No school-zone signs

Drivers get no warning that a school gate is here.

Absent

Also cited for this check

0 of 10 points

LevelNone (L0)

Points0 of 10

ConfidenceMed

Coverage seen≈60%

VerificationConfirmed — both readers agreed

The full reasoning

No traffic signage of any kind visible — no school-zone warning sign, no speed-limit sign, no zone-identity assets — on either approach or the frontage in the seen views. The school's own building name/advertising boards (LCPS name board, 'ADMISSION OPEN') are not traffic-control signage; painted wall text '75'/'986' are property/brand markings, not speed signs. Small signs could be occluded by trees in the 2026-03 views.

◑

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⟳ Corrected in review

MinimalBasic

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

Also cited for this check

5 of 10 points

LevelBasic (L2)

Points5 of 10

ConfidenceMed

Coverage seen≈75%

VerificationCorrected in the second reading

The full reasoning

Corrected to L2; audit's L1 fell. Road-facing 2022-08 view shows the black double-leaf gate opening into a setback forecourt (tree, water stations) behind a boundary wall - clear off-carriageway assembly space. No separate wicket or gate-to-crossing rail, so not L3.

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-09Audited

2027-02-09Re-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