Active travel data
Data on walking and cycling can come from different sources and may vary in quality. The most important point is that the data entered in HEAT should represent the average level of walking or cycling over a longer period. HEAT can also be used to assess hypothetical scenarios that do not rely on observed data.
More information on options for data inputs and on data conversion can be accessed through the above button.
Population survey data
Population surveys can provide representative estimates of average walking or cycling across a population. These figures usually include people who do not walk or cycle, so the population size entered in HEAT should represent the whole population covered by the survey.
Large, regular surveys, such as national household surveys, are particularly useful. However, suitable data are not available everywhere, and conducting a representative travel survey can be demanding. See also Population data.
Short-term counts or surveys
Short-term counts can be strongly affected by weather, season, day of the week and time of day. A count on a sunny day, for example, may be very different from one on a rainy day.
Because HEAT requires long-term average levels, short-term counts may need to be adjusted. This is particularly important when assessing a specific facility, such as a cycle path or pedestrian bridge. An example for how this can be done is provided by the US National Bicycle and Pedestrian Documentation Project.
Continuous automated counts and large surveys conducted throughout the year are less affected by these issues.
Data from a few locations
Counts or surveys at only one or a few locations may not represent walking or cycling across a wider area. Results can vary depending on the location, season and type of users.
Such data should therefore generally be interpreted as representing the locations where they were collected rather than being automatically extrapolated to a whole city or community. HEAT allows adjustments to account for some spatial and seasonal differences.
Trip and count data
If you use the number of trips or people counted, you also need an estimate of the average trip length to calculate the total amount of walking or cycling. For example, a count on a bridge does not show how far people travel beyond the bridge.
Trip length can be estimated from surveys of users or from travel surveys.
For assessments based on counts, the population size does not affect the calculated result because the total amount of walking or cycling is already captured by the counts and trip length. You can nevertheless enter a population size that is relevant to the study area for reporting purposes; see Population data.
HEAT currently does not support count data for motorized modes.
Bikeshare data
HEAT allows data from bikeshare systems to be entered in the flexible and full user interfaces.
Unlike most HEAT inputs, bikeshare data describe the whole system, rather than average use per person. Enter the average number of trips per day and average trip duration. Both are typically available from the bikeshare system.
Pedometer data
If you use step counts, make sure they mainly represent intentional walking, rather than all steps taken during the day.
Where possible, use data that distinguish walking from other steps. Alternatively, you can estimate the proportion of steps that represent intentional walking. A rate of around 100 steps per minute can be used to identify brisk walking.