Road-environment audit · SSI v0.3

The road outsidePrakash Vidhya niketan sr.sec school

WQ6H+JG4, A-11, Ajmer Rd, Shanti Nagar, Civil Lines, Jaipur, Rajasthan 302006, India26.91192, 75.77886audited 2026-08-06

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

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

8.75points earned

80points we could see (80%)

10.9%provision

1exposure — local

10.9provision × exposure

→

11SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (80% 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 N 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 — 22/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≈80%

VerificationConfirmed — both readers agreed

The full reasoning

No physical speed-control device (raised hump, table, rumble strip or thermoplastic bar marking) visible on the frontage or on either approach to the gate, nor at the sampled zone points. Frontage road surface is plain/partly-unpaved concrete.

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) on the frontage, at the corner junction by the gate, or across the zone. Frontage surface is dusty/unpaved concrete carrying no markings.

◑

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

VerificationCorrected in the second reading

The full reasoning

My blind read (L0) fell. Re-examined Svx2sdrhxw8H_h243: a constructed raised paved edge runs along the compound wall on the left (a genuine walkable edge, not merely a private plinth), and narrow paved entrance aprons front other buildings (UkKLHdY_qqB1 corner; fxsuPw2V7H1e_h216) — so a footpath/walkable edge does exist in places. Svx2sdrhxw8H_h063 confirms the school's own frontage is wall/plinth to bare ground with none, and junctions (6pmCcEGt2APv_h001) have none. This is a footpath that exists but is broken/discontinuous along most of the frontage (L1), not wholly absent (L0). Not L2: no continuous usable edge along any one full side. Audit's L1 upheld; MED reflects the genuinely fragmentary provision and the L0/L1 boundary judgment.

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

ConfidenceHigh

Coverage seen≈80%

VerificationConfirmed — both readers agreed

The full reasoning

No road traffic school-warning sign, speed-limit sign or 2023-identity zone asset identifiable on any approach. Building-mounted name boards (PRAKASH VIDHYA NIKETAN; a nearby PRAKASH PUBLIC SCHOOL board) and third-party coaching banners (LEARNING STEP / THE KEN WORLD) are identity/advertising, not traffic signage. Small illegible boards on the pole/railing at the corner (FWS8QZHcD79y_h319) could not be resolved but do not read as standard warning signs.

◑

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

VerificationConfirmed — both readers agreed

The full reasoning

Corner-plot entrance with boundary wall and black spiked railing; a modest paved corner forecourt gives some off-carriageway standing space (UkKLHdY_qqB1_h127). At the immediate side frontage the wall sits close to the dusty road edge with minimal setback (Svx2sdrhxw8H_h307). Reads as partial barrier plus minimal setback; exact gate opening and setback depth not fully resolved (borderline L1/L2). No separate pedestrian opening or continuous rail-to-crossing established.

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