Schools / Jaipur

Road-environment audit · SSI v0.3

The road outsideShree Dev Public Senior Secondary School

Keshav Vidyapeeth Road, Jaisinghpura Khor, Jaipur, Rajasthan 302027, India26.93625, 75.88661audited 2026-08-06

10/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 · 10

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

8.75points earned

71.25points we could see (71%)

12.3%provision

0.85exposure — collector

10.4provision × exposure

→

10SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (71% 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 collector road, on its E side

Junctionthe gate area sits at a 4-leg junction

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

Crash recordno road death within 500 m of the gate in the Jaipur Police crash data

Exposure contextModerate — 37/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

ConfidenceHigh

Coverage seen≈75%

VerificationConfirmed — both readers agreed

The full reasoning

No speed hump, table, rumble strip or raised crossing visible on the frontage or along either approach in the 2026-04 views; the carriageway is bare earth. The 2023-02 far-zone track also shows no devices. Absence assessed over stretches actually seen (near/mid zone both directions).

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≈75%

VerificationConfirmed — both readers agreed

The full reasoning

No marked pedestrian crossing, no raised/table-top crossing and no refuge island observed at, near, or beyond the entrance; the earthen carriageway carries no markings. No crossing provision seen on either approach.

◑

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

MinimalMinimal

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≈70%

VerificationCorrected in the second reading

The full reasoning

Disagreement (blind L0 vs audit L1). Deciding frames re-examined: KxhMdgnA7i5X_h246 and 5jsT_h157 / FEmB_h157 show a raised concrete shop-verandah plinth forming a walkable raised edge along the shop rows, broken by steps, support pillars and level changes and absent on open stretches; Rx_h246 and Kxh_h066 confirm the school's own frontage has no raised footpath (building/wall meets the earthen verge). A raised edge plainly EXISTS (refuting 'none'=L0) but is discontinuous along most of the frontage (refuting continuous L2) — precisely L1. The blind read fell: it wrongly dismissed the shop plinth as non-footpath. Final L1, MED (the plinth's footpath status is interpretive and only one side carries it). Observability gap (0.85 vs 0.6, >0.15) resolved to 0.70; the gap is the school-side verge base under standing water (KxhMdgnA7i5X_h066), plinth continuity occluded by parked motorcycles (5jsT_h157), and the second approach being only 2023-02 track (xsqzXLWamWJR/dxLvBlC5jOJw).

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≈70%

VerificationConfirmed — both readers agreed

The full reasoning

No school-warning sign, speed-limit sign, carriageway speed stamp, or 2023-identity zone asset (transition/zone-start sign, fluorescent yellow-green faces, red-white markings, beacon) identified on the frontage or either approach. A small blue pole-mounted sign in one view reads as informational/non-creditable; the numerous banners are school and commercial name boards, not traffic signage.

◑

The gate itselfP5 · Gate environment

A small setback at the gate

A little setback or partial barrier — limited space off the road.

Partial

Also cited for this check

2.5 of 10 points

LevelMinimal (L1)

Points2.5 of 10

ConfidenceMed

Coverage seen≈55%

VerificationConfirmed — both readers agreed

The full reasoning

Main entrance opens to an internal staircase at the frontage with a partial railing/balustrade and only a minimal setback onto the earthen edge; no clear off-carriageway assembly forecourt, no separate pedestrian opening visible in zoom, and no continuous gate-to-crossing rail evident. Immediate threshold partly obscured by privacy blur, so setback depth is uncertain.

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