The full text to be discussed, possibly amended, and voted on at the June 3 DSNC special meeting is in this Google Doc.
I've included a copy below for accessibility. The document is also linked from the DSNC homepage.
Chris
----
Good Evening,
I may not be able to attend the ZOOM call tonight, here are a few observations/comments.
Response to the temporary and permanent Elmway design proposals:
1. The 45 degree parking option is shown, one has to dig to find the parallel parking option; even though 45 degree is used at Union Sq., it is dangerous and inappropriate to be backing into traffic (parallel parking is an inherently different process). I would stick to the parallel parking recommendation with spaces on both sides of the street, perhaps staggered to lessen the impact visually of the cars. If Uber drop zones and door dash are included that really needs to be thought thru and given consideration.
“Policing” the gig drivers is one of the biggest issues on Elm – more so than drivers.
2. Today Elm street is inherently safe because traffic gets “bogged down” and moves so slowly. The design channelizes the driving lane with the effect to accelerate drivers.
Turning radiuses are shown way too tight (I know this is not a professional engineered drawing, but the chokepoints for delivery vehicles, fire trucks and simply cars are too tight. As an example: The left side neck down at Day street makes sense as this is a right turn only intersection, but the right side should be kept wide since it is not a 90 degree angle.
Consider a short right turn only lane at Chester Street where a lot of backing up can occur (quite a few cars turn down Chester).
One thought on de-channelizing Elm would be to shift the lanes side to side with shoreways (not sure if that is the correct usage here) – see sketch below – sorry, a bit messy with my stylus :/ ) – these must be designed to not impede buses or fire trucks, but would be better (hopefully) than speedbumps.
A final design would be nice to lift the street to match the sidewalk height (and material) so that when the street is closed for special events it feels like a plaza – using bollards to separate traffic and pedestrians. The main plaza at the new high school was designed this way , Denver 16th street mall operates similarly on a much larger scale.
3. A bike lane is warranted here. Thinking about the entire square we should assume the intersection in front of the Somerville Theater will also someday get improvements – it’s a tight spot for bikes when both lanes are taken.
Note that the through drive lane is the left side lane from Highland Ave eastbound and should be the lane that carries straight on to Elm…
I personally don’t prefer the flex posts as a biker in these tight area – a bike also needs to be able to get out of tight situations – so a painted lane should suffice and make things feel less tight.
There are many Urban design studies that show most pedestrian only streets are failures – I think Elm succeeds as a temporary closure for special events and hopefully planted with better green areas and hardscape materials (and well maintained).
The city has a great mobility and engineering team – ultimately we should propose but also listen to them, the fire dept., and business owners.
I personally liked the 4 way intersection design from a few years back, two-way streets are slower and safer here. If the goal is to limit “drive-through” commuters cutting through the square but never stopping, then cutting off Dover street certainly would accomplish that…. And create much larger pedestrian islands at the heart of the square.
Regards,
Alex
--
Davis Square Neighborhood Council · https://DavisSquareNC.org · https://linktr.ee/DavisSquareNC
---
You received this message because you are subscribed to the Google Groups "Davis Square Neighborhood Council" group.
To unsubscribe from this group and stop receiving emails from it, send an email to davissquaren...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/davissquarenc/CAEK62JdiVyGc--HoLEZXeADqM2jF_5m10W03vtSd9w2USGJs5A%40mail.gmail.com.