Exh. C Waterfront district planned action – Scope of biennial transportation report

Exhibit C Waterfront district planned action – Scope of biennial transportation report.

The EIS identified a biennial traffic monitoring program, “traffic monitoring program,” as a mitigation strategy to monitor the traffic being generated and the mode share being achieved by development on site. The following describes the purpose of the traffic monitoring program, the data to be collected, and how the information will be used.

Purpose

The current transportation infrastructure phasing as outlined in the waterfront district transportation infrastructure phasing plan, as contained in Chapter 16.30 BMC, Article II, for the waterfront district is based on the anticipated outbound p.m. peak hour trips generated by development on site. Achieving greater non-auto mode splits, or reduced trip generation, may allow for changes to the Development Phasing Plan as the site develops over time, such as delaying or eliminating the need for certain improvements. Conversely, the inability to meet mode share targets may require a reduction in the overall level of development accommodated on site, additional transportation demand management strategies, or other improvements that are necessary to accommodate development. The traffic monitoring program for the waterfront district is intended to monitor the actual number of trips (vehicle, transit, bike, and pedestrian) being produced, the mode share being achieved, and reconfirm the timing of the infrastructure improvements and off-site mitigation.

The outcome of the traffic monitoring program will be recommendations related to the transportation infrastructure phasing as well as adjustments to the waterfront concurrency service area (CSA) to account for infrastructure improvements and mode splits. Conducting the monitoring on a biennial basis will allow parties to plan and budget appropriately for the various transportation infrastructure and mitigation needs outlined in the EIS.

Scope

The traffic monitoring program will be initiated every two years to report on the development activity that has taken place, the infrastructure that has been constructed, the amount of trips being produced by the development, and the mode share being achieved. Separate monitoring will be conducted for both the Marine Trades area and the areas south of the Whatcom Waterway due to differing on-site and off-site infrastructure needs identified for each respective development area.

The data collection will include vehicle, pedestrian, bicycle, and transit counts at each access point to the site. The data will be used to determine the current mode splits being achieved for the waterfront district as well as updated baseline vehicle forecasts for the weekday p.m. peak hour outbound traffic at each access point. The updated forecasts for the waterfront district will be compared to the transportation infrastructure phasing plan to identify if any modifications should be considered. Modifications could be in the form of delaying the timing of specific improvements or recommending modifications to the scope of the improvements. Based upon the modifications identified, the Port and the City could choose to adjust the transportation infrastructure phasing plan based on the information provided as part of the traffic monitoring program.

Data collection required

The traffic monitoring program shall collect a variety of transportation data. Table 1 outlines the type, location, and timing of data to be collected by the program. Figure 1 illustrates the specific locations for the data collection.

Table 1. Data Required for Collection
Type	Method¹	Locations²	Time Period	Date³
Intersection Vehicle Turning Movements	Manual and video data collection of intersection turning movements.	Site Access and Key Off-Site Intersections	Weekday P.M. Peak Hour (4:00 to 6:00 p.m.)	April/May or October
Daily Traffic Volumes & Vehicle Classification	Tube counts that would identify total traffic volumes as well as vehicle classifications including trucks, autos, and transit.	Site Access Locations	A minimum of three 24-hour periods during a weekday (Tues., Wed., Thur.)	April/May or October
Pedestrian and Bicycle Volumes	Conduct manual or video data collection along the access roadways for the site.	Site Access Locations	Weekday P.M. Peak Hour (4:00 to 6:00 p.m.)	April/May or October
Ridership Data	Obtain average daily ridership data from Whatcom Transportation Authority (WTA).	On-Site Bus Stops and Downtown Transit Center	Weekday P.M. Peak Hour (4:00 to 6:00 p.m.)	April/May or October
1. The monitoring program may use data collected by the City or other sources, if available, rather than collecting new data. 2. See Figure 1 for specific data collection locations. 3. Data should be collected when public schools and Western Washington University are in session.

Traffic monitoring report

The traffic monitoring program shall include the publication of a report that will be similar to a report card such as the City’s Transportation Report on Annual Concurrency (TRAC). The report will contain four main chapters as summarized in Table 2. The report will be the overall outcome of the traffic monitoring report and provide the basis for modifying the infrastructure phasing plan or the planned development capacity on site.

Table 2. Biennial Traffic Monitoring Report Outline
CHAPTER 1 Introduction/Purpose	• Provide context and summarize the intent of the monitoring report.
CHAPTER 2 Summary of Assumptions	• Land Use: Describe the existing land use within the Waterfront District as well as specific on-site developments that are anticipated to occur in the next few years. • Pipeline Development: Identify known development proposals in the vicinity of the Waterfront District (i.e., along Roeder Avenue/Chestnut Street/Holly Street between Hilton Avenue and State Street and along State Street between Chestnut Street and Wharf Street). • Transportation Infrastructure: Identify the Waterfront District transportation infrastructure that has been constructed for general vehicles, trucks, pedestrians, bicyclists, and transit. Also summarize the improvements currently funded within the next 6 years for the site and surrounding the site.
CHAPTER 3 Summary and Comparison of Data	• Data. Summarize the data that was collected. • Current Conditions. Determine the current conditions for the site including mode splits and outbound P.M. peak hour traffic volumes at each access point. • Future Development Trip Generation. Determine trip generation for the planned developments on site that were described in Chapter 2. Include pipeline development off site. Consider the updated mode splits in the calculation of the future on-site trips. • Future Trip Distribution and Assignment. Distribute and assign trips to the existing infrastructure network based on the current travel patterns, as well as the location of the planned development. • Future with Project Conditions. Calculate the future traffic volumes anticipated at each site access. • Transportation Infrastructure Phasing Plan. Compare the total site trip generation (i.e., current plus future traffic) to the infrastructure phasing table.
CHAPTER 4 Recommendations	• Transportation Infrastructure Phasing Plan. Based on the current and projected traffic data, identify needed modifications to the phasing plan or on-site development capacity, if any.

Table 2. Biennial Traffic Monitoring Report Outline

Chapter

Required Contents

CHAPTER 1

Introduction/Purpose

• Provide context and summarize the intent of the monitoring report.

CHAPTER 2

Summary of Assumptions

• Land Use: Describe the existing land use within the Waterfront District as well as specific on-site developments that are anticipated to occur in the next few years.

• Pipeline Development: Identify known development proposals in the vicinity of the Waterfront District (i.e., along Roeder Avenue/Chestnut Street/Holly Street between Hilton Avenue and State Street and along State Street between Chestnut Street and Wharf Street).

• Transportation Infrastructure: Identify the Waterfront District transportation infrastructure that has been constructed for general vehicles, trucks, pedestrians, bicyclists, and transit. Also summarize the improvements currently funded within the next 6 years for the site and surrounding the site.

CHAPTER 3

Summary and Comparison of Data

• Data. Summarize the data that was collected.

• Current Conditions. Determine the current conditions for the site including mode splits and outbound P.M. peak hour traffic volumes at each access point.

• Future Development Trip Generation. Determine trip generation for the planned developments on site that were described in Chapter 2. Include pipeline development off site. Consider the updated mode splits in the calculation of the future on-site trips.

• Future Trip Distribution and Assignment. Distribute and assign trips to the existing infrastructure network based on the current travel patterns, as well as the location of the planned development.

• Future with Project Conditions. Calculate the future traffic volumes anticipated at each site access.

• Transportation Infrastructure Phasing Plan. Compare the total site trip generation (i.e., current plus future traffic) to the infrastructure phasing table.

CHAPTER 4

Recommendations

• Transportation Infrastructure Phasing Plan. Based on the current and projected traffic data, identify needed modifications to the phasing plan or on-site development capacity, if any.

[Ord. 2013-12-091 (Exh. C)].