Traffic Lab must not pretend model proxies are observed reality. The Delhi simulator uses OpenStreetMap-derived roads, pincode demand inputs and curated priors, but it does not claim live traffic or official transport-model calibration.
Road network
OpenStreetMap/Overpass road graph with road class, lanes, one-way, bridge/tunnel and signal tags where mapped
Scenario-only user edits are layered on top; no imaginative fallback roads should render on /delhi
Demand
Delhi pincode adult-population values, KML pincode polygons, density estimates, time profiles and zone-role weights
Deterministic OD demand proxy; no personal traces or live traffic feed
Traffic priors
Curated Delhi NCR pressure locations and corridors with time windows, causes and severity
Manual/open-data planning priors, not live traffic
Amenities
OSM-style POIs if present in metadata
Generated accessibility proxies if POIs are missing
Transit
GTFS/public feeds planned
Bus/metro mode-share proxy; real route geometry pending
Circle rates
Delhi category rates plus NCR collector-rate estimates
Used for scenario footprint/private-land estimates; exact locality imports pending
Edit mechanics
Two-click lane/new-link geometry, flyover approach-lane option, major-corridor connector relief, open-space shortcut index and roundabout radius are stored as scenario properties
Model mechanics, not external datasets
Open-space impact
Distance from proposed new-link geometry to existing road centerlines is used as a shortcut/environment proxy
Planning proxy only; not a real land-cover or environmental dataset
Planned imports include OSM POIs, GTFS routes/stops, metro geometry, crash/blackspot data, land-use profiles, market/freight indicators and row-level collector/circle-rate tables.
Read limitations