Crashfree India School Safety Index DELHI · JAIPUR · PUNE

Schools / Delhi

Road-environment audit · SSI v0.3

The road outsideTitiksha Modern Public School

F-352/8, Hanuman Mandir Road, Block F, Sadatpur, Karawal Nagar, New Delhi, Delhi, 110090, India28.72512, 77.25937audited 2026-08-06
29/100
Unsafeprovisional band
Unsafe. Very little on this road protects a child crossing to the gate.
Of the five things we check, 3 are missing entirely.
This road · 29
0 · no protectioncomplete protection · 100
Checked twice, independently
Two AI readers on separate accounts · corrections logged in public
3
Confirmed
2
Corrected
0
Unresolved
See how each was judged
Of 153 roads scored so far, this one ranks 142 (worst first). The others scored between 0 and 41.
17.5points earned
/
60points we could see (60%)
=
29.2%provision
×
1exposure — local
=
29.2provision × exposure
→
29SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (60% 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
Satellite view of the same area© Google
Satellite · © Google · retrieved 2026-08-13 (capture date not published by the imagery API)
FrontageThe gate opens onto a local street, 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 recordcrash-location data is not yet available for Delhi — this line will be added when a public source lands
Exposure contextModerate — 22/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
Also cited for this check
0 of 30 points
LevelNone (L0)
Points0 of 30
ConfidenceHigh
Coverage seen≈55%
VerificationConfirmed — both readers agreed
The full reasoning

No vertical or horizontal speed-control device seen on the frontage carriageway at the gate or along the observed stretch either side: no hump, table, rumble profile or transverse bar marking in the pTeG (19.4 m) or yqFsIWYw (29.9 m) views along road axis 074/254. The near-gate carriageway edge is a dust-covered unpaved apron, but a raised device would still read in profile and none is present in any view. Frontage road beyond roughly 70 m each way is not covered at grade, so the outer zone approaches are unassessed; observability reflects that.

✕
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, faded remnant, refuge island or raised table seen on the frontage road. The paved carriageway shows only a longitudinal edge line and black/white kerb painting at the retaining-wall base (pTeG h254, yqFsIWYw h254); no transverse markings at or near the gate. The school side is separated from the carriageway by a continuous W-beam guard rail and no crossing point through it was observed. Confidence held at MED because dust cover on the near-gate surface limits detection of heavily faded markings, and the outer zone approaches are not covered at grade.

◑
Walking without stepping into trafficP3 · Footpath & separation

A footpath on one side

A continuous, usable walking edge runs along one side.

Partial⟳ Corrected in review
NoneBasic

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

Also cited for this check
12.5 of 25 points
LevelBasic (L2)
Points12.5 of 25
ConfidenceHigh
Coverage seen≈65%
VerificationCorrected in the second reading
The full reasoning

The audit's read falls. Audit held L0 on the ground that 'at the gate frontage only an informal earthen/unpaved shoulder separates the building line from a road-edge guard-rail'. yqFsIWYw1AsU_h045_f35 refutes this directly: between the guard rail and the building line there is a constructed raised concrete platform, not earth, running as an unbroken light-grey band from the left frame edge, past the gate, along the white wing, to the right frame edge - and a pedestrian in a white shirt is standing on it outside the gate while a second person is in the gate opening. The earthen surface the audit describes lies on the road side of the rail, i.e. the carriageway apron, not the school-side edge. pTeG_gIKlFu5_h074_f90 shows a pedestrian walking along the same band well away from the gate, and pTeG_gIKlFu5_h118_f90 shows it continuous across the full frontage carrying a bench. Three views, two panoramas, two separate pedestrians in use at different points along it. The audit's supporting observation that 'pedestrians including children are seen walking directly on the carriageway' comes only from lBfttsUR4Nxs and sKge5jYCz09j, a neighbourhood lane 145-160 m east captured 2022-03 - a different street from the frontage, and momentary occupancy at that (struck below). My own blind read was then attacked in turn: is the band a genuinely continuous walkable edge or a drain cover interrupted by open channel sections, which would give L1 (exists but broken along most of frontage)? pTeG_gIKlFu5_h118_f35 does show a rectangular concrete channel structure near the gate, but it sits between the rail and the platform, on the road side of the walkable band, with the gate apron slabbed over it; the band itself reads unbroken in all three views. L1 rejected. L3 rejected on clear evidence: the opposite (SW) edge is the elevated-corridor retaining wall meeting the carriageway at a painted kerb with no walkable edge at all (pTeG_h254, yqFsIWYw_h254), so 'both sides' fails, and since levels are cumulative the guard-rail separation cannot lift this to L4 either. Final L2, continuous usable edge one side. Confidence HIGH on the qualifying attribute (existence and continuity of the constructed edge across the frontage); residual uncertainty concerns stretches beyond the frontage and is carried by observability, not confidence. Observability: audit 0.75 vs blind 0.65 is within tolerance, but the audit's figure again drew on off-frontage lane images; settled at 0.65 on the two at-grade panoramas, which cover the school-side edge across the whole frontage and the far side clearly, but not beyond roughly 70 m either way.

✕
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≈45%
VerificationConfirmed — both readers agreed
The full reasoning

No road-side school warning sign, speed-limit sign, carriageway speed stamp or named 2023-identity asset (transition sign, zone-start sign, fluorescent yellow-green face, red-white school-zone carriageway marking, beacon hardware) observed on either approach. Boards visible on the frontage are building-mounted name boards and a small wall notice; the retaining wall opposite carries an advertising banner and a small utility notice, neither a traffic sign. Detection is limited by f90 resolution at distance and by the absence of at-grade coverage on the outer approaches, so observability is held low.

◑
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

The audit's read falls. Audit held L1 on the ground that 'no distinct off-carriageway assembly area or railing is visible'. Both conditions are in fact present and visible in all four gate images. Railing: a continuous W-beam guard rail runs between the gate frontage and the carriageway across the entire width of pTeG_h118_f90, pTeG_h118_f35, yqFsIWYw_h045_f90 and yqFsIWYw_h045_f35 - the audit's own P3 note acknowledges this same rail ('a road-edge guard-rail'), so its P5 finding of 'no railing' contradicts its own record. Assembly area: the raised concrete platform between gate and rail is occupied by a standing pedestrian in yqFsIWYw_h045_f35 and carries a bench in pTeG_h118_f90, demonstrating usable off-carriageway space; the gate apron is slabbed over the roadside drain. L2 requires 'clear setback OR railing giving off-carriageway assembly space' - here both limbs are satisfied. My own blind read was then attacked for over-reach in the other direction: does the configuration reach L3? No. L3 needs a separate pedestrian opening visible in zoom, and pTeG_h118_f35 at f35 resolves the entrance as a single grille leaf under the archway with painted panels either side and no second opening; the alternative limb, a continuous rail from gate to crossing, is unattainable because P2 is L0 and no crossing exists to run to. L4 also fails - no marked pick-up/drop-off bay anywhere on the frontage. Final L2, HIGH confidence (two panoramas, wide and zoom, fully consistent). Observability: both reads gave 0.90 and it holds - the gate is covered by four images from two panoramas at 19.4 m and 29.9 m at two FOVs.

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