Click for next page ( 41

The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 40
40 BENEFIT-COST ANALYSIS TOOL mation that the tool requires depends on the different char- acteristics of the facility that the tool is analyzing. The fol- The guidelines, titled Benefit-Cost Analysis of Bicycle lowing is the detailed logic tree that tool goes through for the Facilities, can be found at general input portion of the tool. bikecost/. These guidelines provide planners, policy officials, The user is prompted by the following general inputs: and decisionmakers with the ability to use a standard method to analyze the costs, benefits, and induced demand associated with a planned bike facility in their community. These guide- 1. Are you interested in: Costs, Demand, Benefits? Or a lines allow the user the ability to tailor the information to a combination of the three? particular project. Figure 2 presents a brief outline of the 2. In which metro area will the facility be located? Central sequence of logic and process contained within the web-based city or Suburb? guidelines. 3. Mid-year of project? The guidelines include useful accompaniments such as 4. Type of facility? "i" buttons and a "Bicyclopedia." The "i" buttons help a. On-street with parking explain variables so that the user can better understand the 1. Restripe information that is being requested (Figure 3). The Bicy- 2. Overlay clopedia comprises a glossary of terms, a guide on how to 3. Full Depth use the guidelines, and a brief description of the method- 4. Signed Route ology that was used to develop the guidelines. The expla- b. On-street without parking nations associated with the "i" buttons and the glossary 1. Restripe appear in separate popup windows so that data entered by 2. Overlay the user are retained. 3. Full Depth 4. Signed Route c. Off-street General Inputs 1. Stone trail 2. Asphalt trail When determining the benefits and costs of a bicycle facil- 3. Concrete Trail ity, the guidelines allow the user to tailor the outputs to the d. Bicycle-Related Equipment specific project that is being proposed. The user first selects a metropolitan area. Second, the user specifies if the proposed facility will be located in the city or suburbs (Figure 4). Such Costs options allow the user to tailor output to local conditions. The user is asked to specify characteristics of the project that is The guidelines prompt the user to select various features of being proposed. Options include on-street bicycle lanes with a trail such as dimensions, signals, landscaping, and materials or without parking, off-street bicycle trails, and bicycle-related used for the trail. The guidelines provide the user the ability equipment. to enter a cost for various features or to use default settings as During the general input portion of the tool, it prompts the outlined in Chapter 1 of this report (see Figure 5). Based on user for information about the proposed facility. The infor- such inputs, the tool calculates the cost of the facility. Costs / Demand / Benefits General Inputs Cost Worksheet Demand / Benefits Inputs Output: Output: Output: Capital cost $ Benefits # of New Annual maintenance cost Cyclists Figure 2. Flow chart showing structure of the guidelines.

OCR for page 40
41 Figure 3. Information from "i" buttons explaining the input variables provided in separate popup windows. Figure 4. General inputs.