Abstract

In this chapter we address the following question: Does the direction and/or magnitude of the influence of urban form on travel vary across different household types? If the answer is `yes', we can suggest the existence of interaction effects in the impact of urban form. If, on the other hand, the analysis shows no differences in the impact of urban form, this suggests that household types display similar responses to urban form, irrespective of their personal situation. In particular, we investigate differences in the effect of urban form, or residential context, on trip frequency and travel time across six household types: single workers, two- and one-worker couples, two- and one-worker families and senior households. The analysis of travel time is segmented by trip purpose: we differentiate between commuting times, `maintenance' times (e.g. trips running household errands, moving goods, shopping, giving lifts to people etc.) and leisure travel times, for several reasons. First, this broader perspective permits us to obtain better insights into the impact of urban form on travel patterns than a focus on commuting alone. Second, the number of both maintenance and leisure trips is larger than that ofcommuting trips in the Netherlands (Schwanen et al., 2001a). The data used for this analysis is derived from a nationally representative sample of the Dutch population, and stems from the 2001 Netherlands National Travel Survey

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.