The Gurugram footpath record
Every published check, as a file you can open in a spreadsheet or a script. Names are never in it. Locations are rounded to about 10 m. Nothing appears here until a moderator has read it.
Files
- checks.csv: one row per published check, flat columns (below). Opens in Excel, Sheets, QGIS.
- checks.json: the same rows with answers and problem counts as nested objects, plus the snapshot time.
- stats.json: the headline counts and the by-sector and by-owner tables.
Snapshots are taken once a day at about 03:00 IST by a GitHub Action in the public repository DeepanshuCFI/righttowalk; the map and report read the live record. The live JSON endpoints are public and read-only:
Columns
| Column | Meaning |
|---|---|
| id | Random identifier of the check (UUID). The first eight characters are the reference shown to the walker. |
| created_at | When the check was sent in (UTC, ISO 8601). |
| mode | quick (one spot, about two minutes) or full (a stretch of about 500 m, eleven questions). |
| method | Method tag, footpath-check-v1.2: method v1.0 weights with problem types recorded. |
| lat, lon | Where the check started, rounded to four decimals (about 10 m). Empty when the walker named the road instead. |
| length_m | Straight-line distance between the start and end fixes of a full check, metres; empty for a quick check or when no end fix was taken. |
| side | left or right: the footpath on the walker's left or right as they walked. |
| road, sector | As typed and chosen by the walker. Free text; not geocoded. |
| land | What sits beside the stretch: homes, shops, city (city commercial street), sensitive (school, hospital, bus stop or market within the stretch). Sets the IRC:103-2022 walking-zone width that applies. |
| road_class | Derived from four questions: arterial, subarterial, collector, local. |
| owner | The agency the walker believes maintains the road: gmda, mcg, hsvp, dtcp, nhai, pwd, unknown. A guess; verified re-walks correct it. |
| gate | The Court's test. yes: the walker could go 100 m on this side without stepping onto the road; no: could not; empty: not answered (quick checks may skip it). |
| i1 to i10 | The ten items of a full check: footpath present, clear of obstructions, a real crossing, slow enough to cross, wide enough for two, ramps and tactile tiles, level surface, lit at night, kerb height and continuity, buffer and shade. Values yes, no, partly (items 2, 3, 7), cant (item 8). When i1 is no, items 2, 5, 6, 7, 9 and 10 fail automatically. |
| score, band | Full checks only. Score 0 to 100 over the items the walker could judge; band g walkable, a walkable with repairs, r not walkable. A failed gate is always r. |
| anchor | Full checks: would you let a 10-year-old or your grandmother walk this alone, 0 (definitely) to 4 (never). Reported, never scored. |
| obs_* | How many times each problem type was tapped: obs_parked, obs_vendor, obs_shop, obs_ramp, obs_electric, obs_green, obs_manhole, obs_slab, obs_dug, obs_waste, obs_furniture, obs_water, obs_riding, obs_cattle, obs_shrine. |
| photo_count | Photos the walker sent. Photos are published with the pin on the map, not in these files. |
| verified | true when a trained volunteer re-walked the stretch and a moderator confirmed the record. |
Licence and citation
Creative Commons Attribution 4.0 (CC BY 4.0). Use it, map it, publish it; say where it came from. Cite as: Crashfree India, Right to Walk: Gurugram footpath record, righttowalk.life, snapshot of the date in the file. Each walker consented to publication under this licence when they added their check.
Not in the record, by design: names, email addresses, phone numbers, device identifiers, exact coordinates, and anything a moderator did not publish. Photos go through a moderator before they can be seen, and they are resized and stripped of camera metadata on the walker's phone before upload.