Ole Avenue questions persist

Ole Avenue is St. Olaf’s planned residence hall/townhome project:

Artist’s rendering of the view up St. Olaf Avenue (Image: St. Olaf)

This is an exciting project, mostly. New residence halls and townhomes will bring students back on campus, St. Olaf Avenue will be reinforced as the tree-lined entrance to the campus from downtown and the pretty, shady campus look and feel will extend further down The Hill. Older, increasingly dilapidated homes which have been used as the Honor Houses will be replaced with state of the art, purpose-built student housing. It’s a more people-scaled project than Olaf’s high rise dorms and much easier to integrate into the neighborhood. All good.

Less wonderfully, the City Council has had two frustrating discussions focused on irrelevant issues, but managing to steer clear of the big questions; now they are about to take action on February 16, 2020.

Quite a lot of these

The Issue

This development, because it is at the edge of the campus zoning, requires a conditional use permit or CUP. Student residence halls are permitted in this area. If they were permitted “by right” St. Olaf could file their plans and city staff would sign off on it with no public review. Instead, they are permitted, but require an additional layer of public review to grant the conditional use permit because this use, in this zone, in this location is deemed to have the potential to create significant impact to the surrounding property and the community.

In short, there is not much discretion to deny the permit (because the use is permitted) if it meets the requirements of our zoning code, but there is the (golden) opportunity to impose conditions which limit the impact of the more intense use on the neighborhood and the community: “The benefits of the conditional use outweigh the potential negative effects to the surrounding area or community” in terms of such things as traffic, light, noise, and the overall character of the residential neighborhood.

The Condition

Back in November, the Planning Commission (I’m on it – this post is my opinion, not the position of the Commission as a whole) held the public hearing as required by state statute. We heard from staff, St. Olaf as the developer and from many concerned neighbors and members of the public.

I went to the Planning Commission meeting concerned about impacts to west-of-Lincoln neighbors from loading zones and security lighting; the huge amount of surface parking and the lighting, stormwater, and traffic it could create looked completely out of scale for the location. I was struck by how much space St. Olaf has devoted to storing cars compared to the spaces for people and the jaw-dropping mismatch between their lofty sustainability policies and what they have proposed.

Look at the footprint of the buildings for people compared to the space devoted to storing empty cars used occasionally.

To guide our discussion, commissioner Will Schroeer took a bottom-up approach and counted parking spaces, read the code and the policy documents, marshaled evidence about parking impacts and assembled a very thoughtful memo for the PC (which you should read). It confirmed there was already enough parking on campus and the new parking should be considered “excessive parking” (not allowed by our code) and approval should add the condition that new parking should be removed.

Based on his analysis and my own policy commitments to climate action and better streets, I voted to make what I believe is a very intentional, well-supported recommendation to Council to approve the CUP with the additional condition. The parking lots will encourage driving, add security lighting, increase stormwater runoff, and be an incompatible addition to the neighborhood.

The Planning Commission voted unanimously to recommend approval with the condition to remove new parking which has turned out to be a very challenging condition for the Council.

Process

CUPs should be pretty routine. Staff presents the Planning Commission recommendation to the Council along with the materials they prepared for the public hearing and a summary of the input from the community and commissioners. The Council then votes and they can factor in political issues and other priorities which the PC did not, but if they disagree they are required to send their reasoning to the PC in writing.

In January, City staff brought the CUP to the Council noting briefly that the Planning Commission unanimously approved the CUP with the condition of removing new parking, but moving on to the staff recommendation eliminating that condition with the justification that many of the stalls are “replacement” stalls from Honor House demolition and “insufficient accommodation is likely to result in more parking in adjacent neighborhoods.”

It is annoying that staff invited St. Olaf to the table to lobby for their plans, present new information, and revise parking stall numbers two times rather than (at least) fully presenting the Planning Commission recommendation and its policy and research justification.

It is disturbing that the Council discussion has focused on defining terms and counting spaces, rather than whether this project and the Planning Commission recommendation is in line with City policies (in which we have invested thousands of dollars, countless staff hours, and the expertise and labor of hundreds of community members) and addresses the impact to the community which is, after all, the purpose for the CUP. There is no number of spaces which is “enough” without balancing multiple interests.

All the focus on the number of spaces has resulted in stirring up a lot of dust so the Council cannot see their way through to a forward-looking, policy-based decision.

Dust storms limit visibility

There is already enough parking

For campus development, parking is evaluated campus-wide, not on a per-building basis. The parking study St Olaf submitted states clearly that “the number of permitted parking stalls (excluding loading parking stalls) exceeds the required parking” stated in the Land Development Code. While no maximum is stated, the approval criteria does stipulate “an excessive number of parking spaces are not proposed” for project.

St. Olaf’s report goes on to describe how the college also has made efforts to “decrease students’ reliance on personal vehicles, reducing the need for long-term on-campus student parking capacity.”  This suggests fewer spaces may be needed in the future, rather than more or the same amount (parking needs are also usually overestimated).

The recommendation which I believed was to remove the new paved parking lots (and could have been quickly clarified by the Planning Commission members at their last meeting) has been translated into a recommendation to remove “new” but not “replacement” parking spaces. This has triggered a new counting game asking which spaces are “new” and which are “replacement” and other number games which invite the Council to get deep into details, rather than helping them thoughtfully consider the long-term impacts to the community.

So, there is enough parking. It may not be what St. Olaf planned, it may not always be as convenient to each person as they want it to be, and, as always, removing parking spaces makes otherwise rational people batshit crazy. But there is enough.

My vote at to recommend approval with the condition that new parking be removed was meant to condition approval on removing the two large new slabs of pavement.

The proposed parking violates the LDC, Comprehensive Plan and other policies

Regardless of the number of spaces, the concentration of parking at the neighborhood edge of the campus is difficult to reconcile with the requirements for compatibility with the existing historic neighborhood, strategic goal to improve transit, stated goals to reduce carbon emissions, plans to improve car sharing (and bike and scooter sharing in the Climate Action Plan), improve bike and walk connections, enhance the small town character, and mitigate climate impact.

The development patterns of land can dictate transportation and building density, creating barriers and opportunities for where people live and how they travel. More compact land use with adequate options for non-motorized travel or transit can help reduce emissions from transportation. Conversely, low-density land use patterns that are designed for the movement of vehicles will create an auto-centric community that results in higher emissions.

Climate Action Plan

The residential part of Ole Avenue is a fine example of what the City has said it wants compact development, creating lovely streetscapes, and enhancing the interface with the St. Olaf campus which is one of the jewels of Northfield. The kind of land development pattern which can reduce emissions and mitigate stormwater issues.

The large parking lots are an example of what the City has said it does not want: The suburban parking layout is hidden from campus, but will strongly impact the surrounding neighborhood in ways which the City has said repeatedly it does not want because of their climate, human, and visual impacts. It is the kind of pattern designed for movement of vehicles.

Further, an increasing amount of research backs up Northfield’s planning by showing that abundant, cheap (to use) parking means people drive more, that reducing parking and making driving less convenient helps people drive less, and that there are multiple ways to manage parking demand to be able to build less of it. There is an increasing wave of cities eliminating all parking minimum requirements (including new DOT Secretary Pete Buttigieg’s South Bend, IN). I know members of the Planning Commission besides me stay current on these developments and I believe we are trying to guide Northfield to a more sustainable future based on best practices.

Mixed messages: Focus on the renewable energy or easy car culture? Image: St. Olaf College

Important policy and practical questions the Council could ask

There are many questions I wish Council had asked and/or staff had considered rather than counting parking spaces as if there was a right number.

How should we balance convenience against community impact? Much has been made of ensuring students have easy access to their cars for their internships, student teaching, and jobs. Yet that convenience for a few will be purchased by encouraging more traffic in the neighborhood, more climate impact, more lighting, and less green space; is this acceptable? This balancing act applies for every street project Northfield builds where parking is proposed to be removed.

How are taxpayers’ interests being protected in the planning of this development? So far, the discussion has continued to center around the perceived need for convenient parking for students. But the CUP is intended to assess the impact to the community. The spillover effects of increased vehicle use (and lighting and stormwater) in the St. Olaf Avenue/Lincoln Street area will be felt by Northfield taxpayers who pay for the streets, parks, climate action programs, and transit. For development away from this campus/community interface (along Highway 19 or by Skoglund or near North Avenue), taxpayer interests are very small. How are you assessing the community impact — especially to taxpayers — as required by the CUP criteria rather than the student impact?

Will the parking help us carry out our policy goals? For only one example, the Strategic Plan calls for improving transit. Accomplishing this requires not just putting buses on the road, but making transit efficient. If driving is prioritized, will transit be impacted? I believe the Council’s job is to stay on a policy level, not a detail level; it is staff’s job to help them do this. Every project should be viewed through the lenses of Northfield policies focused by the Strategic Plan; how does this one stack up?

Is parking on neighborhood streets a problem? Staff and St. Olaf have both threatened “but they’ll park in the neighborhood” if the parking is eliminated. Certainly, I know homeowners are rabidly protective of their curb space and will defend it against bike lanes, curb extensions, and other people parking there. But if a variety of measures are taken to help students get around without their own vehicle (now and into the future) as St. Olaf has already indicated they intend to do, will parking in the neighborhood be significant, will it be more than a temporary issue, and are there other ways to control parking near campus (neighborhood parking permits, for example, which ensure that parking is not free except for residents)?

What other alternatives besides big parking lots and no parking lots exist? It would have been possible for staff to make a principled recommendation which does include more parking, but still took the neighborhood, traffic, and climate impact seriously by requiring parking to be distributed in smaller lots around campus with only limited parking next to the dorms, placing parking with with easy access only to the Highway 19 vehicle-oriented campus entrance, and prioritizing Lincoln, Second Street, and St. Olaf Avenue as local, walkable, bikeable connections. Can you challenge staff to bring you better answers?

Can you approve the CUP without the parking lots and see if the sky actually falls? Trying to change our planning and building behavior is really hard and Northfield’s past development has worked to make driving and parking very easy. Our newer policies point us in the right direction, but still require political will to take the first step at the project level. Could you approve the CUP with additional conditions which would prevent building the parking now, but leave it possible to construct more later if it is actually needed when other mobility and access strategies are implemented, too?

The other large parking lots on the Olaf campus are well-insulated from the neighborhood and this map shows no other residence hall has a large amount of parking.

Bottom line

This project could be a model for green development and a golden opportunity for city/college collaboration. The City priorities for better transit, climate action, and more compact land use should spur the Council to see possibilities and ask “How can we help students get around Northfield?” and the College to look at its wind turbine and sustainability policies and say “We’ve said we do care about the climate, so let’s think with the city about future-looking solutions.”

“Enough” parking is a political question, not a counting problem or pure policy question. The Planning Commission looked at the numbers and made a recommendation which, I believe, reflects the policies of the City and best practices. There certainly is “enough” if Northfield and St. Olaf follow through on their climate action planning, shared mobility, better transit, and commitment to working with the neighborhood on maintaining a wonderful interface between campus and town. Your job is to weigh the political concerns and decide how much is enough.

Urbanists tweet about the roundabout

Last week, the Strib ran an article about Northfield’s planned roundabout with tunnels for people biking and walking:

Twitter responds

As a result, one local urbanist (streets.mn founder, active with Strong Towns, Planning Commissioner, and good guy) tweets:

https://twitter.com/natehoodstp/status/1191201934016942082?s=20

In turn, famous walkability guy Jeff Speck chimes in:

After a bit of back and forth, the exchange ended with:

Aside from the arrogance of this judgment (requiring omniscience to evaluate), there’s really more to be said about why this project, while unfortunate and imperfect, is justifiable.

Strib is wrong!

The Strib corrected their print story to show the the approved design below, rather than the rejected design which brought all the pedestrian tunnels to the center at a sort of below-grade plaza. The adopted version is simpler and allows more direct travel by people riding, rolling and walking:

Approved alternative for TH 246/Jefferson Parkway (image: City of Northfield)

Twitter is right!

I agree with these guys. The proposed roundabout plus tunnels is a huge amount of infrastructure with a very high price tag for an intersection with only 4,000 AADT. MnDOT and the City chose the roundabout design early and cut off opportunities to rethink the intersection for people walking, rolling, and riding and for cost savings in the short and long term.

I especially agree with Mr Speck that while roundabouts are the safest and most pedestrian friendly of the car-centric designs, they are still completely auto-centric infrastructure so the opportunity to really change the design paradigm was lost. So, yeah, the Northfield roundabout is a mega-project which violates the walkability rules and urbanism best practices.

But not completely right

Jeff Speck is an expert on walkable places, but how well does he know Northfield? This intersection is a big problem for Northfield because of prior planning problems, the character of the roads involved, Northfield’s nascent understanding of walkability and how to achieve it, and the political climate of the city.

An earlier exchange with many of the same complaints was kicked off by the only other person in the conversation who knows the Northfield landscape and, as a result, can also see the upside:

https://twitter.com/sdho/status/1169605382379114496?s=20

Northfield is just beginning to walk back the decades of suburban development which reached its apotheosis with the Northfield Middle School. This intersection is smack dab in the middle of this unconnected, residential area with three of Northfield’s five schools, a community center (including a senior center), and a future state trail which will be a major east-west bike/walk connection. And the north-south road is a state highway, just to add some jurisdictional complexity and design constraints.

Satellite image with labels describing the dead end streets on either side of Northfield's Divison Street and Jefferson Pkwy intersection
Jefferson Parkway/TH 246 intersection

No other routes to school

Because there are NO other contiguous streets which connect the Middle School and there are two more schools plus the coming into town get-to-work traffic, congestion at this intersection is highly concentrated into “rush minutes” keyed to the school day. School start and end vehicle traffic jam times are the very same times kids might be walking and biking to school (All detailed here).

MnDOT AADT map (edited): The circle marks the roundabout location and shows what doesn’t connect

Perceived safety

What traffic looks like now as it heads to the 4-way stop with turn lanes during the school rush. There are multi-use paths and sidewalks leading to this intersection, but crossing the multi-lane all way stop in traffic like this is daunting and dangerous – both actually dangerous (with one person killed crossing on foot and multiple crashes) and certainly subjectively dangerous.

Who wants to cross this on a bike? (Photo 246 Solutions)

Parents are rightly afraid to let their kids bike or walk through this area now and are also concerned that kids crossing this kind of traffic at a roundabout doesn’t feel safe. Slowing cars and crossing at grade is the urbanist recommendation, but that still doesn’t address the sense that safety is achieved only by making sure people walking and biking are physically separated from heavy traffic. A small bonus – the intersection is already somewhat elevated, so underpass grades will be quite flat.

Older adults and people with mobility or vision challenges are also uncomfortable with crossing traffic lanes and needing to perch on “refuge medians” (surely the word “refuge” suggests being stranded) especially if crosswalks are before vehicles enter the roundabout and traffic is slowing down from 45 or 50 mph and looking left for other vehicles rather than for unprotected people.

The Mill Towns State Trail will also pass through this intersection along Jefferson Parkway. While many riders and walkers on this leg will be able to cross at times which are not during the concentrated school times, the DNR recommendation for trails crossing roadways with these speeds would be a grade separated crossing which, again, is typically perceived as safer and easier for recreational users.

It’s a state highway

The current 4-way stop doesn’t work well for any mode of travel, but when choosing another intersection control the City was limited by MnDOT requirements for its highway. The intersection does not meet MnDOT warrants for a traffic signal (traffic projections forecast warrants would be met by 2040) for one thing, and MnDOT’s emphasis on traffic flow and Level of Service prioritized easy driving…so, a roundabout was the choice. There is discussion of turning back this route to the county and/or city, but that possible future development will come too late for this project.

The highway has a posted speed limit of 45 mph in front of the middle school as vehicles slow down from the 55 (or maybe 60 as speed limits were raised recently) out of town section:

Speed limits on TH 246

Building schools on state highways is a bad idea, but Northfield did it anyway three times. So, the school district buses kids across the street to the Middle School because it is a hazardous crossing and the traffic accelerates out of town right about at the Middle School. Slowing traffic should happen well south of the roundabout and maybe, if this becomes a county of city route, there will be more opportunity to do that. But, again, too late for this project.

Back to the roundabout

So, given all the other factors, what should Northfield do right now to improve safety (actual and perceived), fix school traffic jams and encourage small people and older people and recreational trail users to walk and bike through this intersection?

Note the Catch-22: If Northfield could increase the number of students getting to school under their own power that would reduce rush minute congestion created by adults chauffeuring kids to school…and if it reduced demand during peak times then the over-engineered roundabout would not be needed. But how could Northfield increase walking and biking through an intersection where people die?

My position is the roundabout can relieve the traffic jams (and improve air quality by eliminating those idling cars and buses), reduce the number of conflict points for car crashes (of which there are many), and adding tunnels makes the walking and biking not only statistically safe, but safe feeling. Making biking and walking feel safe opens the door to schools encouraging kids to walk and bike (and parents will allow it), gives the Mill Towns Trail an enhanced chance of success by allowing low stress, non-stop travel (just like cars want!).

Mill Towns Trail proposed alignment

Will it work?

Mr Speck has decreed it has never worked and will never work, but I’m hopeful that IF the City ensures that there are safe bike and walk routes to the roundabout from all directions (for thinking beyond the project area is always a challenge), then Northfield opens the door to biking and walking as real transportation so that by the time this needs to be reconstructed, the landscape will be different and the next solution will be climate focused instead.

But. I also have deep reservations about this approach. Adding bike and walk facilities, even really good ones, to a system designed for and prioritizing vehicle travel – as this project most certainly does only reinforces the unsustainable design mentality which supports the “drive everywhere” status quo. At this moment in Northfield, it is
what is politically possible, but it dodges the critical issue of reducing driving to save the planet and our health.

I have two desired outcomes for this project beyond getting people riding, rolling and walking safely to all the important destinations near this intersection. First, making this project an object lesson in Northfield’s evolving climate action planning highlighting what not to do in the future. Second, the City and school district will understand this project is a bandaid to fix a series of land use and transportation mistakes which both
jurisdictions will want to endeavor not to repeat. Maybe the very high price tag will focus their attention more sharply.

A quick look at a map of the City shows the wonderful, walkable core, but then how the City sprawled and spread. Northfield did a very thorough job of not merely breaking, but flouting Mr Speck’s walkability rules and we’re just starting to put the town back together. The particular challenges at this critical intersection mean I’m defending the choice to separate the bike and walk trails from the vehicle traffic to help people feel safer while we work on all the other pieces.

After so completely cutting off connectivity in the past, Northfield’s decision to try a big fix at this intersection is defensible, but disappointing.

https://www.youtube.com/watch?v=Rwsz1Qb81tk
The bike’s eye view from Jake Thomas

UPDATE! Northfield does get the message right

Look! Northfield has updated its sidewalk stencils for directing bicycle traffic off the sidewalks:

On view now at 7th & Division Street!

A few years ago, I complained about the City of Northfield’s misleadingly negative image on downtown sidewalks:

Really, let’s have more bikes downtown (and skateboards – also prohibited on the sidewalks!). Just walk them on the sidewalk where there’s very limited space. So THANK YOU Northfield (especially Dave Bennett) for changing the stencil and the message with the latest downtown street project.

More ideas for helping bikes fit in downtown

Provide parking (off the crowded sidewalk in high traffic locations)

But where will they park (their bikes)? Right here!

And some great destinations (again, keeping the sidewalk clearer for walking and access)

A parklet in a parking space (Image: Dero – the bike rack people)

And some signage to tell drivers and riders that they are welcome on the street rather than the sidewalk:

Sharrows (Image: Cornell)

East Cannon River Trail is in (all) the Plans

The East Cannon River Trail is the only issue on the Northfield City Council’s special meeting agenda (although there are multiple actions to be taken) tomorrow, Tuesday, April 26 2016 (here’s the packet). While there are multiple pieces in the project puzzle, approving the trail should be easy – no-brainer easy – because building this trail segment is so richly supported by prior planning going back more than a decade. This piece of trail specifically or more general guidance for improving access to the Cannon River and increasing recreational opportunities along it is contained in all Northfield’s major planning documents. The Council can take a big step toward implementing the City’s policy vision by approving this trail.

The Trail Itself

Right now, there is a section of paved trail beginning at the Peggy Prowe Pedestrian Bridge extending south toward Dundas, but the trail stops behind the commercial development. There have been wetland issues (and the Army Corps of Engineers) to manage (and wetland credits are also on the agenda tomorrow) as well as inter-jurisdictional negotiation (Dundas, DNR). Now, however, the Northfield city staff have lined up all the ducks for the Council to approve, culminating in approving a resolution accepting bids and awarding the contract for the East Cannon River Trail Project.

Map of Northfield East Cannon River Trail route

East Cannon River Trail Route

This piece of trail is important for Northfield and Dundas because it helps achieve a long-term vision to capitalize on the Cannon River as a distinctive natural, economic and recreational resource, provides an off-road link (along the busy and otherwise difficult to walk or ride Highway 3) to a charter school, commercial areas, and three parks (including Sechler Park which is being developed by CROCT as an offroad bike facility), forms another link to the Mill Towns Trail under development, and can be another small part of making Northfield good to walk, great to retire, and highly livable. No wonder it is included in all these city plans:

General plans

Comprehensive Plan: The Comp Plan highlights the importance of the Cannon River and applauds efforts “to better integrate the river into the community; its scenic beauty and recreational possibilities afford the possibility for further integration of the river into the community. The Greater Northfield Area Greenway System Action Plan is an important resource in helping with this integration.” Land Use, Community Identify and Economic Develop objectives all identify the Cannon River as critical and expanding access to the river, linking to downtown, and connecting parks, places and people.

The Economic Development Plan makes activating and leveraging the Cannon River one of three key findings for economic success; Northfield’s rich sense of place is considered critical. And, the Transportation Plan contains objectives to trail connectivity between areas of the City including current bike and pedestrian route deficiencies (current as of 2008) such as the east side trail dead ending, lack of trail integration into overall design, and challenges linking downtown with the trail system.

East Cannon River Trail specifically

Greenway Corridor Plan: Generally, this plan recommended trails should be considered on both sides of the Cannon River as well as some creeks to link neighborhoods to the river. The East River Corridor (east side of the Cannon River from Highway #3 bridge south to Dundas) was identified as the first priority “because it forms the backbone of the system, due to the potential for development, and because creation of this link will help to create strong support for the system.”

Northfield Greenway Corridors system map

Greenway Corridor System Plan

Park, Open Space, and Trail System Plan: The plan identifies this trail connection as a Destination Trail (which neighborhood trails and linking trails connect to the rest of Northfield). Individual park plans for Babcock, Riverside Lions Park, and Compostella Park also note development of an east river trail should be integrated into master planning for these currently underutilized parks.

Parks, Open Space, and Trail System Plan

Parks, Open Space, and Trail System Plan

Gateway Corridor Improvement Plan: This plan to improve gateways into Northfield incorporated the Greenway Corridor and other plans to highlight trail connections and other green infrastructure.

Costs and benefits

Almost half of the approximately $1 million trail construction cost (with bids substantially less than engineering estimates) is from grants with the remainder coming from the general fund (about $200,000), TIF funding (about $175,000), and the City of Dundas (about $93,000).  I’m not a big fan of grants, believing too often grants are sought to fund projects the City would not otherwise undertake. In this case, however, the plan to build the trail is well established and grant funding has been awarded to complete this well-documented, long-planned project. The City will need to build maintenance of the trail into the budget and CIP in coming years, but the costs relative to the wide benefits of this long-planned trail segment appear very reasonable.

The question of trail surface material must also be answered. In this area prone to flooding, the choice of a paved rather than crushed rock surface would provide a high-quality surface for more users with better durability. The plans for this trail emphasize its importance for access and connectivity; building for residents with limited mobility, children, skateboards, walkers, runners, and people on bikes; choosing the bituminous option provides bigger benefits to more people. I hope the Council will take action to carry out so many of Northfield’s plans by approving this trail project.

Connecting the trail for a bike-friendlier (and age-friendlier, walk-friendlier, people-friendlier) Northfield

Connecting the trail for a bike-friendlier (and age-friendlier, walk-friendlier, people-friendlier) Northfield

 

Development pattern productivity, continued

“No additional financial impacts are anticipated,” claims the staff report accompanying proposed revisions to Northfield’s nightmare land development regulations. Yet the proposed changes will change zoning around Northfield’s downtown to make lower density, less compact development the default pattern and this does have financial impacts for the City of Northfield.

The motivation for the changes is to make development easier and help cure Northfield’s purported reputation hostility to business, developers and development. Yet the discussion has only focused on making it easier and cheaper for developers and not on the longer term impacts for the City of Northfield and its taxpayers.

Mayor Graham was the first (but certainly not the last) person to call me anti-growth and anti-business, so let me say again that neither is true. I wholeheartedly support making the development permit process easy, predictable and cheap for developers. I urge the Council, Economic Development Authority, NDDC, and Chamber to work to encourage business and development in Northfield by retaining current business and attracting new companies.

But, and of course there was a but, I continue to advocate for the City to work to make developing in a pattern which will sustain the City financially the easiest choice rather than changing the regulations to development which is less profitable for the City the norm. Tonight, the Council should have a robust discussion about how to make the most productive use of land in Northfield for the taxpayers and how to help developers make money in the short term so the City can prosper in the long term.

Private development depends on a great deal of public infrastructure water, wastewater, stormwater, and roads.  While developers usually pay for the required improvements (but the proposed business park plans also proposed to subsidize this, too), the infrastructure is all dedicated to the City – to me and my fellow taxpayers – to maintain, repair and eventually replace. It matters a great deal whether the development the City permits can pay for the costs to maintain the infrastructure and some development patterns yield more revenue.

To help the Council consider what I mean about more productive vs. less productive development patterns, let’s do the numbers. Following in the footsteps of Strong Towns “Taco Johns math” in Brainerd and Joe Minicozzi’s work in Asheville, NC (and an additional example from Rochester), I offer three examples of different development patterns in Northfield with taxable market values and tax revenues (from Rice County public records) compared on a per acre basis to compare apples to apples. The downtown block is by far the most efficient and highest producing use of land on a per acre basis.

When considering how to zone and regulate land, the City’s interest should be to guide development in a pattern which produces the most tax revenue for the least cost in terms of infrastructure. The proposed revisions to the LDC help create lower density and lower productivity for the City.

Downtown Block

The development pattern is on a traditional grid street pattern with mostly two-story construction (there are a couple of single story buildings plus the taller First National Bank and Grand Event Center), zero setbacks, and sidewalks. This block has a mix of residential (apartments on upper floors along Division Street as well as an apartment building on Washington), retail and service businesses at street level plus additional business uses on upper floors (this makes for greater density of jobs, too).

Downtown block bounded by Division, Washington, 3rd and 4th Streets

Downtown block bounded by Division, Washington, 3rd and 4th Streets

  • Total acres: 1.71 (not including city parking lots)
  • Total Market value: $4,192,400 (not including value of parking lots)
  • Total Tax revenue (State, county & city level): $148,586
  • Value per acre: $2,451,696 (w/o parking)
  • Tax revenue per acre: $86,892 (w/o parking)

Southgate Mall development, Highway 3

This development was built in 1976, well into the suburban, highway and automobile-oriented phase.  The single-story structure with parking in front on a state highway frontage road is difficult to reach except by car. The sidewalk and new-ish bike trail along the river behind this development get pedestrians and bicycles close, but there is still no direct access. The highway oriented development requires considerably more infrastructure – a frontage road and a state trunk highway – as well as requiring off-street parking for additional distance for pipes and more stormwater runoff to manage.

Southgate development, Highway 3 south

Southgate development, Highway 3 south

  • Total acres: 1.16
  • Total market value: $152,500
  • Total tax Revenue: $4,982
  • Value per acre: $131,466
  • Tax revenue per acre: $4,295

Target/Cub development

Moving further south on Highway 3, the early 21st century big box development of Target and Cub (plus Applebee’s Restaurant) is also single-story, requiring a much greater amount of land for parking and the location at the far south end of town makes it less accessible for many on foot or bicycle.  Additional improvements to highway intersections and local connections streets added to the public cost.

Target, Cub Foods and Applebees development, Highway 3 south

Target, Cub Foods and Applebees development, Highway 3 south

  • Total acres: 26.4 (13.8 for Applebees/Cub + 12.6 for Target)
  • Total market value: $10,721,700
  • Total tax revenue: $446,882
  •  Per acre value: $406,125
  • Per acre tax revenue: $16,927

On a per acre comparison, the denser, multi-story, mixed use downtown block is the clear winner as I’ve argued before, but now provide the numbers.  As luck would have it, the proposed land development regulations share an agenda with a proposed resolution supporting a state omnibus transportation funding bill that provides additional dedicated state funding for city streets (including non-MSA street maintenance, construction and reconstruction).  How much of the pain the omnibus transportation funding bill is trying to solve is self-inflicted by building more than we can afford?

Consider why Northfield and other cities need more money for local roads; one reason is that cities have built a great deal of infrastructure to support very low return development that cannot support itself. Working toward revising how we build can also help change how resilient and prosperous Northfield will be in the future.

 

Next link in the TIGER trail project

TH3, Northfield's car sewer

TH3, Northfield’s car sewer

The tale continues…after the City Council authorized rebidding the TIGER trail project in September, 4 bids were received. All bids exceeded projected costs and the low bid is $828,465 over.  Although it took two tries to get the bids and much procedural grandstanding, let’s catch our collective breath.

TIGER supporters would probably agree that Trunk Highway 3 is a 4 lane “traffic sewer” through the middle of Northfield affecting land use, deterring bicycle and pedestrian crossing, and dividing the east and west sides of town.  Since this is also the picture drawn by the Council-adopted Comprehensive Plan (and other plans and policies I get tired of listing for those Council members who ignorantly or willfully avoid them), their understanding is well-grounded in the city’s public policy.

The City has been implementing the policies by adopting more detailed policies (like the Complete Streets policy and Safe Routes to School Plan) and following through on smaller improvements such as filling gaps in the sidewalk network (despite the failure on Maple Street) in annual street projects.  But, TH3 remains a big obstacle.  The 2009 Multimodal Integration Study (which involved collaboration among City staff, elected officials, various City boards and business owners) identified several grade-separated “concepts” which could provide better access across TH3/TH19 and subsequently form the basis of a grant application.  The TIGER grant application selected one of these and the Council approved the application…and so on.

Here are my questions about the project itself (in no particular order):

  1. Costs of retrofitting: This project builds capacity for non-motorized transportation which has not only been excluded from transportation planning until quite recently but made substantially more difficult by projects like the Highway 3 expansion.  What amount is reasonable to remedy a problem created by a mono-modal transportation project (and how can gradual improvement be added back into the transportation planning and budgeting in the future)?  When answering this question, try to identify the ways in which government subsidizes automobile travel.
  2. Cost and value of completion vs. cancellation: The state and federal government are spending money on this project; in addition to the financial contribution, what value is there in completing this project on time, honoring our commitment, and developing good working relationships with the agencies?  When answering this question, map how transportation dollars are allocated to local government from other levels of government.
  3. How does this project link to other bicycle/pedestrian facilities?  Does building this link help increase the usefulness of those facilities?  What other future improvements will further integrate this link into the network?
  4. Compared to other projects of similar scope/complexity, are the bids reasonable?  This is another way of asking whether the grant application underestimated the cost and/or complexity of the project (and that we can believe the bid numbers are the “right” ones). 
  5. Downstream effects: This project will provide jobs, help increase value in the neighborhoods most directly served, perhaps stimulate development at the stalled Crossings development as well as providing Northwest Northfield residents with additional access to jobs and services.  What are these worth?

Yes, the project costs a lot of money and more money than anticipated.  But determining whether it is “too much” should depend on a thoughtful discussion of how the trail serves the long-term transportation goals, what contribution this project makes to future projects, and how we want to build accessibility and equity into the system.

I would like to hear the Council discuss and reach a shared understanding (if not agreement) about the policy perspective adopted by the City which seeks to address transportation beyond cars and maintain and improve the transportation system in ways which serve the entire community.  It’s a big subject which could encompass everything from walking to air quality to storm water to freight to land use to economic development…but the conversation should start and providing for non-automobile connections is one place to do it.

If a majority of the Council believes the current adopted policy positions are misguided, then change the guiding policy with community participation.  Don’t get to the point of decision on projects and try to dismantle the policy one vote at a time.