Category Archives: Annapolis 

Ignite Annapolis!

I hope you enjoyed my Ignite Annapolis talk “If you always do what you’ve always done, you’ll always get what you’ve always got”. The talk was a really brief – but cheeky – overview of how choices we make in our zoning code and regulations often have unintended results that we really don’t appreciate until much later when we experience the consequences in a very real way. Also, it was a nod to the three people that have had the most influence on my thinking about urbanism: Charles Marohn, James Howard Kunstler and Andres Duany. If you know any of their work, you will hear them loudly in this talk. The short version in the video:

Read on to get a deep dive into the topics!

Continue reading

Forest Drive/Eastport study offers hope for better walkability

Appearing in The Capital, March 9, 2019

The Forest Drive/Eastport Sector Study takes a small step in the right direction towards a more satisfying future. It is not a plan but it is a hope, a strategic hope. And one must hope and envision in order to get anywhere.

We need to accept the study and keep going.

The Sector Study does accomplish, among other useful things, a vision. It does this by taking what might seem a radical perspective, and that is the perspective of a person walking from one place to another. Why is this important?

Virtually every trip begins with pedestrian infrastructure, whether you are walking or using a wheelchair. People like to walk and ride bikes. You can see this in small and large cities around the country including the older neighborhoods right here in Annapolis.

There are several main factors that affect walkability: efficiency, interest and comfort. Trips have to be close, the path has to be interesting, and people need to feel safe and comfortable. People will typically walk a quarter to a half mile such as around downtown, West Street, Eastport, and West Annapolis because it’s pleasant, interesting and often easier than driving. Biking for transportation is pretty much the same except the distances you can cover are about five times longer, up to two miles for the average person.

But if the trip is interrupted by unsafe or uncomfortable spots with no easy alternatives, walking ceases to be an option.

Unfortunately, this is the situation along the Forest Drive corridor, a typical autocentric pattern where businesses are separated by long distances and the only connection between them is on a sidewalk six inches from 50mph traffic. This environment is hostile outside of a car, so everyone drives even if going between two neighboring businesses.

Furthermore, as we’ve seen areas where we attempt to mix fast traffic and commercial activity, the combination ultimately devalues the land resulting in ugly strip malls.

The area is this way because we’ve made it this way based on the zoning and autocentric requirements we’ve had in place for a long time. Band-Aid solutions such as adding a sidewalk or a multiuse path to the side of Forest Drive are not reasonable as they don’t fundamentally address the conditions that enable people to want to walk or bike.

The vision outlined in the sector study is the first step in addressing these problems. It suggests changing the existing character of specific areas to be more people oriented by having a pattern that is mixed-use and human-scaled, which is shorthand for “things are not far apart and it’s pleasant and efficient to get around outside of a car.”

If we have places like that, we have a real chance to move between them without requiring a car trip. It could be walking or biking or even some kind of specialized transit, like entrepreneurial, privately owned shuttles.

Of course, the area will still accommodate cars for people who need to drive and we will always have significant traffic on Forest Drive given it’s the only major road and the number of people who commute in and out of the city.

But walkable, mixed-use neighborhoods that are efficiently and pleasantly connected with the rest of the city will cut down on local car trips and provide options for people who don’t drive.

As mentioned in the study, under current law there is significant capacity for development now. Stopping the study does not stop development, it just gets us more of the same, which is clearly not working. A popular opinion I’ve heard at public meetings is we have to fix all the infrastructure before we do anything else.

That view assumes the status quo, doubling down on an untenable path. At the very least, the vision of the study moves in a direction away from the autocentric policies of the past.

Alex Pline is a member of the Annapolis Planning Commission. This editorial is his opinion and does not represent the opinion of the Commission.

Forest Drive/Eastport Sector Study

The City of Annapolis Forest Drive/Eastport Sector Study, one of the “neighborhood” plans that rolls up in the city comprehensive plan is in full swing. There were a number of public meetings which I attended and a variety of presentations and work sessions with the Planning Commission, some of which I have also attended.

My main comments on the plan over time – the area is in general the newest part of the city and the most auto oriented as outlined in a prior piece on street grids – revolve around a bifurcated view of the goal of the plan. People who just pass through the area (both city and county residents) do not want any changes that affect auto mobility. They focus almost exclusively on the traffic engineering portion of the plan and only comment on the land use and other parts in so far as they don’t want changes that bring people and in their opinion, more cars. There is the other side of the street that would like to see the area more urban in nature with less emphasis on auto mobility and more on traditional urban development with a more human scaled setting for buildings, economic and residential activity, and mobility. It is this dichotomy that causes some cognitive dissonance in the plan. Strong Towns points out as a core principal that these two are fundamentally incompatible and result in a STROAD which we currently have. The worst of both worlds, people, auto oriented commerce and fast moving cars.

I have expressed this philosophically in public meetings and to staff, but I’m not sure there is really anything fundamental that will come out of that. Because of this dichotomy, I assume the plan will pretty split the difference (status quo) or attempt to do both which will read with the same cognitive dissonance I see now.

Be that as it may, I did want to comment on one very specific aspect of the study area – the need for bicycle mobility along Forest Drive. This has been a long standing goal, perhaps best documented in the 2011 Bicycle Master Plan being the only online “active” plan that contains explicit reference to this.  The May 31 draft of the report is much more explicit about this, and I am encouraged by the additional focus, but want to supplement the options presented with practical implementation suggestions that will result in the highest return on investment. This is the summary I sent to the Planning Commission and Planning and Zoning Staff to be entered into the June 20 public meeting record:

Leaving or entering the City of Annapolis by bicycle requires crossing the ring of automobile-oriented arterial roadways that surround the historic core of Annapolis, including: Roscoe Rowe Boulevard (MD Highway 70), US Highway 50/301, Solomons Island Road (MD Highway 2), and Aris T Allen Boulevard/ Forest Drive (MD Highway 665). Bicyclists of necessity can be seen in all parts of Annapolis, weaving routes through neighborhoods and often on sidewalks to access commercial and employment destinations. The existing network of off-street bicycle facilities is similarly discontinuous, but provides the initial links in what will be an exemplary regional trail network, connecting neighborhoods and forming the core of Annapolis’s future Bicycle Network.

Desired and Existing Bicycle Network

I appreciate the updates in the May 31 draft of the sector study that brings bicycle mobility to the forefront. Both the short term and long term issues are addressed in section 2.7.2.2, Bike and Pedestrian Networks, as well as the potential solutions in section 3.4 Mobility: Pedestrian and Bikes.

Building on the discussion of the issues and potential solutions, it is important to go into additional detail because the efficacy of bicycle infrastructure for both transportation and recreation is very dependent on the implementation. I refer to an article published on strongtowns.org (https://www.strongtowns.org/journal/2014/5/19/follow-the-rules-bikers.html) which discusses the auto-centric cultural bias of planners and engineers and how it affects bicycle and pedestrian infrastructure implementation. Perhaps equally important is how this bias affects public perception of this infrastructure. I encourage you to read the entire article.

“…the concept of a “complete street” as “separate but equal”, not to diminish the despotism of racial segregation but to show the parallel of mindsets with how most of the country treats bikers and walkers. When we build a trail – or a separate drinking fountain – we’re (engineers, planners, drivers, society) doing something within our comfort zone. It allows us to feel like we’ve fairly accommodated others while not really having to change our approach to be accommodating. We can continue to act in a despotic way only now with a tinge of self-righteousness. We paid for them to have theirs, after all.”

“We need to rethink our urban areas. They need to be redesigned around a new set of values, one that doesn’t seek to accommodate bikers and pedestrians within an auto-dominated environment but instead does the opposite: accommodates automobiles in an environment dominated by people. It is people that create value. It is people that build wealth. It is in prioritizing their needs – whether on foot, on a bike or in a wheelchair – that we will begin to change the financial health of our cities and truly make them strong towns.”

With this in mind, when the city begins to implement infrastructure outlined in the sector study, we have to make sure it is done in a way that does not just accommodate bikes in an auto-centric environment, but results in a network that is not only safe, but also contiguous, fast and comfortable. If we expect to shift mode share based on this infrastructure – that is to fully realize the return on investment – there must be a definite “value add” for bike riders. For example, faster transit time, bike parking at the front door of the destination, and/or a more pleasant trip. If we always give priority to the auto mode, why would someone chose to ride a bike? This is the most common criticism. Or worse, it incentivizes breaking the law which is always most unsafe for the bike rider because this infrastructure prioritizes the mistakes of drivers over the mistakes of bike riders. The following examples illustrate this bias towards the auto mode and implementation suggestions that attempt to remove this bias.

An Unrealistic Expectation For Path Users

This bike path requires cyclists to stop at every curb cut. Anyone trying to get down this bike path bike will likely never fully stop, resulting in a very unsafe situation.

Shared Use Path Along Forest Drive

In the study area, the existing path near the Safeway grocery store is typical of US-based infrastructure along arterial roads where it is clear the path users are secondary because the turn radii are large and the auto lanes uninterrupted which promotes fast vehicle movements in an area designed to (minimally) accommodate pedestrians and bike riders.

In a similar vein to the visual examples of community character in the draft document, examples of well-designed bicycle infrastructure – we can look to the Dutch for inspiration – will help guide future implementation. The Dutch are not only leaders in urban bicycle infrastructure, but also suburban bicycle infrastructure. The You Tube Channel “Bicycle Dutch” (https://www.youtube.com/channel/UC67YlPrRvsO117gFDM7UePg) is an excellent resource for examples of both.

Contrast the above images with this Dutch junction design where the bicycles are given priority and this priority is supported by the visual treatments on the pavement.

Typical Dutch Junction Design

Additionally, an east/west separated path along the corridor should be as isolated from the major arterial as far as possible. Not only will this make the user experience more pleasant, but will move conflict points away from arterials and allow for vehicle speeds to decrease before a conflict point. This is consistent with the complete streets philosophy and many of these ideas are also discussed in the National Association of City Transportation Officials Urban Street Design Guide (https://nacto.org/publication/urban-street-design-guide/).

There are a number of areas that are slated for development along the corridor that the city should require this type of design as a condition for the development such as The Village at Providence Point and Rocky Gorge (at least garnering an easement for when a path can practically be extended along Aris T Allen). Furthermore, around Annapolis Middle School, there is copious right of way owned by Anne Arundel County that could easily be used for this path and would significantly benefit the children who attend the school. This would also mitigate the current safety concerns resulting from the recent crashes involving school children. Funding for this area of the trail could be sought through the federal Safe Routes to Schools part of the Transportation Alternatives Program.

Given the corridor is a priority residential development area, the large number of existing commercial services and the lack of non-auto infrastructure, construction of this path along the entire corridor should be the highest priority in the capital improvement project recommendations.

A new way to look at development and planning with Alex Pline (E-66)

After all the ranker about local development projects during the election, I asked John and Tim of The Maryland Crabs Podcast if they’d be interested in having me on to talk about development. Much of the discussion focuses on who can say NO the loudest. Ultimately it’s disingenuous to just talk about yes or no on more development or just about the traffic issues. We need to question the underlying assumptions that go along with local development such as the implications of various styles of development on mobility. I lso really wanted to discuss local development in a Strong Towns frame of reference by bringing in the idea of productivity of development styles.

“You may remember Alex Pline. He was last on the podcast talking about parking and biking in Annapolis. He also has some unique ideas on City planning and says that theCity is (and has) been doing it all wrong and proposes a different, holistic way at looking at planning and development.”

It was a lot of fun and I hope I was able to bring a different view to the development discussion. I definitely can’t wait to be back to be back on the show, especially given that we all like to have “beer drinking episodes”.  I also got a nice look around The Commons, a local shared work space on West Street where they do many of the podcasts now.

Give it a listen:

Alex Pline Talks Parking, Transportation and Biking in Annapolis

Sitting around the 'Dirty Kitchen Table' with John Frenaye and Tim Hamilton

Sitting around the ‘Dirty Kitchen Table’ with John Frenaye and Tim Hamilton

I recently appeared on The Maryland Crabs Podcast, a podcast that covers the waterfront of local topics, to discuss parking, transportation and biking in Annapolis. In my role as Chair of the Annapolis Transportation Board, the subject of parking comes up at almost every monthly meeting. Since I’ve been in Annapolis, parking has always been handled in a fractious and ad hoc manner by the city. There have been many studies and virtually every transition team for an incoming mayor has recommended reforming the parking policy to be “holistic” so that all of the parking facilities (metered spots, residential parking permits and parking garages) all work together as a “system”. Despite these recommendations, the city has never been able to accomplish this goal on its own.

The Pantelides Administration made it a goal to implement this idea and actually did through a contract with SP+ Municipal Services, a national player in parking management. Of course people in Annapolis hate change – any change of any sort – so the implementation of the contract has not been without its detractors. One of the goals of hiring a “playa” in the parking management business is that they, as subject matter experts, can bring state of the art ideas in parking management to the table and in fact one of their contract deliverables is a Parking Utilization Analysis (full report, large PDF)  in Annapolis that would contain recommendations for parking policy changes in the city (summary in The Capital).

As these recommendations filtered out to the public opinions on social media were abound. I got into it with John Frenaye and Tim Hamilton over their assertion that this contract was a “money grab” by SP+ and the city and other misunderstandings about the effort. So they invited me on the podcast to talk about this and my other passion, transportation cycling.  It was a fun experience and a great conversation to bring some perspective to this activity for people who have not been intimately involved.

Unfortunately, we did not have as much time to talk about biking, which could fill an entire podcast itself, but I did make a few key points about transportation cycling in Annapolis (we need more connectivity!).

It was a lot of fun and we had a great conversation. According to Tim, there has been very positive feedback and a higher than usual download rate. I hope to be back on in the future to discuss the nexus of transportation, land use and municipal finances, because these are typically viewed as separate, siloed issues, when in reality they are different facets of the same issue that interplay in ways that most people don’t really understand.

Give it a listen!

Or subscribe via iTunes or Google Play

The Kobayashi Maru Test

Last night, the Annapolis Planning Commission faced their Kobayashi Maru test. How will they decide whether access to the Rocky Gorge planned development is via Aris T Allen Boulevard or Yawl Rd: place the lives of Rocky Gorge residents in grave danger by turning off and on a highway or assuring the destruction of the Oxford Landing neighborhood with 48 homes worth of traffic down their main street?

Followers of this development have been watching this issue come to a boil slowly over the last two years. But, for those not familiar with the development and this issue specifically, let me recap.

Rocky Gorge is a planned development of 46 units of single family and townhouses south of Aris T Allen Boulevard. For a good overview, you can see the site plans here (76MB) or search for project PD2016-001 on the Annapolis eTRAKiT project tracking site for all the project details.

location

The project has a long and sordid history with many, many complicated facets. It began with two annexations of land in 2003 and 2005 followed by development approval (SE2005-11-547) and initial grading, the financial crisis of 2008, bankruptcy and sale to a capital management firm and most recently restarting the development in 2014. This history, while important to how we got to this point, is for the most part, water under the bridge, not to mention that the more you dig into understanding the history, the more questions arise. That said, one of the limitations placed on the development by the annexation agreement was no direct access from Aris T Allen Boulevard. However, that was predicated on a “relief road” south of the development, but for many practical and environmental reasons was never, and will never be built.

As the design and review of the restarted development progressed, due to the access limitation in the annexation, Yawl Rd was the only way in and out, straight through the center of the Oxford Landing development built in the late 1980s. And of course the residents objected, so resolution R-33-14 to remove the annexation restrictions was introduced to the City Council. If passed would open the door to alternative access via Aris T Allen Boulevard.  It wound it’s way through the process and was ultimately passed. I wrote about it here and here and the Planning Commission,  Transportation Board, and The Capital also thought it was not a good idea. Once the restriction was removed, it went to the State Highway Administration (SHA) for a decision as they “own” the road (MD 665). After an additional traffic study and meetings with the SHA, access was granted with addition of acceleration and deceleration lanes.

yawl_access

Rocky Gorge – Access Via Yawl Rd

Once this access was granted by SHA, the site plan was substantial altered to change the access from Yawl Rd to Aris T Allen. As such, the project went back to the Planning Commission, which brings us up to date for the meeting last night and the Kobayashi Maru test.

665_access


Rocky Gorge – Access Via Aris T Allen (right in right out)

The developer’s representative Allan Hyatt gave a long and somewhat tedious presentation. He is a lawyer and every presentation I have seen him make to a city Board or Panel is treated in language and actions like a trial, explicitly stating everything for the record along with expert testimony, even though the Planning Commission does not officially recognize “expert witnesses” (a point of snickering with the chair). This was a public hearing so a number of people spoke, residents, representatives of ARTMA, the Annapolis Neck Peninsula Federation, Oxford Landing, and Alderwomen Finlayson/Pindell-Charles, indicating significant safety problems with either access scenario – deadly car crashes on Aris T Allen or kids run over by cars on Yawl Rd.

Kirk

Those were the only two choices on the table: 1. Approve the application as submitted (design with ingress/egress to Aris T Allen only, other than a pedestrian/emergency connection to Yawl Rd) or 2. Deny the application and revert to the prior approval (design with ingress/egress via Yawl Rd only). Virtually all the Planning Commission members expressed frustration with these equally bad choices. There must be alternatives that would not be unsafe for users Aris T Allen or residents of Oxford Landing, but how? Like Captain Kirk, they chose a different way: leave the public hearing open indefinitely and allow the applicant – who fortunately saw the writing on the wall – to look for alternatives.

It is my hope that all parties involved can think about innovative solutions that attempt to mitigate the compounded mistakes and prior planning decisions that lead up to this scenario and hopefully learn a lesson and apply it future developments. The suburban design pattern of cul de sacs and hierarchical road networks is a detriment to incremental growth that is so important to a healthy Annapolis as it was intended by design to be static and does not scale well. See this short video for a primer on incremental development and why it is important. Much of downtown Annapolis and inner West Street developed this way and has been better off for it.