Pedestrian Analysis for Urban Designers: Routes, Catchments and Observed Flow

Identify likely origins and destinations such as homes, stations, schools and services. Use actual entrances rather than parcel centres where possible. Map plausible desire lines, then ask where public access, opening hours, severance or level changes prevent the direct connection. Record existing conditions separately from proposed links.

The reviewed pedestrian calculation attempts to use a street network but can fall back to a direct line when road data or a route is unavailable. Check the route type and available source information before calling a result a walking route. A line across a railway, fenced plot or river is not a verified connection. Route time remains an estimate based on assumptions.

For a footfall question, record counts, direction, location, observation periods, weather and unusual events. Consider school times, commuting peaks, weekends and relevant seasonal use. Repeat or commission an appropriate survey where the decision warrants it. A network route result alone has no observed pedestrian volume and should not be presented as a calibrated forecast.

Walk the route and record crossings, kerbs, width, resting opportunities, surface condition, lighting and gradients. Check applicable accessibility standards and consult users or specialists where relevant. Do not apply a single gradient threshold to every jurisdiction and route type. Review safety and perceived comfort with evidence rather than infer them from the number of nearby amenities.

Compare entrance locations, crossing improvements, through-routes and frontage uses. Label unapproved links as proposals and check deliverability. Retail viability needs more than potential passing movement: use mix, catchment demand, access and commercial advice also matter. Evaluate the preferred option against the observed problem rather than assume every new path will attract the intended users.