Schools / Pune

Road-environment audit · SSI v0.3

The road outsideGendibai Tarachand Chopda High School

JRW3+H6V, Telco Rd, MIDC, Chinchwad, Pimpri-Chinchwad, Maharashtra 411019, India18.64649, 73.80306audited 2026-08-06

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

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

11.25points earned

69.75points we could see (70%)

16.1%provision

0.75exposure — arterial

12.1provision × exposure

→

12SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (70% 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

FrontageThe gate opens onto an arterial road (Chikhali - Kaspate Vasti BRTS Road | Telco Road | Chinchwad Station Road), on its NW 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 contextElevated — 52/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

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 seen anywhere in the assessable stretch: no hump, table, rumble strip or markings on the smooth asphalt carriageway in the frontage road views or along the traversal points. No raised table at the gate. Carriageway seen over a good fraction of the zone but not its full 147 m length.

Getting across the roadP2 · Safe crossing

No safe place to cross

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

Absent

0 of 25 points

LevelNone (L0)

Points0 of 25

ConfidenceMed

Coverage seen≈70%

VerificationConfirmed — both readers agreed

The full reasoning

No marked pedestrian crossing anywhere in view - no zebra, no refuge crossing, none at or near the gate. Only white edge-lane lines are present on some stretches. Crossing this wide divided carriageway would require a refuge for L3+, none exists. Frontage and several traversal stretches assessed.

◑

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

Also cited for this check

6.25 of 25 points

LevelMinimal (L1)

Points6.25 of 25

ConfidenceMed

Coverage seen≈55%

VerificationConfirmed — both readers agreed

The full reasoning

Arterial (collector+) requires a raised footpath. Pedestrian edge is mostly an unpaved dusty apron/shoulder along the frontage; only a short stretch of paver-block paving exists at the base of the compound wall by the gate. No continuous raised footpath on either side (far side beyond median is open ground/parking). Existing walkable edge is discontinuous/broken along most of frontage. Permanent built condition judged, parked vehicles/stalls ignored.

Being seen and expectedP4 · Signage & zone identity

No school-zone signs

Drivers get no warning that a school gate is here.

Absent

0 of 10 points

LevelNone (L0)

Points0 of 10

ConfidenceMed

Coverage seen≈55%

VerificationConfirmed — both readers agreed

The full reasoning

No road school-warning sign, no speed-limit sign and no 2023 zone-identity asset seen. The only boards at the gate are the school's own name/welcome banners (not road safety signage). A blue directional gantry sign is visible far down the road but is not a school-zone asset. No carriageway speed stamp or zone markings.

◑

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

ConfidenceHigh

Coverage seen≈90%

VerificationCorrected in the second reading

The full reasoning

Disagreement (audit L1 'minimal setback' vs blind L2 'clear setback'). Decided from the wide gate/frontage views. QpxBWyMay64W_h331_f90 and h304, and FtUiBs8BgXFH_h351_f90 all show the masonry compound wall and gate set well back from the asphalt carriageway behind a broad dusty forecourt/apron - a substantial off-carriageway space where assembly can occur, not the 'minimal' setback the audit described (the audit weighted tight gate-zoom frames, obs 0.75 MED, and undersold the setback width). This clearly meets L2 'clear setback giving off-carriageway assembly space'. Not L3: no separate pedestrian wicket resolvable (single/two-leaf vehicular gate) and no continuous rail gate to crossing. The audit's L1 read falls on the wide-view evidence; blind L2 confirmed at HIGH.

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