Traffic Data and Projections. The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TPP traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP’s comments.
Traffic Data and Projections. The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. . The Engineer shall collect 00-xxxx xx-xxxxxxxxxxx/xxx xxx approach traffic volume counts as needed for turning movements at intersections. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for DocuSign Envelope ID: 211A8780-3A56-4C71-A0A9-95EA90C5E646 inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TPP traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP’s comments. The Engineer shall perform traffic operational analyses for all mainlane, ramps and frontage roads within the added project limits using the Highway Capacity Software and utilizing Synchro for the intersections. The analysis will be performed for the future peak hour AM and PM no-build and one (1) build alternative for opening and design years. Capacity analysis will be used to determine future levels of service in the no-build and one (1) build alternative networks. The Engineer shall develop recommendations from operational analyses and incorporate them into one technical memorandum for the project. It is assumed that there will be one round of comments which will result in a Draft and Final Report. Traffic analysis technical memorandum will include the following sections: Introduction Methodology Traffic Analysis Turn Bay Recommendations at the added intersections Summary of Conclusions and Recommendations
Traffic Data and Projections. The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TPP traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP’s comments. To accomplish this effort the Engineer will: The Engineer will calibrate/validate the base year model. This is an iterative process that involves the execution of the travel demand models, comparison of modeled traffic volumes to observed counts, adjusting the travel demand models, and repeating the process until acceptable match is obtained.
A. Obtain regional Travel Demand Model (TDM)
B. Detail code the roadway network within the study limits C. Develop and apply regional impedance factor to offset additional impedances created by detail coding the study area
Traffic Data and Projections. Obtain from the City the 2017 and design-year (opening year +20) travel forecasts, and related traffic analysis. The developed traffic projections shall be utilized for design and environmental analysis. Obtain traffic counts for side streets for use in determining median openings. Obtain traffic forecasts for the lanes, cross streets, and intersections, for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table.
Traffic Data and Projections. The Engineer shall develop the opening-year (2020), design-year (2040) and pavement design year (2050) travel forecasts, and related traffic analysis in coordination with State Transportation Planning and Programming Division (TP&P). Existing turning movement counts (TMC’s) will be collected for the AM and PM peak hours at signalized intersections along LP 1604. These TMC’s will be useful in the development of the traffic data projections and modeling of current conditions. The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for LP 0000, xxxxx xxxxxxx, interchanges at FM 143, East- West Connector (City of San Antonio (COSA), Metropolitan Transportation Plan (MTP)), Union Pacific Railroad (UPRR) /Macdona-Lacoste Road, Xxxxxxxx Road, UPRR/Xxxxxxxx Road and at IH 35, for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare Line diagrams of existing and proposed conditions to submit to TP&P for traffic projections. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TP&P traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TP&P for review and approval, and the Engineer will revise the traffic volumes based on TP&P’s comments. DocuSign Envelope ID: ED57FAE2-481A-4535-A126-CE7F0E526760
Traffic Data and Projections. The Engineer shall develop the opening-year (2020), design-year (2040) and pavement design year (2050) travel forecasts, and related traffic analysis in coordination with State Transportation Planning and Programming Division (TPP). Existing turning movement counts (TMC’s) will be collected for the AM and PM peak hours at signalized intersections and major cross streets along LP 1604. These TMC’s will be useful in the development of the traffic data projections and modeling of current conditions. The Engineer will collect 24 hour classification volumes at three (3) locations along Loop 1604 to provide daily traffic and percent trucks for existing conditions. The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for LP 1604, interchanges at US 281 and IH 37, and cross streets at FM 3499, Cambellton Road, Priest DocuSign Envelope ID: 719137B1-7E3D-42BC-8A29-9D6AE732CB6A
Traffic Data and Projections. The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) traffic data projections. The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes for ultimate conditions (opening and design year) and interim conditions (opening and design year). These projections shall include graphic representations of the anticipated ADT movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. Traffic DocuSign Envelope ID: 08011FCF-93C2-4F54-8A05-20A33047A1D8 volumes developed by the Engineer will be submitted to TxDOT for review and approval, and the Engineer will revise the traffic volumes based on TxDOTs comments.
Traffic Data and Projections. The Engineer shall obtain the base year traffic data from new counts and develop the opening- year, design-year (opening year +20), and pavement design year (opening year + 30) travel forecasts for the AM peak hour, PM peak hour, and 24-hour scenarios. The following traffic data locations shall be obtained on a Tuesday, Wednesday, or Thursday: • 4-Hr Turning Movement Counts (7-9 AM and 4-6 PM) o Goforth Road at Xxxxxx Creek Road o Lehman High School Driveway west of Lake Washington Drive o Lehman High School Driveway east of Lake Washington Drive • 24-Hr Bidirectional Tube Count o Bunton Creek Road west of Xxxxxx Circle o Xxxxxx Xxxx east of Twin Estate Drive The Owner shall provide information regarding proposed developments near the study area that have not yet been built. Traffic forecasts shall consider the traffic generated by these proposed developments. The developed traffic projections must be utilized for design analysis. The Engineer shall develop traffic forecasts for the mainlanes and intersections listed in this section for no-build and build alternatives. Traffic projections for the AM peak hour, PM peak hour, and 24-hour shall be presented graphically.
Traffic Data and Projections. The Engineer shall provide additional engineering services to update the development of the opening-year (2020), design-year (2040); and pavement design year (2050) travel forecasts, and related traffic analysis in coordination with the TxDOT Transportation Planning and Programming Division (TP&P) The Engineer shall collect existing turning movement counts (TMC) for the AM and PM peak hours at signalized intersections along LP 1604. Using these TMC’s the Engineer shall develop traffic data projections and modeling of current conditions. The Engineer shall use the developed traffic projections for design and environmental analysis. The Engineer shall develop traffic forecasts for both the no-build alternatives for LP 0000, xxxxx xxxxxxx, and DocuSign Envelope ID: 1DB60CEF-DAD9-4F47-8AE2-182BB19769B8 interchanges at:
(1) FM 143 (2) East-West Connectors
Traffic Data and Projections. The Engineer shall provide existing traffic counts. The Engineer shall perform an Origin/Destination Analysis of the IH35W/IH20 and IH 35W/SH 174 interchanges. The Engineer shall develop base year 2025, interim year, and design year 2045 daily and a.m. and p.m. peak travel forecasts for the No-Build Conditions, corridor alternatives and geometric design schematic of the preferred alternative including all upstream/downstream interchanges within the study area. These traffic forecasts shall be prepared from a corridor model in coordination with North Central Texas Council of DocuSign Envelope ID: B4E47CBB-54AA-4467-B86B-B1C47B94F45E
