Road-environment audit · SSI v0.3

The road outsideKaushik Shiksha Niketan Sr. Sec. School , Jaipur

kaushik circle, 259 kaushik school, Green Park Ln, Dadi Ka Phatak, Suraj Nagar, Nirmal Vihar, Jhotwara, Jaipur, Rajasthan 302012, India26.97109, 75.74927audited 2026-08-08

0/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, 5 are missing entirely.

This road · 0

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

0points earned

80.75points we could see (81%)

0.0%provision

1exposure — local

0.0provision × exposure

→

0SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (81% 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 3-leg junction

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

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

Exposure contextModerate — 24/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≈85%

VerificationConfirmed — both readers agreed

The full reasoning

No physical speed-control device (hump, table, rumble strip) and no road markings visible on either approach at the gate or along the near/mid zone; carriageway surface plain. Both approaches assessed from multiple consistent 2026-04 views, so absence is supported (not merely unseen).

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

VerificationConfirmed — both readers agreed

The full reasoning

No pedestrian crossing markings anywhere; carriageway near the gate on both approaches is plain with no zebra, table-top or refuge. Undivided single carriageway. Near-gate surface clearly visible in multiple views, so absence is supported.

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

VerificationCorrected in the second reading

The full reasoning

Reads differ (audit L1, blind L0). Deciding images: the four near-gate road frames plus the 3f6x mid-zone travel pair (2026-04) and the Tr5uOSkGvUQK travel frame (2024-11). Assessing permanent built form only (parked two-wheelers, shop goods and construction/brick/gravel piles ignored per P3 discipline), there is no continuous clear walkable edge on either side: the edge is unpaved dusty shoulder interrupted by discontinuous private building plinths at varying levels and by utility poles/drains, and pedestrians are observed walking on the carriageway in several frames across both capture dates. Paved frontage plinths are present along only a minority of the frontage and do not connect, so even L1's 'exists but broken/blocked along most of frontage' is not met. Attacking L1: the no-provision / pedestrians-on-carriageway refutation is strong and survives; attacking L0: treating private plinths as a broken footpath does not survive. Audit over-credited private frontage plinths as an existing walkable edge; the audit read fell. Final L0.

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

VerificationConfirmed — both readers agreed

The full reasoning

No school-warning signs, speed-limit signs, carriageway speed stamps, or any named school-zone identity asset on either approach; only commercial shop signage present. Poles and frontages where such signs would mount are clearly visible near the gate, so absence is supported.

The gate itselfP5 · Gate environment

The gate opens onto the road

Children step from the gate straight toward moving traffic.

Absent

Also cited for this check

0 of 10 points

LevelNone (L0)

Points0 of 10

ConfidenceLow

Coverage seen≈55%

VerificationConfirmed — both readers agreed

The full reasoning

Candidate gate (ornamental metal gate at the south frontage by 'Arihant Stationers') sits essentially at the carriageway behind only a narrow raised plinth; no clear off-carriageway setback or assembly space, no frontage railing line, no separate pedestrian opening, and no marked pick-up/drop-off bay evident. Built form reads between L0 and L1; gate identity is uncertain (LOW), so the lower candidate level is 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-08Audited

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