
The following was emailed to members of the Open Space and Habitat Commission (OSHC) on Sunday. The OSHC is scheduled to discuss the revised MRIC/ARC/DISC project, now dubbed DiSC 2022, at its Monday Oct 4 meeting. If you wish to comment on the project yourself, see instructions on the agenda for the meeting, located here.
Dear members of the Open Space and Habitat Commission,
I am writing to you as a former commissioner (10+ years) and Chair of the OSHC, having completed my term last December. I was involved in analyzing what is now being called the DiSC 2022 project in all of iterations, so I hope you find my comments helpful in your discussions.
To begin, I am pleased to see in the minutes from your last meeting the following: "[Ms. Reynolds] said the Commission also had the option of agendizing the Addendum to the project's Environmental Impact Report ("EIR") later this year if the Commission wanted to provide comments on the Addendum to the EIR. That meeting would have to happen before December when the project is scheduled to go before the Planning Commission, she said." I strongly urge you to do this. The OSHC has a history of productively discussing and giving comments on EIRs, as it did with earlier versions of DISC as well as Nishi and other projects, with the comments thoughtfully crafted from the Commission carrying more weight than comments from individual members. For example, you might wish to ensure that the biological surveys have been properly updated and that greater awareness of approaches to climate change are being taken into account, such as the lost opportunity for regenerative agriculture on the property if the project is built.
Another important piece of background: in the last iteration of the project, the developer kept insisting that Mace 25 was not part of project, even though it clearly was. This led to mistrust in the community. Because of that mistrust, people are now concerned that this smaller project without Mace 25 is just a foot in the door for the already rejected larger project to come later. I urge you to recommend that the developer state, as a sign of good faith, that this is not their intention — designating the ~100 acres to the north of the project as ag mitigation would be the clearest way to do that.
The rest of my remarks will focus on the Staff Report and related attachments, located online here.









On July 1st Davis Vanguard covered the announcement of Federal funding of 86 million dollars for the Yolo-80 Managed Lanes project.
I appreciate most the comments of Alan Miller, Alan Pryor and Richard McCann. I hope I can add something below.
The MTC area gets a lot of income from its bridges, and uses it for public transportation. Consider that Davis and SACOG-area drivers pay into this when driving south to San Jose, west to Oakland and San Francisco, and so on, but people from those areas make no similar contribution our region – really, the east side of the Northern California Megaregion – when traveling to Davis or Sac or of course towards Lake Tahoe.
Caltrans dropped the long-promised new bike-ped bridge across the Bypass, replaced by some improvements on the west side of the Bypass. Combined with new infrastructure such as separated lanes and a lot of shade trees in West Sac, the whole corridor could be optimized for faster e-bikes and provide a good alternative for many, especially in east and the east part of South Davis. But… nope! Or so it seems.
The graphics in the Caltrans presentation on the Yolo 80 Corridor planned for the BTSSC meeting this Thursday show only buses in the managed lanes, which is not what’s really planned for the managed lanes. Nasty! The managed lanes are mostly in added lanes, and if these lanes are available for private vehicles off-peak, for a premium, or free for a carpool then induced demand happens – see also Alan Pryor's comment in the Vanguard article – and we eventually lose.
It’s also not clear how this project interfaces with the 80-Richards project.
It’s not clear how much congestion there will be during the long construction period.
It’s not clear if any general re-paving will decrease noise (new technology makes this possible).
It’s probably unlikely that Caltrans will support a discount on Capitol Corridor during the construction period.
But yeah, rail. What’s up with the future Capitol Corridor improvements? How does this project related to our impending new General Plan? My favorite idea is to build a highway bypass south of town and then put the railway below grade so that it also no long splits the City in two (in retrospect, it would probably have been better to not build anything south of the 80-rail corridor). Anyway, all the new space roughly in the center of Davis could be the location of a lot of new dense, mixed-use development which could facilitate low-vehicle ownership or at least use, as it would eventually be convenient to UCD and Downtown by bike, to both Sacramento and especially the Railyards, and to points to the west by rail. It would also be much quieter in parts of the City with this sort of ring-road solution. In general terms it would complement my concept for building above 113 roughly between Russell and Covell. I've also proposed a noise-mitigation and solar-generation project for the I-80 corridor through Davis.
Related to this whole thing and that next to last point, over three years ago when I was on the BTSSC I initiated a sub-committee on 80 and related. It never went anywhere and was dissolved as the other Commissioner who joined it moved to Sacramento and no one else on the Commission wanted to pursue this… route. Sigh. Please demand that BTSSC members ask some hard questions this Thursday!