City of Sac blind adherence to ADT

Dan Allison2 Comments

Another post on the Freeport Blvd Transportation Plan. See the category Freeport Blvd for other posts.

“We are designing for the traffic we have, not for the traffic we want.”

Ali Doerr Westbrook, Chair of Sacramento Active Transportation Commission

I could stop at that, but perhaps you’d like some more detail. This comment was made during the Sacramento Active Transportation Commission (SacATC) meeting on January 18, 2023. The context was the admission by the two city planners, Leslie Mancebo and Jennifer Donlon Wyant, that the city eliminated the possibility of a road diet (roadway reallocation) before even starting planning for Freeport Blvd. The reason expressed is that the ADT (Average Daily Traffic count) is above 20,000 for Freeport, and that requires more than two lanes (one each direction). Interestingly, ADT counts for various locations along Freeport are nowhere to be found in the plan or appendices. In a different location on the City of Sacramento website, Traffic Counts, the ADT for various locations along Freeport Blvd, rarely exceed 20,000, and have not exceeded 20,000 since 2011. There is no indication that the city even did new traffic counts in preparation for this planning effort. So far as can be determined, they just decided to not consider a road diet from four lanes to two lanes, or two+one lanes, 3/2 configuration) because they wanted to prioritize motor vehicle traffic over all other uses of the roadway.

The city planners also acknowledged that a road diet was a prominent request of the community during the planning process. But, community input be damned, the city is going to serve car drivers before anyone else.

A reduction of lanes from four to two is the single most important traffic calming effort that can be made on a roadway. That does not mean it is the appropriate solution for Freeport Blvd, or for all of Freeport Blvd in the planning area. What is does mean is the that city should have considered it in the planning process.

Back to Ali’s comment. The city is planning for a roadway configuration that should have already been in place years ago, before the city over-widened the roadway, and in several cases narrowed sidewalks to accommodate the widening. They are not planning for a roadway which would reduce vehicle miles traveled (VMT) or increase safety and access for those outside cars. The city’s responsibility, under the Mayors Commission on Climate Change report, is to reduce VMT in order to reduce greenhouse gas emissions (GHG), not to maintain VMT at current levels. But this Freeport plan is a plan to guarantee current VMT for at least 30 years in the future, which is about the length of time before the city will be able to reconstruct the roadway again, and correct the mistakes they made this time around.

The intent of the city in this plan is made very clear in the common design principles: “10. Maintained necessary travel lanes, turn lanes, and parking: Maintaining travel lanes and turn lanes ensures that drivers traveling along the corridor will not be compromised, and preserving parking spaces where 5 the utilization is higher so it serves better adjoining businesses.” Though this is the last item in the list of ten, it is clear that this is the highest priority for the city.

The refusal to consider a road diet/lane reduction/roadway reallocation is a fatal flaw in this plan. The effort should be sent back to staff to re-do. It should not be adopted by city council. If the city council does not reject this kind of flawed planning, city staff will continue to make the same mistake, again and again and again.

I’ll post on some of the other flaws in the plan, but this is the most important, not just because it misses the best opportunity for traffic calming, but because it retains roadway width for the exclusive use of motor vehicles that could be better used for walking, bicycling, trees, and even parking for businesses.

Added graphic below, which I had not noticed in the plan, that documents vehicular counts on sections of Freeport Blvd. Is it suspicious that half of the plan area is ‘just’ over the city’s criteria of 20,000 ADT? Remember, the plan itself and the city’s traffic counts website do not indicate this level of ADT.

Freeport Blvd Transportation Plan

Dan Allison11 Comments

The City of Sacramento has released the final draft Freeport Blvd Transportation Plan. Appendix F Design Layouts is a key part of the document. This post reflects my original comments (Freeport Boulevard Emerging Design Concepts) and the new plan. The city’s plan page is at http://www.cityofsacramento.org/Public-Works/Transportation/Planning-Projects/Freeport-Blvd-Corridor. The plan is on the Active Transportation Commission agenda for January 20, 2023, and will go to the city council within the next two months.

The ten common design elements on page 21 (24 of the pdf) include: “10. Maintained necessary travel lanes, turn lanes, and parking: Maintaining travel lanes and turn lanes ensures that drivers traveling along the corridor will not be compromised, and preserving parking spaces where 5 the utilization is higher so it serves better adjoining businesses.” This is statement is contrary to all walkability, bikeability and vision zero goals. It should be removed from the document, and removed from planning goals. It is offensive. It means that no matter what other improvements to the corridor will be made, cars and motor vehicle drivers will be preferenced over all others.

The ten common design elements do not mention trees. Trees are an integral part of the walking experience, as well as providing climate and heat island benefits. They should be prominently recognized throughout the document, but they are not. The phrase ‘existing trees’ occurs many time in the document, but nowhere are ‘proposed trees’ identified.

Frequent driveways along much of this section present hazards to walkers and bicyclists, and handicap the design of safe streets. It is clear that the city did not consider reduction or narrowing of driveways to address this hazard. If you look at the design layouts (Appendix F), the number of gaps in the bikeway, shown as dashed green, is remarkable. Each of these is a driveway. Again, this is a clear indication that the city intended to maintain the car-dominated character of this street.

All crosswalks at intersections should contain all three or four legs (three for T-intersections). The design leaves many intersections with only one crosswalk over Freeport Blvd, meaning pedestrians must cross three streets in order to reach some destinations, rather than just one. Though not mentioned in the plan, this often means installing pedestrian crossing prohibition signs and barriers. These should be outlawed, not encouraged.

North Section

pages 25-26 (28-29 in the pdf)

The intersection of Sutterville Road to the east with Freeport Blvd is shown with a two-lane roundabout. Two lane roundabouts have almost none of the traffic calming and safety benefits of one lane roundabouts, in fact they should not even be called roundabouts, with the implication that they have safety benefits. This roundabout should be redesigned to a single-lane. Traffic levels on Freeport to the north certainly do not justify two lanes, in fact Freeport become single lane each direction a short distance to the north at 13th Avenue.

The dedicated right turn lane on Freeport Blvd southbound at Sutterville Road to the west is not needed and presents an unnecessary hazard to bicyclists. Dedicated right turn lanes should be eliminated from this plan, and from all city roadways. They are rarely justified by traffic volume, create conflicts for bicyclists, and widen roadways and therefore crossing distances for walkers. They also encourage drivers to make right hand turns without looking for people walking.

There should be a crosswalk on the north side of the Freeport-Sutterville intersection. There is no justification for leaving it out, unless an attempt to discourage walkers from accessing the park.

South Section

pages 27-31 (30-34 in the pdf)

The offset crosswalks with median refuge at Oregon Drive and Potrero Way/Virginia Way are a good design, but there is no reason to not provide crosswalks on the other leg of the intersection.

The median gap at Arica Way, with dedicated left turn lanes, is not needed. Arica Way is a low volume street that is a good candidate for right in/right out treatment. The shopping center access can be provided for northbound traffic.

At the intersection of Fruitridge Blvd and Freeport, there should be no dedicated right turn lanes. They create a hazard for bicyclists, that cannot be mitigated by pavement marking, and they lengthen the crossing distance for walkers. In this location, where center refuge medians are not proposed, this is particularly egregious. The dual left turn lanes southbound on Freeport are a hazard to bicyclists and motor vehicles, and should be reduced to a single left turn lane. This intersection, due to long crossing distances, should provide center refuge medians on both the north and south crosswalks.

Northgate Blvd Transportation Plan

Dan Allison1 Comment

The City of Sacramento has released the final draft Northgate Blvd Transportation Plan. Appendix F Layout Designs is a key part of the plan. This post reflects my original comments (Northgate Boulevard Emerging Design Concepts) and the new plan. The city’s plan page is at http://www.cityofsacramento.org/Public-Works/Transportation/Planning-Projects/NorthgateMobility. The plan is on the Active Transportation Commission agenda for January 20, 2023, and will go to the city council within the next two months.

Travel Lanes

The most important aspect to the plan is that travel lanes (general purpose lanes) have been reduced from two each direction to one each direction. A reduction of lanes and narrowing of lanes (from 12 feet or more to 11 feet) is probably the single most effective action for calming traffic. When there is a single lane, the prudent driver who is traveling at or near the speed limit controls the behavior of other drivers, many of which would be traveling at excessive and incredibly dangerous speeds.

Trees?

Of the 10 common design elements on page 20 (23 of the pdf), none are about trees. Yet the lack of trees and shade for walking was a major issue in community input. The city has a tendency to minimize trees in transportation planning, because they are a detail beneath the interest of traffic engineers, and the city doesn’t want responsibility for maintaining street trees. Trees are often treated on the standard timeline of it is either a) too soon to address that (which was the response to early plans lack of attention to trees), or b) decisions already made so it is too late to address that (which will be the answer on trees now). Yet trees are a critical element of walkability, and walkability is a critical element of economic vitality. No trees, no walkers, no economic vitality.

On page 26 (29 of the pdf), the proposed cross-section does not show any trees within the public right-of-way, only on private property. Sidewalks are shown as eight feet, which is great, but without trees, many fewer people will walk there than if there were trees for shade. The wide-open viewshed also encourages higher speed driving, counteracting efforts to reduce speed.

Driveways?

One of the unfortunate aspects of the corridor is the prevalence of driveways. In most cases, each and every business has its own driveway or driveways, and its own parking. That is a characteristic of how the area developed, and in some ways it is a strength, because many small businesses make for a more vibrant economy (not to mention higher property tax and sales tax income). But crossing driveways are also the biggest impediment to a safe and welcoming walk, and to bicycling.

The city seems to have decided that it is not worthwhile addressing the number of curb cuts for driveways. The plan acknowledges wide and number driveways, but offers no solution.

Page 28 (31 of the pdf) shows a diagram for Wilson Avenue intersection. In just this short section, three properties are shown as having double in-out driveways for a single business. Not only is this unnecessary interruption of the sidewalk, but an interruption of the bikeway (green color in the diagram).

I believe the city should proactively reduce driveways by eliminating all double in-out driveways. It could be left to the property owner or business to decide if they want to have one in driveway and one out driveway, or a wider in-out driveway, though clearly one in-out is better for walkers and bicyclists.

more Sac failure to properly mark/sign ADA for construction

Dan AllisonLeave a comment

Note: This post was developed in October 2022 but not posted at that time due to an oversight. It is still useful.

There is a new construction project at N St & 14th St in the Sacramento central city, opposite Capitol Park. The project, called Cypress, is a CADA project for multi-family housing, but I do not know the lead construction company. The site has been fenced along N St and 14th St (address is 1330 N St), and across Neighbors Alley. Along N St, the sidewalk is closed at the project, and the crosswalk over 14th St is closed at the southeast corner. Along 14th St, the crosswalk over N St is closed at the north side, and the sidewalk is closed at a property south of the alley.

As is usual for a project permitted by the City of Sacramento, either the traffic control plan was written to allow violation of ADA, or the company has not followed the plan. Or both.

The photos below show the failures.

construction barrier not ADA at 14th St crosswalk
14th St at N St crosswalk, southeast corner, construction barrier not ADA

At this location, the barrier is not ADA compliant. The bottom bar must be no more than six inches from the ground, at bottom, so that it is detectable by a person using a cane. The barrier footing is a trip hazard for both unsighted and sighted persons.

construction barrier not ADA at N St crosswalk
N St croswalk at 14th St, construction barrier not ADA
Read More »

SacATC meeting Jan 19 with report, Northgate, Freeport

Dan Allison2 Comments

Update: The letter on the status of walking/biking was deferred to the next meeting, where a modified letter will be considered and hopefully passed. The Freeport and Northgate Transportation Plans were forwarded to council. I spoke in favor of Northgate and against Freeport, for reasons I will detail in the near future. The applications for planning grants were supported.

The Sacramento Active Transportation Commission (SacATC) is meeting online Thursday, January 18, 2023, 6:00PM to about 8:00PM, via Zoom. See http://sacramento.granicus.com/ViewPublisher.php?view_id=21 for agenda and eComment.

The three main topics are:

A read of the subcommittee report, formatted as a letter to the mayor since the commission is advisory to the council, is good and should be supported. I particularly like the emphasis on completing the construction detour policy, since city staff otherwise do not care about the safety of walkers and bicyclists in navigating construction projects that close or change sidewalks and bikeways. Two items missing are bike/scooter share, and Vision Zero. These two items may or may not fall under the purview of SacATC, however, the city is not making information available to the public on these efforts, so it seems to fall to SacATC to do so.

In general, the Northgate and Freeport plans are an immense improvement over existing conditions, so meet needs of the moment, but it is less clear they are going to meet the needs of the future, which will be much less private motor vehicle driving, and more walking, bicycling and transit. If time is available to look at the plans more closely, I’ll add posts.

Sacramento disdains walkers

Dan Allison3 Comments

The City of Sacramento, both the city government and many people who live here, have a picture of a pretty good place to live, and work, and play. And that is true, to some degree. Good climate (except middle of summer), a wealth of trees, interesting and useful businesses (at least in midtown), mostly flat (for bicyclists), two rivers and the confluence, moderately friendly people. But the transportation network sucks.

Heavy rain of course brings out the flaws in the transportation system. Flooded roadways that at the least make it hard to get places, and at worst kill people. Trees and tree debris blocking both sidewalks and bike lanes. Light rail that runs late or not at all, buses behind schedule. All of those are important issues. But this post is about flooded ADA ramps.

flooded ADA ramp, Q St at 13th St
flooded ADA ramp, Q St at 13th St

The above photo is a mild case, as it does not make the ADA ramp and connecting sidewalks impassible. It just means wet feet for people who can’t jump the puddle, or wet wheels for people with mobility devices. You might think that this is a problem created by the storms. But look closer. The ADA ramp was built so that it is LOWER than the drain inlet. This puddle will remain until it evaporates, and if the rain continues, it will be there for quite some while. There are two explanations, and I don’t know which is correct. 1) The ramp and drain inlet was designed by an incompetent engineer; or 2) ramp and drain inlet were not built as designed, meaning that the construction inspector did not notice or did not care that it was not installed as designed. In either case, it is the fault of the city.

You might think that this is an unusual circumstance, but if you walk and notice, about half the ADA ramps in the city have this same problem. Why is this so common? Because the city doesn’t care. The engineer doesn’t care, or the inspector doesn’t care. Every one of these situations expresses the city’s disdain for walkers, and users of mobility devices.

I started with a mild example, but to present a much worse example:

flooded ADA ramp and sidewalk, 3rd St at O St
flooded ADA ramp and sidewalk, 3rd St at O St

This puddle won’t disappear for at least a week, even without additional rain. This is not a problem of a plugged drain inlet. The ramp and sidewalk was designed to be BELOW the gutter level along the street.

I have reported this location multiple times to the city, over the years. It has never been fixed. When I submit a 311 report, it is marked as complete without anything being done. Which is not untypical for the city, most of my 311 reports are ignored, marked as complete without anything being done.

Does this bother you? Get in touch with your city council member, provide photos and stories about how this impacts you and the people you know. Ask council members to hold city staff responsible for their incompetence and lack of care. If the city manager can’t fix these problems, it is time for a new city manager. If Public Works can’t fix this problem, it is time for a new head of Public Works. Anything else is not acceptable.

Measure A fails, and mapping

Dan Allison3 Comments

Measure A, the transportation sales tax for Sacramento County, failed spectacularly, 44% yes and 55% no. Advocates for a better, safer, more equitable transportation, and better investment of our transportation dollars, celebrate this failure. Final election results were released on December 8, 2022.

Sacramento County Measure A 2022 results

More analysis of the results and significance to come, but for now, some maps.

Sacramento County Elections provided a map of the Measure A results.

Sacramento County Elections, Measure A 2022 map

Sacramento Bee provided a similar though not identical map.

SacBee Measure A 2022 map

Both these maps indicate whether a precinct voted yes or no, but no indication of the number of voters or the proportion of the vote yes or no. There is a movement towards better election reporting maps, called ‘Land Doesn’t Vote, People Vote’. A few references are U.S. election maps are wildly misleading, so this designer fixed them, Election graphics 2020: Land (still) doesn’t vote, and Land Doesn’t Vote, People Do: This Electoral Map Tells the Real Story, but you can find many more.

Below is my first attempt at producing a better map for Measure A. Click on the graphic for a linked pdf, which allows you to zoom in on specific areas. What’s different? I used a range of colors, from red (no) to green (yes) votes (ArcGIS: graduated colors, equal interval, 10 classes). You can see there is much more subtle detail. There were a few precincts which voted entirely no or entirely yes, but very few. Most were somewhere in between. For elections (other than the antique federal electoral college), votes count, precincts do not.

The map still over-emphasizes precincts with large area and few voters (some precincts have as few as one person who actually voted). If you look (unfocus your eyes), you would think that there were almost no ‘yes’ votes in the county, but that is not accurate.

The data I used, modified from the Sacramento County Elections data, is here.

Measure A 2022 mp by Dan Allison, graduated colors

Some of the other map alternatives, which are better, require ArcGIS techniques and skills that I’m just looking into, so I expect I’ll have better maps soon. Stay tuned!

Sac region does well on ATP grants

Dan Allison1 Comment

The California Transportation Commission (CTC) adopted the staff recommendations for funding Active Tranportation Program (ATP) grant applications. The Sacramento region did well, with seven grants awarded. Sacramento County received two, City of Sacramento two, Rancho Cordova one, West Sacramento one, and Placerville one. More detailed descriptions of these projects will be available on the CTC ATP or Caltrans websites.

CTC ATP awards for Sacramento region

The SACOG announcements will be made later, and there may be additional projects awarded that did not make the state-level cutoff of 89/100.

the worst ADA violation in Sacramento?

Dan AllisonLeave a comment

Let me say up front that there is a lot of competition for ‘the worst’, but I think the sidewalk and other construction on Capitol Ave between 16th St and 17th St is certainly in the running.

What are the issues?

  • No advance warning of sidewalk closure at the preceding corners on 17th St.
  • No ADA detectable barrier. The project is using chain link fencing with yellow caution tape strung through the fence.
  • Fence bases protrude into the sidewalk, presenting a tripping hazard for blind or low vision persons, or anyone at night.
  • No appropriate ‘sidewalk closed’ sign at the point of closure.
  • Both sides of Capitol Ave have closed sidewalks, so there is no choice between sides of street.
  • The small sign on the fences at 16th St indicate very long detours to reach the entrances of both 1616 Capitol Ave (south side) and 1615 Capitol Ave (north side). Photo below. This sign of course would be of absolutely no use for someone with impaired vision, or anyone on a dark day or early in the morning or late afternoon (at this time of year).
  • The bike lanes on both sides of Capitol are partially obstructed by fencing. No signing for bicyclists or drivers indicates this. Bicyclists have to merge away from the fencing into the general purpose lane, with no advance warning.

This is a California Department of General Services (DGS) project, and signing indicates that the construction contractor is Z Squared. I have reported these violations to both the City of Sacramento 311 (case 221130-1423348) and DGS Facilities Management Division.

It is worth noting that his current construction seems to be part of an ongoing construction project that was stalled for about a year. DGS removed the rocks from a sidewalk adjacent area meant to protect walkers from walking into the awkward building buttresses, then fenced these areas. About a year ago. Then, nothing.

There is also construction going on Capitol Ave between 15th and 16th, but I was so depressed by this one that I didn’t include it.

1616 Capitol Ave construction blocking sidewalk
1616 Capitol Ave construction blocking sidewalk
1615 Capitol Ave construction blocking sidewalk
1615 Capitol Ave construction blocking sidewalk
Capitol Ave at 16th St construction blocking sidewalk, north
Capitol Ave at 16th St construction blocking sidewalk, north
Capitol Ave at 16th St construction blocking sidewalk, south
Capitol Ave at 16th St construction blocking sidewalk, south
Capitol Ave detour signing for pedestrians
Capitol Ave detour signing for pedestrians

lower speed limits on complete streets in Sac

Dan Allison1 Comment

The eternal argument on speed limits has resurfaced on Twitter. The binary solution is: a) lower speed limits, or b) redesign roadways. This is a false dichotomy, to which I answer yes! Ultimately, the solution is to redesign roads (and motor vehicles) so as to physically enforce posted speed limits. But in the meanwhile, speed limits that are posted too high for urban areas (and with speeds that alway exceed that, because the road was designed for a higher speed than is posted) should be reduced.

There are two types of speed: posted speed, on the speed limit sign, and design speed, the speed that the road was designed for. Design speeds have traditionally been much higher than posted speeds, at least 10 mph higher, and often more, because the traffic engineer’s value system says that we must always protect drivers from their errors by providing a road that is safer at higher speeds. This is highway design thinking, applied to city streets, and is always inappropriate outside freeways and rural roads (and maybe even there). Protecting other users of the road (walkers and bicyclists) does not traditionally figure into this at all.

As a starting point, local or residential streets should be 20 mph maximum, collector streets 30 mph maximum, and arterial streets 40 mph maximum. These are maximums, more than is appropriate for many roads. 40 mph may never be appropriate in an urban area. Of course most arterial streets are stroads, roads designed for higher speeds but then knee-capped my multiple driveways and intersections. These roads should never have been built that way, or allowed to evolve that way, and must be radically changed.

Existing posted speed limits for the city are available.

It should be noted that most research indicates that the majority of fatality and severe injury crashes are caused by people egregiously exceeding speed limits, by 10 mph or more. It is not unusual for speed surveys, and the rare law enforcement, to record a few drivers exceeding freeways speeds on surface streets. Roadway design, along with lower speed limits, probably does little to change the behavior of egregious speeders, and those are better addressed through automated enforcement.

The City of Sacramento has a number of complete streets or road reconstruction projects underway or planned. Two significant ones are Northgate Blvd and Stockton Blvd. Stockton is on the city’s high injury corridor Vision Zero plan, Northgate is not.

Stockton Blvd

The city has been through several cycles of planning for Broadway and Stockton Blvd. The current plan is the Stockton Blvd Plan – Community Working Version. Though public concerns about motor vehicle speed have been a recurring theme, the city plans to address this by reducing travel lanes and planting trees. They do not intend to reduce the posted speed limit. In fact, speed limit is hardly mentioned in any of the documents. In fact, design speed is never mentioned. The city is pretending that posted speed limits have nothing to do with roadway design. The city is not willing to share with the public its intended design speeds.

The posted speed limits on Broadway and Stockton are 35 mph and, south of Lemon Hill, 40 mph. Broadway and Stockton are ‘other principal arterial’ in the state functional classification system, one step below freeway. And much of Stockton’s current design is very freeway-like. Given the intensity of uses along both Broadway and Stockton, posted speed limits of 30 mph would be appropriate. Instead, the city intends to maintain 35 mph and 40 mph for the redesigned road. This will ensure that they remain stroads rather than streets.

Northgate Blvd

Northgate Blvd is not on the city’s high injury corridor Vision Zero Plan, but was identified because it is a road with intensive local use in a disinvested community. The planning effort for Northgate is in an earlier stage. An existing conditions report, appendices, and initial community outreach are available. These reports document that posted speeds are mostly 40 mph, with a small section 45 mph. Recorded speeds are not that far off from posted speeds. but then again, the 40 mph speed is above what one would normally find in an urban area. Northgate is a ‘other principal arterial’, one step below a freeway. Parts of Northgate are have freeway-like designs, but most of it is more like a simple stroad.

Though public concerns about motor vehicle speed have been a recurring theme, the city plans to address this by narrowing travel lanes and planting trees. I participated in the initial workshop on Northgate, and I and others asked whether the posted speed limit would be reduced. The answer was no. But it is early enough in the planning process that this could be changed by public pressure. Another online workshop was scheduled for yesterday (I was unable to participate), and an in-person open house will be October 22 (Saturday, October 22 from 11:30am-1:30pm at Garden Valley Elementary School).

The city’s standard answer to questions about reducing speed limits is that they cannot be changed, because of the 85% rule (not a law, but guidance by Caltrans and courts), but this is incorrect. When a street is reconstructed, whether complete streets or other, the city can design for and set whatever speed limit it wants. It is as though a new street is being constructed. But the city doesn’t want to see it that way.

I think to redesign a road without seriously considering a reduction of the posted speed limit, as well as the design speed, is throwing money down the toilet. These projects will probably be in place for 30 years. 30 years of less than ideal design, 30 years of less than a fully functional and livable street, 30 years of failure to take climate change seriously, 30 years of unnecessarily high fatalities and severe injuries.

Background

Research on the effects of reducing posted speed limits are mixed. Some have indicated a significant impact, particularly at the higher end of the speed range (over 35 mph), and others indicating no significant change. Though even one life saved by a lower posted speed limit is worthwhile to me, it also points out that the ultimate solution to speeding is not just posted speed limits, or enforcement of those, but also roadway redesign. As I said, both!

Law enforcement of speed limits has been well documented as a tool of harassment and oppression of people of color and low income, so I am not in favor of in-person enforcement. Automated enforcement can easily manage speeds and particularly egregious speeders.

Streetsblog: Vision Zero Cities: How to Fix Our Most Dangerous Roads

Streetsblog: STUDY: 20 Is Plenty — But Signs Alone Don’t Always Get Drivers to Slow Down

Caltrans Setting Speed Limits

NACTO City Limits: Setting Safe Speed Limits on Urban Streets