This page is open for editing because it is part of the Incubator. Have something to add? Please register so you can contribute. Have an option you would like to share? Please click on the 'Talk' button to enter the dialogue. The TF Resource Volunteers appreciate your feedback and interest.

Go to the Project-level traffic forecasting topic page.

Project-level forecasts must be accompanied with a document that describes how the forecast was accomplished. The document should be written in memorandum form. The document should describe these items:

  1. Project description, including the environmental setting, surrounding land uses, potentially impacted transportation facilities, and the anticipated open-to-traffic date;
  2. Project alternatives, including the do-nothing alternative;
  3. Elements of the forecasting process, including a list of techniques and models employed;
  4. Special requirements;
  5. Types and sources of data, including descriptions of networks;
  6. Methods used to process data;
  7. Sources of parameters;
  8. Base and forecast years;
  9. Time period of analysis;
  10. Problems encountered and assumptions;
  11. Scenarios;
  12. Direct results (volumes and speeds);
  13. Results of any other post-processing;
  14. An assessment of the level of confidence in any estimate; and
  15. Name and affiliation of preparer, date of preparation.

The document should be well written and sufficiently attractive for presentation at a public meeting. The document should contain a list of preparers and their affiliations, if there is more than one preparer. The document should be signed by the person responsible. Optionally, the documentation may contain a glossary or list of acronyms. An appendix should include the traffic forecast request form, as submitted.

The documentation shall be professional, “objective, impartial and impersonal” (Oregon’s “Traffic Analysis Manual”).

The report should contain maps and illustrations, such as:

  1. Study area map and boundaries;
  2. Map of surrounding highway system;
  3. Map of surrounding land use;
  4. Map showing any new site developments;
  5. Picture of the forecasting network, if any;
  6. Traffic volumes on roads;
  7. Turning movements at intersections;
  8. Details of project geometry for all alternatives, to the extent that they affect the forecast; and
  9. Details of traffic control elements for all alternatives, to the extent that they affect the forecast.

Forecasted traffic volumes, traffic speeds and other outputs should be presented in tabular form, where possible.


References