San Jose EIR Observations

I’ve now had a chance to give the EIR a pretty good run-through and I’ve compiled a laundry list of comments to submit to the City. I won’t publish those yet since I want to give it another pass. For now, I’ll list highlight items I felt were important in the document and its presentation.
First of all, it should be kept in mind at all times when reading this type of document that it is an environmental impact report, not a feasibility study and planning guide. Therefore, the authors are not making any judgments on its feasibility or cost, nor are they taking political implications into consideration.

Key assumptions are made early on:

  • The HOK-derived ballpark concept has a seating capacity of 45,000. That’s a full 10,000 more than the Wolff concept. This will become very important later on in the discussion.
  • The ballpark is built at grade, with no submerged field. This is similar to AT&T/SBC Park.
  • Traffic and noise studies are confined to the area immediately surrounding the ballpark to within roughly 1 mile of the ballpark. There is no study of the impact on southbound I-880 due to East Bay fans driving down for a game during rush hour.
  • Development alternatives consist of sites and options discussed as of early last year. The soccer stadium option, which was discussed in December 2005, is not in this document.
  • One alternative is called Existing Plan, which is based on the development strategy outlined in the Diridon/Arena strategic planning document. There is no alternative for a combination of a ballpark and elements of the planning document. While the ballpark is cited as fitting within the the scope of the Diridon/Arena plan, there is no inherent link between the two since it is not known how the ancillary development would proceed.
  • The fire training site is to be used as a combination parking structure and area for the relocated PG&E substation. Any plans for a public park would have to be moved elsewhere.

Now onto the juicy stuff.


The most impactful issue is obviously the noise factor, which has been picked by all local media. However, the noise estimates are inflated because of assumptions made on the size of the project. As noted before, the ballpark’s capacity is set at 45,000. The baseline statistical sample was data gathered by measuring noise outside Qualcomm Stadium for a Padres game where 40,000 fans were in attendance. Since the conceptual ballpark is 5,000 seats bigger, a peak noise gain of 5 dB is estimated from the Qualcomm measurements. Should the 35,000-seat ballpark be built instead of this concept, it can be assumed that peak noise could be at least 5 dB less than the figures cited in the EIR.

Delmas Park is in a bad situation when it comes to noise. It has a freeway and a light rail train immediately to the east. LRT also runs to the north. Another freeway is a mile south. Several major bus lines populate the corridors to the north and south. Jets fly in low on their final approach to the airport 1/2 mile east of the neighborhood. Freight and commuter trains rumble 1/2 mile to the west. HP Pavilion sends hundreds of cars through the neighborhood after events are completed. Finally, San Jose Water Company just received entitlements allowing it to build a planned 1,000,000 square feet of office space along with 325 homes and 3,000 parking spaces, so bring on the piledrivers.

Add a ballpark sending noise directly into the neighborhood, and the result is that the residents of Delmas Park will soon be living in cacophony if they aren’t already. Delmas Park is in a zone where a limit has been established on ambient noise – 65 dBA. Having a ballpark won’t make the neighborhood consistently louder. Instead, it will increases instances of loud noise. For instance, say a crowd at the ballpark cheers really loud 18 times per game, or twice an inning. Over a three hour game, that translates to 6 peak noise events per hour, equivalent to 6 additional jets flying overhead or 6 additional buses’ squealing brakes stopping nearby per hour. I honestly wouldn’t blame residents for being angry, especially because San Jose telegraphed this a while back when they for planning purposes expanded Downtown to include the Diridon/Arena area, yet not enough mitigation measures were taken to protect Delmas Park.

A few ideas were pitched to reduce noise and congestion:
  • Provide sound insulation for 40 affected homewoners inside the 60 dBA contour. Frankly, this should be extended to all homeowners in the neighborhood out of consideration for the impact of other development. Should the Diridon/Arena area become a true mixed-use transit hub, the noise is only going to get ratcheted up. It’s the very least they can do.
  • Utilize a distributed sound/PA system. That would probably mean that venue audio kings Meyer Sound would be out of the running, with a PA system provided by other companies like Panasonic, EV, or JBL. It’s a relatively minor issue, but Meyer Sound is a big reason why Jon Miller calls Coliseum PA announcer Roy Steele “the voice of God.”
  • Widen Delmas Ave to 2 through lanes south of W San Fernando St. This should help traffic pass through the area more quickly and has been identified as a mitigation measure for development at the SJWC site.

There are a few mitigation measures I’ve identified that could make things a lot easier for Delmas Park.

  • Shut down W San Fernando St and maybe Park Ave between Autumn St and Delmas Ave/Woz Way two hours before each game through one hour after each game to all traffic except Delmas Park residents and buses. By routing most traffic on the north-south routes in the area, traffic can flow freely around the ballpark while also preventing access for unscrupulous types looking for shortcuts through the neighborhood. This option was discussed during the scoping session, but for whatever reason didn’t make it into the document. There are problems related to shutting down Park Ave because the premium parking garage would be on the corner of Park and Autumn/Montgomery, but this could be managed.
  • Plant more trees. Sounds simple, but trees and other foliage can act as a nice sound barrier when strategically placed. That would means trees with lots of leaves, not low maintenance palms. Since a few dozen trees would need to be removed to make way for construction, why not use the buffer presented by the Autumn St/Los Gatos Creek public space to make a visually pleasing and practical sound barrier?
  • Tighten the seating bowl. The model used in the EIR is based largely off AT&T Park, which has an approximately 80-degree bowl angle that tapers in along the outfield lines. If a tighter infield angle were used (60 degrees based on the models I’m using), the bowl could better attenuate sound while providing fans in the outfield corners with closer views of the action. Examples of a tighter angle exist in Yankee Stadium and Raley Field.
  • Turn the field orientation 15 or more degrees north. Planners want to include the downtown skyline, but tilting the field in a more northerly direction can allow some noise to be directed away from Delmas Park without severely impacting the view.
  • Make a pact with the community. This would be similar to what was negotiated with residents surrounding Chicago’s Wrigley Field in which there are a limited number of night games. It doesn’t have to be that extreme, but there can be limits to the number of night concerts (15-20 estimated per year) and fireworks displays. It should be stated that sound studies don’t typically measure noise that carries due to the inversion layer or other weather factors. It’s that type of noise that caused the rash of complaints when the Rolling Stones came to SF, or when Shoreline Amphitheater opened and drove much of Palo Alto crazy.

Surprisingly, the Cahill Park/St. Leo’s neighborhoods don’t appear to be affected much by ballpark noise (see picture above: blue = ballpark 60 dBA contour, yellow = concert 60 dBA contour). This is mostly due to the field orientation as the grandstand attenuates much of the sound directed to the west and south.


There were a few more interesting nuggets I culled from the EIR:

  • The only building on the site with any significant historical value is the former KNTV Studio, which is reportedly over 50 years old. It won’t be saved should the ballpark get built.
  • At 45,000 seats, the ballpark rises 165 feet from street grade, 200 feet including scoreboards, 235 feet with light standards. It doesn’t need to be nearly that tall. A 35,000-seat ballpark would reduce or eliminate the need for a large upper deck. The models I’ve drawn up have the topmost row only 83 feet above the field. If the field were sunken 15 feet below street grade, that same row would be only 68 feet above the street, the equivalent of a 5-6 story building. The facade that fronts the concourses would be even lower. Add a roof with light standards contained beneath the roof or at the roof’s edge and the height is raised roughly 20 feet. If done in this manner, the ballpark would have less height and visual impact than HP Pavilion, which rises 100 feet from street grade. This lower profile would allow the building to comply with FAA building height requirements and limit light spill into the surrounding neighborhood. There are plenty of other tangible benefits to building lower, such as decreased materials costs, lower seismic risk, and better views for fans.
  • No community benefits are pitched because it’s an EIR. Since a park wouldn’t be possible under this plan, perhaps there’s a way to building a community center and/or gymnasium on top of the parking structure, the same way a banquet hall was placed above the Fourth Street Garage.

  • The Submerged Stadium alternative assumes digging the field 24-28 feet below ground. With a smaller first deck like the one I’ve drawn up (see picture above), it could be submerged 15 feet, which could reduce the amount of excavated dirt that would have to be hauled away and relocated by at least 25%.

All in all, plenty of good stuff in the EIR to chew on.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>