How NACTO street design guidance reaches a Minneapolis skyway walk

What to take away

• NACTO Urban Street Design Guide Minneapolis guidance reaches the ground through street reconstruction projects, not through a single citywide mandate.
• FHWA pedestrian guidance sets the federal frame that Metropolitan Council and Hennepin County planners apply to downtown projects.
• A walk down Nicollet Mall shows the design choices the guidance calls for: narrow curb radii, short crossings, and clear separation of modes.
• The Minneapolis skyway route runs above the same blocks, giving a second pedestrian network that is weather-protected but privately managed.
• Everyday Counts pedestrian connections funding helped push design innovation into ordinary city projects.
• Walkers notice the difference in crossing distance, corner space, and where they can rest.

What the NACTO Urban Street Design Guide asks of a downtown street

The National Association of City Transportation Officials publishes the Urban Street Design Guide as a set of recommended practices for city streets. It is not a federal rule. Cities adopt it voluntarily, often by referencing it in their own complete streets policies or design manuals.

For a downtown street, the guide pushes several provisions. It calls for narrower travel lanes, which slow traffic and shorten crossing distances. It calls for tight corner radii so drivers turn slowly and pedestrians get more corner space.

It calls for pedestrian refuge islands on wider streets. It calls for clear separation between bike lanes and vehicle lanes. It also calls for frequent, well-marked crossings rather than long gaps between them.

Minneapolis has leaned on this framework. The city's street design guidance and its Vision Zero work both cite NACTO principles. When a downtown street is rebuilt, engineers check the NACTO provisions against the block's actual conditions.

That matters because downtown Minneapolis blocks are short and the pedestrian volumes are high. A design that works on a suburban arterial does not work here. The NACTO provisions are written for exactly this setting: dense blocks, many crossings, mixed modes.

One provision walkers feel directly is corner radius. A large radius lets cars turn fast and pushes the crosswalk farther from the corner. A small radius does the opposite. It shortens the walk across the street and gives people waiting more room.

You can read more about how that dimension plays out block by block in what sidewalk width tells you about a downtown's real walkability.

How FHWA pedestrian guidance reaches a Minneapolis project

The Federal Highway Administration publishes pedestrian planning and design guidance that states and metropolitan planning organizations use when they program federal funds. That guidance covers sidewalks, crossings, signals, and the safety analysis behind them. It is the reference layer above the city manual.

The chain runs like this. Federal transportation planning requirements shape how money is allocated and what projects must document. The Planning, Environment, & Real Estate office at FHWA administers those requirements, including the planning factors that metropolitan areas must address. Pedestrian safety is one of them.

From there, the Metropolitan Council, the Twin Cities MPO, writes the regional plan and programs projects. Hennepin County and the City of Minneapolis then design the actual street. Their designers consult both the federal guidance and the NACTO guide. Where the two overlap, the stricter or more current practice usually wins.

The FHWA Guidance - Bicycle and Pedestrian Program page is the entry point many city engineers use. It links the design guidance, the planning guidance, and the safety programs in one place. A Minneapolis project manager preparing a downtown street rebuild can pull the relevant chapters without hunting across agencies.

There is also a reference shelf. The FHWA Resources - Bicycle and Pedestrian Program page collects design references, count methods, and planning documents. Downtown walking projects draw on it for crossing treatments and pedestrian volume data.

From the page to the street: a downtown Minneapolis route

Take Nicollet Mall, the transit and pedestrian spine through downtown Minneapolis. It is the clearest place to watch the guidance land. The mall was rebuilt with wider walkways, transit-only operation for buses, and a surface that signals to drivers that they are guests.

Here is how the guidance shows up on a walk from the Minneapolis Central Library to the Hennepin Avenue intersection.

1. Start at the library entrance on Nicollet Mall. The sidewalk here is generous, and the building edge gives a clear walking zone separate from the curb zone.
2. Walk north toward the mall's transit stops. The pavement changes color and texture where buses run, which separates the transit lane from the pedestrian area without a physical barrier.
3. Cross at the mid-block crossings. These exist because the guide favors frequent crossings over long, unprotected stretches between intersections.
4. Reach the Hennepin Avenue intersection. The corner radii are tight, so turning vehicles move slowly and the crosswalk sits close to the corner.
5. Continue to the skyway entrance. The stairs and elevator put you at the level of the parallel network above.

Each step reflects a design decision that traces back to a written provision. The mid-block crossings, the corner geometry, the separation of modes: none of it is decorative.

A worked example helps. Suppose a downtown block has a wide one-way street with fast traffic and a single crosswalk at each end. Under the NACTO provisions, a designer would look at lane width, corner radius, and crossing spacing.

The likely fixes are a road diet, a refuge island, and a new mid-block crossing. Under FHWA guidance, the designer would also document pedestrian volumes and crash history to justify the change and compete for funding.

That pairing, local design language plus federal documentation, is how a page becomes a curb.

The skyway as a parallel pedestrian network

The Minneapolis skyway route is a system of enclosed, elevated walkways connecting buildings across downtown. It spans dozens of blocks and links offices, retail, hotels, and parking ramps. In winter it is the difference between a ten-minute walk and a ten-minute ordeal.

For a walker, the skyway is a second network with different rules. It is mostly private property open to the public. Hours vary by building. Wayfinding is inconsistent. Some segments close in the evening. The street below stays open.

The design guidance that shapes the street does not directly govern the skyway. But the two networks interact. Skyway entrances are street-level design elements. They need clear doors, visible stairs, and curb access. A poorly placed entrance can break the street's walking continuity.

Minneapolis has learned to treat the skyway as part of the pedestrian network, not a substitute for it. The city's pedestrian plan counts both levels. Planners know that a route that works in January may be a skyway route, while the same trip in July is a street route.

This dual network is unusual among American downtowns. It also creates a trap: a visitor can spend a whole trip above the street and never see the city. The better approach is to use the skyway for long cold stretches and the street for short, interesting ones.

The principles behind that mix, block structure, shade and reused land, apply to both levels.

Everyday Counts and pedestrian connections in practice

Everyday Counts is an FHWA program that moves proven innovations into routine practice faster than the normal adoption cycle. The fourth round, EDC-4, included a pedestrian connections focus. The EDC-4 Innovations page describes how that round pushed states and cities to build connected pedestrian networks rather than isolated improvements.

The idea is simple. A single new crosswalk does not change a walking network. A set of them, placed to close gaps, does. Everyday Counts gave agencies a framework and peer examples for that work.

For Minneapolis, the practical effect is that pedestrian connections show up in project scoping earlier. A street rebuild becomes a chance to close a gap in the network, not just repave. That is how a national program changes a local block.

The same logic applies to route planning for visitors. A long walk holds together when it has waypoints, one purpose, not when it strings together unrelated stops. Connected pedestrian networks make that kind of route possible.

Accessibility is part of the same frame. The Americans with Disabilities Act and the ADA Accessibility Guidelines set the minimum for public rights of way. Any pedestrian connection project has to meet them. That is why public sidewalks must provide clear width, firm surfaces, and detectable warnings at crossings, not just a painted line.

What a walker notices when guidance is applied

Most of the guidance is invisible when it works. You notice the absence of problems, not the provisions themselves.

You notice shorter crossings. A tight corner radius and a refuge island cut the distance you spend in the roadway. On a wide downtown street, that is the difference between a comfortable crossing and a dash.

You notice more places to cross. Frequent crossings mean you are not walking to the end of a block to get across. That changes how the whole downtown feels. It also changes how far you are willing to walk.

You notice the separation. When the bike lane, the transit lane, and the sidewalk are each legible, you stop scanning for conflicts. That frees attention for the buildings, the storefronts, and the route itself.

You notice the skyway decision. At each entrance, you choose: up into the enclosed network or along the street. Good design makes that choice clear and quick. Bad design hides the stairs or buries the entrance behind a blank wall.

You notice the winter. Minneapolis keeps a strong pedestrian culture through cold months because the network gives people options. The street works in summer, the skyway works in January, and the guidance supports both.

Before a trip, it helps to check where the walkable fabric actually is. You can use a city's zoning map to find where mixed use and dense blocks cluster, then match that to the skyway and street routes downtown.

Common questions

Does Minneapolis have to follow the NACTO Urban Street Design Guide? No. It is a recommended practice, not a federal mandate. Minneapolis references NACTO principles in its own street design and Vision Zero work, so the guidance influences projects through local policy.

How does FHWA pedestrian guidance affect a city street? It shapes the planning requirements and funding conditions that metropolitan areas must meet. The Metropolitan Council and Hennepin County then apply that frame when they design and program downtown projects.

Is the Minneapolis skyway part of the public sidewalk network? Mostly no. The skyway is largely private property open to the public, with varying hours and access rules. The street-level sidewalks remain the public network that the design guidance governs.

What is Everyday Counts? It is an FHWA program that speeds the adoption of proven transportation innovations. Its EDC-4 round included a pedestrian connections focus that encouraged agencies to build connected networks rather than isolated improvements.

What should a walker look for to judge a downtown street? Crossing distance, corner space, crossing frequency, and how clearly each mode is separated. Those four things tell you whether the written guidance made it to the ground.