Memorandum: To: TISTWG Members From: Dan Hardy Date: November 30, 2014 RE: Latr Concept Sheets and December 3 Meeting
Memorandum: To: TISTWG Members From: Dan Hardy Date: November 30, 2014 RE: Latr Concept Sheets and December 3 Meeting
To:
From:
Date:
RE:
TISTWG Members
Dan Hardy
November 30, 2014
LATR CONCEPT SHEETS AND DECEMBER 3 MEETING
This memorandum provides background and guidance for the interactive discussions we will have at our
December 3 meeting (1:30-3:30 PM) in the MRO Auditorium. In response to comments on the initial
LATR concepts presented at the November 5 meeting, we have organized a full range of LATR Concepts
into three categories:
Scoping existing and proposed concepts that describe when a transportation analysis will
be needed, or what type of analysis will be needed based on the type and extent of
proposed development
Analysis existing and proposed concepts that describe the types of analysis appropriate for
each concept
Concepts proposed to be dismissed from further study
We have organized both existing and proposed LATR Scoping and Analysis concepts into subcategories
as described in Table 1, and have prepared a summary sheet for each concept. We request that you
review this material before the December 3 meeting, and come prepared with some thoughts to share
at the meeting.
The objective for our December 3 meeting is to gain additional feedback, and consensus where possible,
on LATR Concepts that should be either retained for more detailed analysis or removed from
consideration.
o
o
The primary purpose of this meeting is to understand areas of focus for LATR concepts that have the
greatest areas of interest among TISTWG members and guests. The key element in each of the LATR
Concepts presented in this packet is the Next Study Steps described for each concept, with two
different types of recommendations:
We do recommend removing the five concepts (D-1 through D-5) on Board #3 from further
study,
For all other concepts being discussed at Boards #1 and #2, we are not making any final
recommendations, but are rather seeking feedback on the most valuable areas to pursue and
refine in the next three months.
We hope that you are all able to review these materials in the first half of the week and attend the
meeting this Wednesday afternoon. If you are not able to attend, we will follow up with you to get your
reactions and input.
2
Prepared by Renaissance Planning Group
November 30, 2014
3
Prepared by Renaissance Planning Group
November 30, 2014
4
Prepared by Renaissance Planning Group
November 30, 2014
5
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
What planning objective does the concept achieve? How does it help implement the jurisdictions
vision?
Strengths
Weaknesses
Examples of Application
How might the concept work, either based on the experience of other jurisdictions or hypothetical
examples in Montgomery County?
6
Prepared by Renaissance Planning Group
November 30, 2014
Concept in a Nutshell:
Enter into a Traffic Mitigation Agreement (TMAg) to agree to reduce
50% of peak period vehicle trips and pay twice the applicable
transportation impact tax in lieu of conducting any Local Area
Transportation Review or Transportation Policy Area Review actions.
-50%
Primary Purpose:
Incentivize trip reduction and eliminate need to examine and mitigate vehicular LOS in Metro Station
Policy Areas
Strengths
Focuses private sector efforts
solely on trip reduction.
Weaknesses
None.
Improving predictability
Eliminates uncertainty
associated with LATR and TPAR.
Streamlining implementation
Examples of Application
Two applications have been approved under this Alternative Review Procedure:
7
Prepared by Renaissance Planning Group
November 30, 2014
Twinbrook Commons was approved (Preliminary Plan 1-04054) in May 2004 by the Planning
Board and subsequently annexed into the City of Rockville
North Bethesda Center (LCOR) was approved (Preliminary Plan 12004049A) in November 2007
by the Planning Board and is within the geographic area now covered by the White Flint Special
Taxing District.
The North Bethesda Center project has an executed Traffic Mitigation Agreement (TMAg) executed in
December 2006 and in effect for 55 years, or until the Planning Board determines it is no longer needed.
It is possible that over time the LCOR approach will be renegotiated at some point in the future to shift
from the TMAg approach to the broader Special Taxing District approach.
This procedure has rarely been applied, due primarily to the risk associated with its aggressive, and longterm, trip reduction performance requirements. However, it remains a logical option to retain in the
pantheon of LATR concepts as it is a key option in fulfilling the Countys vision for reducing reliance on
auto travel in transit-served areas.
8
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Leverage the property values in the White Flint Sector Plan
area to help fund needed transportation system
improvements, notably a robust street grid with significant
eminent domain requirements that make it infeasible to
implement under traditional LATR and TPAR exaction
processes.
Strengths
Monitoring program examines
periodic progress towards
multimodal goals
Removes uncertainty from
development proposal process
Facilitates implementation of
well-defined, multimodal
network improvements requiring
governmental actions such as
eminent domain to implement.
Weaknesses
Requires substantial advance
planning and negotiation to
establish alternative process
Staging plan entails some risk of
future areawide moratoriums
None, although the challenges
with a consolidated plan
implementation initiative may be
more visible than would be with
dozens of smaller projects.
9
Prepared by Renaissance Planning Group
November 30, 2014
Examples of Application
The White Flint Sector Plan area is the only location in Montgomery County where LATR and TPAR are
fully replaced by an alternative review procedure.
This project classifies the establishment of such districts as Pro-Rata Share approach to addressing the
transportation impact of development.
The concept might be considered for other areas of the County where individual transportation impact
taxes could be replaced by a multimodal implementation district. Other jurisdictions in the literature
review utilizing a similar approach that replaces analysis with a pay-and-go approach include:
Multimodal Transportation Districts in Florida, including the City of Kissimmee and the City of
Destin
Plan Districts in the City of Portland, Oregon (covering about half the city acreage)
Traffic Mitigation Zones in the City of Baltimore, Maryland (covering about half the city acreage)
10
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
The vehicle trip generation thresholds serves as a definition of de minimis impacts on the Local Area
Transportation system.
Strengths
None
Weaknesses
None
Streamlining implementation
transportation impact tax in lieu of taking action under LATR. Under the proposed change to increase
the threshold to 50 or more vehicle trips countywide, this clause would become obsolete.
The Subdivision Staging Policy also notes that the 30-vehicle trip generation rate applies to both existing
and new trips, but that if the existing development is fairly well established (75% of approved use and
occupancy permits were issued more than 12 years prior to LATR study scoping) then the study scope
must be based on the increased vehicle trip generation rate rather than the total trip generation rate,
and that no LATR action is needed in such cases if the proposed development expansion would generate
5 or fewer new peak hour vehicle trips.
75 peak hour vehicle trips in Metro Station Policy Areas and Central Business Districts
50 peak hour vehicle trips elsewhere in the County
The existing 30-peak hour vehicle trip threshold is the lowest threshold of any of the jurisdictions
included in the literature review (Rockville also has a 30-trip threshold). A threshold of 50 vehicle trips is
a fairly common threshold; most jurisdictions with a vehicle trip threshold use either 50 or 100 vehicle
trips. Further, the TPAR and transportation impact tax processes provide a belt-and-suspenders
approach toward addressing transportation impacts. Finally, since review of the MWCOG household
travel survey indicates that MSPAs tend to have non-auto-driver mode shares about 20-30% higher than
the rest of the County, a 75-vehicle trip threshold for MSPAs and CBDs might reasonable be equated to
the level of activity generated by a 100-vehicle trip threshold commonly used by other jurisdictions.
A higher trip generation rate threshold is appropriate in the most smart growth areas for several
reasons:
These are the areas where the County most wants to encourage private development, so
reducing the barrier to entry in these areas is a recurring theme for all LATR Concepts
These areas generally share a few common characteristics that suggest private and public sector
analysis efforts are better spent elsewhere:
o The overall levels of activity mean that a new neighbor generating 75 vehicle trips will
likely be less noticeable in an MSPA/CBD than one generating 50 vehicle trips in a less
developed community
o Adjacent intersections within CBDs tend to operate well below the congestion
standards; congestion requiring mitigation is generally outside the MSPA/CBD areas
where only larger studies requiring larger study areas would trigger analysis of
congested locations
12
Prepared by Renaissance Planning Group
November 30, 2014
Examples of Application
There is likely to be concern regarding loss of analytic information associated with the proposed
increase from 30 to 50 peak hour vehicle trips. Examples of urban jurisdictions that have adopted
mode-specific person trip generation rates include:
New York City has development thresholds that are based in development size descriptions,
such as 200 dwelling units, 115,000 square feet of office space for lower Manhattan designed
to establish 50 peak hour vehicle trips as an appropriate threshold
Conversely, the beta draft of Washington DCs Comprehensive Transportation Review
Guidelines recommends a threshold of 50 peak hour person trips, which in some cases could be
lower than 30 peak hour vehicle trips.
The City of San Francisco also uses the 50 peak hour person trip threshold
13
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
The existing approach serves to identify intersections where the site trips generated are expected to
have a significant impact. The proposed changes streamline the identification process.
Streamlining implementation
Strengths
None
Weaknesses
None
None
None
14
Prepared by Renaissance Planning Group
November 30, 2014
Per the Subdivision Staging Policy, the number of vehicle trips cited reflects the total trips (not the net
increase in trips), unless use and occupancy permits for at least 75% of the originally approved
development were issued more than 12 years before the LATR study scoping request.
The Subdivision Staging Policy also indicates that if a site requires improvements to at least one
intersection (or a TMAg is required or proffered by the applicant) and the site causes a second
intersection to have a < 5 CLV increase, then the applicant need take no action to mitigate that latter
intersection. The LATR/TPAR Guidelines indicate that this consideration can be applied at time of study
scoping, but the conditions to satisfy this characteristic can only be known after the study has been
completed.
Examples of Application
Most jurisdictions have some level of relationship between the size of the development and the size of
the transportation impact analysis. Examples of precise guidance include:
The City of Rockville expresses minimum study parameters based on the number of new peak
hour trips generated that are somewhat similar to Montgomery Countys; the smallest study
area (for 30 peak hour vehicle trips) is expected to include at least 4 intersections within a
quarter mile of the site and the largest study (for more than 700 peak hour vehicle trips) is
expected to include at least 16 intersections within a mile of the site.
The Atlanta region has
square footage/dwelling unit
thresholds (for Cobb County,
within the Metropolitan Tier,
these thresholds include 400
DU, 400,000 GSF of office)
that trigger a Development of
Regional Impact (DRI)
processes administered by the Atlanta Regional Commission (ARC). For DRIs, a roadway
segment has a significant impact if the site generates at least 7% of the subject facilitys capacity
(an example shown in the table excerpted from the DRI guidelines). A similar process, using
Critical Lane Volume analysis, identifies significant impacts at intersections.
King County, Washington identifies a significant intersection impact as occurring when the site
will add more than 30 vehicles per hour to the intersection and those 30 vehicles constitute at
least 20% of the total site generated trips.
15
The proposed adjustment to the study area would utilize these concepts to better define locations
without significant impact during the scoping process. Unlike the current LATR/TPAR Guidelines
process, the straw-man proposal would consider:
Intersections that would otherwise be included in the study area defined by the minimum number of
intersections in each direction may be excluded from analysis if:
The site-generated intersection volume is less than 1% of the total intersection entering volume
(note that the site entering volume is likely to constitute only 2 to 6 of the possible 12 turning
movements at a four-legged intersection and the total entering volume includes all 12
movements), or
The site-generated intersection volume is less than 5% of the total site generated traffic.
16
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
To account for cumulative impacts of multiple development
projects.
Strengths
Recognizes increased travel
demand in background condition
Improving predictability
None
Streamlining implementation
Weaknesses
Many legacy development
approvals do not reflect current
market trends
Addressing assumptions for
legacy approvals can create
uncertainty
Documenting/monitoring shared
responsibility for improvements
can be challenging.
Examples of Application
The assessment of an appropriate analysis horizon year and level of background traffic is perhaps one of
the most widely divergent topics found in the literature review. Most jurisdictions that require
assessment of impacts from background traffic apply a high level of judgment in defining those
background developments compared to Montgomery County. However, many jurisdictions are more
conservative in the amount of additional growth beyond approved developments.
Traffic Growth Factor
Cobb County / GRTA (M)
VDOT 527 (F)
Background Developments
Montgomery County (J)
Pasadena (J)
San Francisco (J)
Both
Los Angeles (J, O)
San Jose (J, O)
Boulder (F, J, O)
Baltimore
New York City (J)
Key to abbreviations:
(F) = more than one future horizon year may be required (i.e., project open, longer term buildout)
(J) = considerable judgment applied in defining background developments re:
location, size, approval status
(O) = options for cumulative traffic (California term) may include pending plans in addition to approved
developments and/or a growth factor
(M) = travel model data may be used in lieu of historic trendline traffic growth
The simplest approach to background traffic is to use a common traffic growth factor in lieu of specific
background developments, such as applied by Cobb County, GA and in the Virginia statewide guidance
for Section 527 analyses. Many jurisdictions like Montgomery County, simply use the amount of
background traffic generated by approved but unbuilt developments. But many jurisdictions combine
the two approaches, recognizing that some background traffic will be generated by developments
beyond those near the subject site. In nearly all cases, the written guidance stresses the need to apply
judgment in determining an appropriate definition for background developments.
The background conditions also include transportation system improvements that are either
conditioned of prior development approvals or are fully funded in the first six years of the currently
approved County CIP or state CTP (LATR/TPAR Guidelines, p. 12).
Bill #14-02 would change the Subdivision Staging Policy for the White Oak Science Gateway Policy Area
by eliminating the provision of background traffic conditions. This proposal, as well as the Planning
Boards response proposing a proportional share payment approach, is described in the packet for the
October 20, 2014 PHED Committee packet:
http://www.montgomerycountymd.gov/council/Resources/Files/agenda/cm/2014/141020/20141020_P
HED1.pdf
18
Prepared by Renaissance Planning Group
November 30, 2014
The concerns currently paramount in the White Oak Science Gateway Policy Area echo similar concerns
that have surfaced as free rider concerns over the past several decades in different areas of the
County, so an approach that works countywide is desirable. The PHED discussion on October 20
directed the TISTWG to consider alternative approaches and develop a recommendation as part of the
comprehensive Subdivision Staging Policy recommendations.
For White Oak, define whether sufficient knowledge is available to move from a negotiated
exaction approach to a true pro-rata share approach for all improvements in the White Oak
Science Gateway Policy Area. Given the uncertainty associated with BRT and interchange
specifics
Define the limitations associated with the payment in lieu of construction element of the
LATR/TPAR Guidelines (p. 26) as applies to the White Oak area concerns.
Identify other approaches in the current Subdivision Staging Policy that may be applicable and
cite pros and cons as applied to the White Oak area concerns, including:
o Approach for Multiple Applicants for intersection improvements (LATR/TPAR Guidelines
p. 19)
o Establishment of a development district and Provisional APF approval under TP4 of the
Subdivision Staging Policy
Identify additional alternative means for addressing proportional assignment of costs and
benefits for multiple public and private sector applicants.
19
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Identify impacts and mitigation that are responsive to the types of
travel demand anticipated by each mode, based on the type of
development, location in the County, vision for the County, and
desired travel demand management approaches.
Improving predictability
Streamlining implementation
Strengths
Establishes context-sensitive
triggers for modal analysis based
on expected demand for each
mode
None
Helps identify specific
improvements for each mode of
travel
Weaknesses
None
None
None
achieving a non-auto driver mode share goal (NADMS), regardless of the submodal split
between auto passengers, transit riders, pedestrians, bicyclists, and/or number of trips not
made due to flex time or telework
20
focusing on the home-based work (HBW) trip, which usually consists of a journey-to-work trip
for which the US census (and its continuous and rolling American Community Survey element)
provides a robust data source at the census block level, and often an assumption that the return
journey home from work is made by the same mode as the journey to work
Across the nation, jurisdictions are realizing that the consideration of multimodal travel demands needs
to become both more accurate and more precise. The Institute of Transportation Engineers has
recognized this need in a full revamping of their how-to guide on trip generation, called the Trip
Generation Handbook, which is a companion
to the more frequently referenced Trip
Generation (aka Trip Generation Manual)
compendium of observed vehicle trip
generation rates compiled from studies
nationwide. The first two editions of the Trip
Generation Handbook, published in 2001 and
2004, provide guidance on nuances such as
pass-by trips and internal trip capture in mixed
use activity centers, but remain oriented on
vehicle trips. The 3rd edition of the Trip
Generation Handbook was published in draft
form (as a Proposed Recommended Practice)
in August 2014 and proposes a sweeping
change from a vehicle-trip orientation to a
person-trip orientation. In most suburban and
rural environments, the 3rd edition recognizes
that vehicle trips may continue to be the only
mode which warrants quantitative analysis.
However, the handbook recommends
thinking in terms of person trips and then
assigning those trips to each mode of travel,
particularly important in environments such as mixed use centers, transit-friendly developments, and
infill developments, where the NADMS will be substantially higher than the primarily suburban
environments for which the Trip Generation Manual has vehicle trip generation rates. The draft Trip
Generation Handbook provides available information to estimate NADMS for vehicle trip generation
rates for many common land use codes. In suburban environments, the primary component of NADMS
is auto passengers; Table C.3 of the draft Trip Generation Handbook demonstrates that for most uses,
each auto tends to carry between 1.1 and 1.4 persons (i.e., with an average auto occupancy of 1.25,
even if there are zero walk, bike, and transit trips, the NADMS equals 20%).
The Trip Generation Handbook will likely take a year or so to be adopted by ITE as a Recommended
Practice, following a formal comment period and editorial changes in response (ITEs Recommended
Practices go through an adoption process not too dissimilar from a master plan or sector plan adoption
21
Prepared by Renaissance Planning Group
November 30, 2014
process). In the interim, the Montgomery County Planning Department is proceeding with a separate
study to update trip generation rates and similarly convert from an auto-oriented approach to a persontrip oriented approach. The Planning Departments approach builds from the ITE approach to utilize
both the MWCOG Household Travel Household Surveys conducted between 2007 and 2012 which
report on all modes and purposes for some 144,000 individual trips in the region; as well as the MWCOG
travel demand model which is validated against those survey data points.
An assessment of NADMS for all purposes
and all times of day from the MWCOG Travel
Model for trips starting and ending in each of
the Countys policy areas provides a fairly
recognizable picture of travel demand in the
County. As indicated in Table C.3 of the draft
Trip Generation Handbook, the fact that auto
passengers are fairly common, particularly for
most non-home-based work trips, means that
every policy area in the County has a baseline
NADMS of about 26%, with many MSPAs and
CBDs having an NADMS of 38% to 43%. This
range may not seem as wide as
conventionally perceived in master plan discussions of NADMS, but is due to the inclusion of all trips,
rather than peak period journey-to-work trips (as well as the fact that even for work trips, a common
misperception is that the ITE rates are suburban and therefore reflect an NADMS of 0%, whereas even
the most suburban workplaces typically have an NAMDS of about 10% due to carpooling).
Examples of Application
A straw man proposal would include the following triggers:
Location
CBD/MSPAs
Elsewhere
Quantitative analysis would entail the concepts described in Analysis Methods Concepts:
23
Prepared by Renaissance Planning Group
November 30, 2014
Concept in a Nutshell:
Most intersections in the Potomac Policy Area
are not subject to LATR review
Primary Purpose:
The vision of the Potomac Subregion master
plan is predicated on part of the retention of
narrow, two-lane roadways, which is more
important than addressing delays due to
congestion. For the most part, the Potomac
Subregion has been classified as a subregional
cul de sac in that its position adjacent to the
Potomac River limits its attraction to through vehicles. Eleven intersections in the Potomac Subregion,
where the prevailing environment is more suburban and economic and regional concerns outweigh the
desire for a rustic ambiance, are subject to LATR.
The Potomac two lane roadway policy is somewhat similar in approach to the Protected Intersection
concept in SR-3, although the latter concept applies to enhancing the pedestrian experience in urban
areas rather than preserving the rural ambiance of rural areas.
Improving predictability
Streamlining implementation
Strengths
Recognizes the balance between
rural preservation, local resident
interests, and broader
countywide mobility needs
Reduces uncertainty in
negotiating unpopular
intersection improvements
None
Weaknesses
None, as long as the policy
remains in place and the public
sector needs not make capacity
improvements to catch up.
None
None
24
Prepared by Renaissance Planning Group
November 30, 2014
Examples of Application
Common across all LATR studies for development proposals in or affecting the Potomac Policy area.
25
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Address one element the free rider concern by recognizing that the first mitigating action (intersection
improvement or trip reduction program) likely creates more capacity than required so that an additional
minor impact elsewhere can also be considered to have been mitigated by the first mitigating action.
Strengths
None
Weaknesses
None
None
None
Examples of Application
TBD.
Primary Purpose:
Reduce propensity for widening intersections to provide vehicular
capacity at locations where additional widening is contrary to the established vision for an area.
Improving predictability
Streamlining implementation
Strengths
Reduces the identification of
auto-oriented solutions where
such solutions are contrary to
the vision
Reduces uncertainty in
identifying and negotiating costly
and unpopular vehicular capacity
improvements
Reduces the likelihood of a
conditioned improvement being
superseded or otherwise
affected by a public sector
improvement
Weaknesses
Detracts from finding other
negotiated-exaction solutions,
such as non-auto facilities at
$12K per trip
None
None
Examples of Application
San Joses Protected Intersection policy provides a precedent for this approach
The concept of a protected intersection is most sound where:
Additional roadway capacity is likely not feasible or runs counter to established plans or visions
The county has already established a policy establishing a pedestrian priority in intersection
design, such as in the Countys urban areas
Appropriate alternative routes are available for traffic to avoid the protected intersection.
For instance, the intersection of Georgia Avenue (MD 97/US 29) and
Colesville Road (US 29/MD 384) in the Silver Spring CBD is a logical Protected
Intersection candidate as it is impractical to add additional roadway capacity,
it is located in a designated MSPA/CBD/urban area, and there is a robust
network of designated business district streets to allow traffic to disperse in
all four quadrants to avoid the subject intersection.
Conversely, the intersection of MD 355 and Gude Drive is not a logical
Protected Intersection as the Shady Grove Sector Plan recommends
additional capacity enhancements (either at-grade or grade separated) as
part of the staging plan, it is not located in a designated urban area, and
there are no designated business district or arterial routes within a half-mile
radius to allow traffic a bypass option; all traffic most flow through this
intersection.
28
Prepared by Renaissance Planning Group
November 30, 2014
TA3 (p. 15) Automobile Related Uses in the Cherry Hill Employment Area: no action needed
under TPAR or LATR for APF-related submissions prior to July 26, 2016
TA4 (p. 15) Public Facility Project: no action under TPAR or LATR for projects constructed
solely for public use such as schools, libraries, or fire stations.
29
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Bring consideration of multimodal impacts to the
forefront of both the analytic approach of all LATR
studies and to public awareness.
Strengths
Promotes and codifies
multimodal approach consistent
with County priorities
None
Streamlining implementation
None
Weaknesses
None
Examples of Application
TBD
31
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Improve walkability and implement planned pedestrian
connections.
Improving predictability
Streamlining implementation
Strengths
Improve identification of the
most valuable pedestrian
connections in the vicinity of a
development site
Improve identification of
potential connections through
pre-screened candidate locations
provided by M-NCPPC
Improve implementation or
funding of pre-screened
candidate locations
Weaknesses
Potential for increased analytic
complexity, depending on
analysis details
Potential for increased
negotiation for potential
connections not on pre-screened
candidate location list
None.
The Pedestrian and Bicycle Impact Statement remains essentially a state of the practice assessment of
qualitative conditions, emblematic of similar requirements in most jurisdictions nationwide. It should be
retained essentially as is; but with additional quantitative considerations described below.
Examples of Application
Quantitative analysis thresholds and approaches for pedestrian system analysis include:
The New York City CEQR requires detailed pedestrian analyses for any pedestrian system
element such as a sidewalk segment, crosswalk, or intersection corner will increase by 200 or
more peak hour pedestrians (including pedestrians en route to transit). For these location, the
quantitative pedestrian assessment utilizes on Highway Capacity Manual approaches to
pedestrian level of service which focuses on pedestrian flow densities (pedestrians per square
foot of space). Qualitative assessments of safety are also required in a manner similar to the
current LATR Pedestrian and Bicycle Impact Statement.
The Washington DC draft CTR requires detailed pedestrian and bicycle system analysis for sites
that have at least 200 residential units, 50,000 GSF of commercial/retail, is more than one block
in size, or generates 100 combined pedestrian/bicycle trips. The pedestrian analysis walkshed is
one-quarter mile from the site. Quantitative analysis includes signal-related traffic delay along
pedestrian routes to major destinations such as
Metro stations. Simulation may be required showing
how pedestrian and bicyclist flow will be
accommodated at locations where a high
concentration of multimodal conflicts is judged to
occur. Qualitative analysis includes sidewalk widths,
condition, and gaps; ADA compliance, and presence
of pedestrian scaled lighting. Mitigation includes
addressing any characteristics that would preclude
achievement of the proposed mode splits for the site.
Any mitigation to address pedestrian improvements
must assess its delay on other modes.
The City of Rockville incorporated accessibility
analysis in the Transportation Element of its
Comprehensive Master Plan. The concept of
pedestrian walksheds that are based on travel time
33
rather than a fixed radius is shown in the page 4-24 exhibit from the plan showing walk travel
time to area schools. The concept of pedestrian accessibility is an element of the Citys Trip
Reduction Plan.
Considering the relative sizes and densities of the New York and Washington system environments, the
Washington DC approach (with lower thresholds
combined with a more flexible and collaborative
analysis approach) appears more appropriate for
Montgomery County.
Three potential means for incorporating pedestrian
accessibility in the LATR Guidelines are shown in the
following set of exhibits, with a focus on the Spectrum
development at 12345 Old Columbia Pike. The first
graphic shows a conceptual 4,000 radius distance from
the study site, with an overlay of the areas that could
be reached (labeled as the walkshed) by walking 4,000
along the local street network. The selection of 4,000 is only for illustrative purposes; a one-quarter
mile, one-half mile, or one-mile radius may be more appropriate for walking or bicycling trips. The ratio
of land accessible within the walkshed as compared to the crow-flies radius is roughly 50%.
The second graphic shows the effect of a hypothetical
new connection between Old Columbia Pike and Staley
Manor Drive and the Southern Asian Seventh Day
Adventist Church, which would increase the walkshed
by about 20 acres, or about 2% of the land area. This
could be one measure of the value of offsite pedestrian
system improvements for a given development site.
Of course, the White Oak Science Center is bounded
along its western edge by the Paint Branch Stream
Valley Park, which is a natural and passive recreational
resource, but not a high volume destination. A second
alternative would be to use destinations, rather than land area, as the measure of accessibility. Again,
hypothetically speaking, the original walkshed may provide access to only 50% of the land area within
the crow-flies radius, but perhaps that land area contains 90% of the jobs and housing units within the
crow-flies radius. Therefore, the same connection may increase walk and bike access to 3% or 4% of the
total jobs and housing units; a second measure of accessibility.
Finally, the relative value of proximity to the study site could be incorporated in the assessment by
applying a friction factor or decay curve, to the value of jobs and housing units that are more distant
from the site, reflecting the fact that most people will walk a short distance to a desired destination but
only a small proportion will walk 4,000 to the same destination. Applying a gravity weighted, or
34
Prepared by Renaissance Planning Group
November 30, 2014
decay-weighted value would increase the complexity of the analysis, but assign a more appropriate
value to the new connection by weighting connections that are closer to the study site higher than those
that are farther away.
The accessibility approach could be measured in terms of distance, as in the 12345 Columbia Pike
examples shown above, or it could be converted to consider walking time and incorporating signal
delays, as in the Rockville plan example.
The accessibility value would be
used to either augment or replace
the modal value associated with the
new connection. Currently, Table 6
in the LATR/TPAR Guidelines assigns
off-site sidewalks and bike paths an
equivalency between length of new facility and a number of vehicle trips to be discounted. A simple
replacement would be to replace the 100 linear feet specification with additional acreage,
jobs/housing units, or gravity-weighted jobs/housing units, depending on the independent variable
selected.
An alternative approach could be to establish context-sensitive standards for pedestrian accessibility.
For instance, in CBDs and MSPAs with good grid networks, the ratio between accessibility for the crowflies distance and the walking distance should be high (perhaps 75% or 80%). In contrast, rural areas
with sparse networks would have a much lower ratio (perhaps 25% or less). This concept can be
explored further, although given the wide range of possible parcel-specific accessibility scores, this
approach would likely have unintended consequences if established as a standard measure as opposed
to an incentive-based approach.
Predictability of application could be enhanced by the development of a list of desired pedestrian
system connections in each policy area that are pre-screened by M-NCPPC and MCDOT as ready for
implementation (including facilities in facility planning). Applicants should be encouraged to identify
potential valuable connections that are not already in master plans.
36
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Increase the ability to move about the County in a lowstress bicycling environment, focusing on connections
between bicycling activity clusters.
Improving predictability
Streamlining implementation
Strengths
Improve identification of the
most valuable low-stress bicycle
connections in the vicinity of a
development site
None
Weaknesses
Potential for increased analytic
complexity, depending on
analysis details
Potential for increased
negotiation for potential
connections
None.
Examples of Application
Most jurisdictions, like Montgomery County, handle bicycle system impacts from a qualitative
perspective, with judgment applied where necessary. For instance, the San Francisco guidelines indicate
that if sufficient bicycle traffic exists or is anticipated on a study area street, it may be necessary to
include a quantitative analysis of the impacts using the methodology in the 2000 Highway Capacity
Manual or some similar technique.
37
Prepared by Renaissance Planning Group
November 30, 2014
The Washington DC draft CTR requires detailed pedestrian and bicycle system analysis for sites
that have at least 200 residential units, 50,000 GSF of commercial/retail, is more than one block
in size, or generates 100 combined pedestrian/bicycle trips. The bicycle analysis walkshed is
one mile from the site. Simulation may be required showing how pedestrian and bicyclist flow
will be accommodated at locations where a high concentration of multimodal conflicts is judged
to occur. The location of any proposed bikeshare stations must be shown. Any mitigation to
address bicycle improvements must assess its delay on other modes.
Most jurisdictions and staffs recognize that the methods for assessing on-road bicycle LOS such as those
in the Highway Capacity Manual are somewhat limited for an approach to development review.
Because they are based on stated and revealed preference surveys by on-road bicyclists themselves
(which is an appropriate and noble goal) the level or quality of service is more a function of adjacent
street traffic and truck percentage than it is a function of the on-road bicycle facility itself. The inability
to move the needle with mitigation makes such measures undesirable from a development review
perspective. Admittedly, the 2010 Highway Capacity Manual techniques were derived prior to the
advent of buffered bicycle lanes or cycle tracks, which may represent a notable improvement over
signing and marking techniques used for more conventional shared roadway and bicycle lane
treatments.
The Montgomery County Planning Department is exploring the concept of Low Stress Bicycling and
Network Connectivity following the techniques described in the Mineta Transportation Institute (MTI)
Report 11-19 from May 2012.
http://transweb.sjsu.edu/PDFs/research/1005-low-stress-bicycling-network-connectivity.pdf
This connectivity approach recognizes that many roads will not
practically be made comfortable (or low-stress) for most on-road
bicyclists, and examines ways to increase the connectivity
between places through a network of roadway that are low
stress.
This approach might be combined with the accessibility-based
concept described in AM-1 on pedestrian system measurement to
examine places that are accessible via low-stress bicycle facilities.
Considering for the moment that all the industrial streets east of
US 29 and south of Fairland Road might be found to be low-stress
bicycle routes, but that crossing US 29 might be high stress, the
area of low-stress bicycle connectivity within a 4,000 distance of
12345 Columbia Pike might be shown in the first diagram at right.
If an improved crossing of Columbia Pike were provided in the
vicinity of Industrial Parkway, then much of the neighborhood on
the west side of Columbia Pike might be found also within a
38
Prepared by Renaissance Planning Group
November 30, 2014
39
Prepared by Renaissance Planning Group
November 30, 2014
Concept in a Nutshell:
Assessing the degree to which additional transit trips
generated by site development create capacity constraints in
the transit system.
Primary Purpose:
Ensure transit system adequacy to support additional
development and encourage additional transit use.
Streamlining implementation
Strengths
Introduces transit system
analysis for significant transit trip
generators
None
Weaknesses
None
Introduces identification of
transit system mitigation
elements
None
Examples of Application
Most jurisdictions do not have a specific threshold for triggering a transit system analysis. For instance,
San Francisco publishes current and horizon year screenline capacities for different transit systems and a
quantitative analysis is required if the project would cause a screenline to exceed a 1.0 volume/capacity
40
Prepared by Renaissance Planning Group
November 30, 2014
ratio (which as of the current publication date was only 100 additional peak hour, peak direction riders
on the Third/Mission Street corridor, but more than 500 additional peak hour, peak direction riders on
all other screenlines.
Specific trip thresholds for transit analysis include:
The New York City CEQR requirements have fairly stringent transit analysis metrics but also fairly
high analysis triggers:
o A subway/rail analysis is required if the proposed action will increase the peak hour
volume at a single subway station (with multiple lines) or a single subway line (with
multiple stations) by 200 or more riders per hour. In such a case, the CEQR analysis
requires detailed assessments of line-haul, platform, farecard machine, fare array
turnstiles, stairway, and escalator capacities.
o A bus transit analysis is required if the proposed action will increase the peak hour
volume at a single bus line by 50 or more riders (in the peak direction) per hour.
The Washington DC draft CTR requires transit system analysis if the proposed site generates at
least 50 transit trips or the transit mode share exceeds 30%. A capacity analysis of transit
conditions will be performed for any site that generates 30 peak hour transit trips to any bus or
streetcar route that has headways greater than 20 minutes in the peak hour. Remaining
justification of the transit system to accommodate the projected transit volume is to be
performed qualitatively, considering the transit service characteristics and adequacy of the
pedestrian access between the transit station and the site. The Washington DC draft CTR refers
applicants to the WMATA Design and Placement of Bus Stops guidance for prioritization of
potential mitigating improvements.
Considering the relative sizes and densities of the New York and Washington system environments, the
Washington DC approach (with lower thresholds combined with a more flexible and collaborative
analysis approach) appears more appropriate for Montgomery County. It is unlikely that the 30% transit
mode share will be achieved in all but the most Metro-accessible residential locations (such as Wheaton
Safeway), and the use of the 50 transit trip threshold appears sufficient without combining it with a 30%
transit mode share criteria (i.e., an infill project of 20 townhomes might generate 10 peak hour person
trips with a 30% transit mode share, but quantitative analysis should not be required to assess the
impact of those three transit trips).
41
Prepared by Renaissance Planning Group
November 30, 2014
Assessment of bus system capacity if the site is currently served by buses with 20
minute or longer headways
Application of the pedestrian gap analysis described in Concept AS-3 to include connectivity to
the nearest bus stop or Metrorail station (if within one-quarter mile). In other words, even if
the AS-3 concept is not found supportable as a stand-alone approach, it should be considered
part of the transit analysis.
42
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
More roadway congestion is appropriate in
urban areas where transit service is excellent;
more stringent roadway congestion standards
are needed in suburban and rural areas where
transit options are less robust.
Improving predictability
Streamlining implementation
Strengths
Provides multimodal equity by
balancing transit and auto
mobility (one, but not both,
modes must be adequate in all
areas of the County). Promotes
walkable TOD by reducing
pressure to widen intersections.
None
None
Weaknesses
None
None
None
43
Prepared by Renaissance Planning Group
November 30, 2014
Examples of Application
Applies to each application based on the policy area that the intersection is located in.
44
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Apply multimodal operational assessment of intersection operations
where CLV does not provide sufficient accuracy to gauge an appropriate
mitigation approach due to the potential for queueing/spillback.
Improving predictability
Streamlining implementation
Strengths
Potential for improved
assessment of quality/level of
service for all modes of travel,
including delay-based measures
of effectiveness
Improved constituent buy-in on
problem identification and
appropriateness of solutions
Improved identification of
appropriate solutions
Weaknesses
Increased cost of analysis
preparation, review, and impact
determination/negotiation
Within 600 feet or less (an industry standard for desired intersection spacing to facilitate traffic
flow) of another signalized intersection, or
On a segment of roadway identified by MNCPPC in the most recently published
Mobility Assessment Report as congested
(the graphic from the 2009 Highway
Mobility Report is no longer current, but
shown as an example of the potential for
agency designation of congested corridors
where operational analysis would be
triggered at a 1450 CLV.
Examples of Application
Many jurisdictions use Highway Capacity Manual techniques, including simulation programs such as
Synchro or VISSIM, as the primary tool for intersection adequacy analysis. Examples of additional
guidance includes:
Alexandria, VA uses HCM where V/C ratios are < 0.85 and VISSIM for more congested locations
as well as locations where there is a dedicated transitway or interstate highway access. The city
provides guidance on VISSIM calibration acceptance targets for modeled link volumes.
Washington DC indicates that an increase in 5-seconds of delay per vehicle at an intersection or
a queue length increase of more than 150 feet are significant impacts to be mitigated, and that
solutions to mitigate vehicle LOS must not add significant delay to other modes.
New York City describes significant impacts as 3 seconds (if already at LOS F) to 5 seconds (if
already at LOS D) in an increase to average vehicular delay and indicates spillback should be
addressed, although without a specific definition or mitigation requirement.
o
o
o
47
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
An applicant should be held fully responsible for substandard intersection
performance that they do not cause, but in such cases the applicant should be required to not only
mitigate their own trips but help improve the baseline condition in an effort to return to (or towards)
the congestion standard. This has been informally described in prior Subdivision Staging Policy
discussions as akin to the Boy Scouts motto of leave things better than you found them.
Improving predictability
Streamlining implementation
Strengths
Focuses additional private sector
attention and resources where
intersection performance is
substandard.
None
Minimizes the likelihood that an
applicant improvement and
public sector improvement will
both be pursued simultaneously
Weaknesses
None
None
None
Examples of Application
Existing applications in Montgomery County; this approach was not found in the literature review.
$12K
Primary Purpose:
Improve ability to provide safe and convenient pedestrian travel and
support the creation of facilities that encourage transit use, walking, and bicycling (as stated in the
Subdivision Staging Policy TLI, p. 11)
Strengths
Facilitates consideration of
multimodal solutions
Improving predictability
Streamlining implementation
Weaknesses
Policy does not relate to value of
actual vehicle trip reduction
achievement
None
None
49
Prepared by Renaissance Planning Group
November 30, 2014
Examples of Application
The payment of a fee to mitigate peak hour vehicle trips was applied fairly regularly for Preliminary
Plans under the Policy Area Mobility Review (PAMR) procedure (e.g., BB&T Bank Kensington-Wheaton
120110350, Bethesda Center 120120070, Olney Assisted Living 120120090, Travilah Grove 120120290).
The PAMR procedure is no longer relevant under the Subdivision Staging Policy but the fee payment
remains available as a mitigation approach for LATR.
50
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Address gaps in pedestrian and/or bicycle connectivity in areas with
high levels of non-motorized demand.
Improving predictability
Streamlining implementation
Strengths
Facilitates identification of
meaningful gaps in the
pedestrian/bicycle network and
identification of solutions
None
Weaknesses
None
51
Prepared by Renaissance Planning Group
November 30, 2014
Examples of Application
The definition of significant pedestrian impacts is likely to require some discussion. Two jurisdictions in
the literature review have quantitative definitions for significant pedestrian generation that are fairly
disparate:
New York, NY requires detailed pedestrian analysis for increases of 200 or more pedestrians per
hour at any sidewalk, crosswalk, or intersection corner.
Washington DC proposes detailed pedestrian analysis for increases of 100 or more pedestrians
per hour generated by the site, or by site characteristics including more than 200 residential
units, 50,000 square feet of commercial/retail space, or a site encompassing more than a small
block grid.
The Washington DC draft CTR notes that if deficiencies in the study area would preclude achievement of
the proposed mode split, then those deficiencies must be mitigated. The 2013 TRB paper by Zimbabwe
et al states that if pedestrian, bike, or automobile exposure is substantially increased in any area where
a safety deficiency has been documented, then a developer must provide partial mitigation of the issue,
so as to not significantly exacerbate an existing condition.
52
Prepared by Renaissance Planning Group
November 30, 2014
The comparison to a regional average is unclear, but has many potential adverse consequences:
o If not separated from land use type, it may have the effect of making low-intensity uses
(i.e., self-storage) more desirable than high-intensity uses (i.e., grocery stores)
o If segregated by land use type, it would likely penalize non-core jurisdictions where VMT
rates are usually lower than even smart-growth locations in suburban jurisdictions. For
instance, from a regional perspective, it is likely than any hospital in DC, Arlington, or
Alexandria would generated lower than average VMTs for hospitals, therefore having no
significant impact, and that any hospital in Montgomery County would generate higher
than average VMTs for hospitals, a significant impact. Or, if the comparison was simply
within-County, the Washington Adventist Hospital location in Takoma Park may be
53
found to have no traffic impacts based on its infill location, whereas the White Oak
location would have traffic impacts.
The analysis of safety impacts complicates the reliance on VMT. There is widespread
concurrence nationwide that safety for all modes of travel is of paramount importance. The
OPR draft suggests that safety impacts would be triggered if additional traffic generated by a
new development (regardless of its location or VMT generation characteristics) created a 15MPH speed differential between adjacent roadway travel lanes, or an off-ramp backup onto a
freeway. These safety concerns are important, but both require the analysis the initiative was
designed to minimize and suggest auto-oriented mitigation actions the initiative was designed
to avoid.
From a broader perspective of potential application to LATR, there are three key reasons that VMT
should be dropped from further consideration, without delving further into the philosophical and
technical concerns above:
LATR focuses on localized impacts; very few vehicle trips generated are likely to be shorter than
the LATR study area,
VMT is already implicitly incorporated in the TPAR approach, and
LATR already has many other existing tools for mitigating auto trips with non-auto-oriented
solutions, and many additional concepts are being investigated as part of this study.
A slightly broader summary of SB 743 is included in the TISTWG meeting packets for September 3 and
October 1. The full OPR report currently under discussion is available here:
http://www.opr.ca.gov/docs/Final_Preliminary_Discussion_Draft_of_Updates_Implementing_SB_743_0
80614.pdf
The Western District of ITE has prepared a letter of commentary on concerns related to SB 743 as
related to land use policy, planning and implementation. The final letter (November 21) has not yet
been posted to the westernite.org website but a copy in PDF form can be provided upon request.
http://www.westernite.org/ITE%20Draft%20Letter%20to%20OPR%2010-27-14.pdf
Primary Purpose:
The genesis for SB 743 was to exempt transit-oriented or infill development projects from CEQA
transportation analyses, as such projects would have lesser impacts on typically congested roadways,
thereby supporting both the private sector investment in TOD/infill projects and removing the need to
mitigate congestion impacts in environments where even small projects often triggered auto LOS
mitigation in CEQA in congested areas where the state and local agencies frankly did not intend to
uphold LOS standards by adding vehicular capacity.
54
Prepared by Renaissance Planning Group
November 30, 2014
Strengths
Intent is to exempt infill/TOD
projects from transportation
requirements.
Improving predictability
None
Streamlining transportation
project implementation
None
Weaknesses
Californias exemption process
would not capture community
concerns about understanding
congestion and addressing
multimodal needs.
Most vehicle trips are longer
than LATR study areas, so VMT
does not add much more
information than vehicle trip
generation.
Requires more information on
trip purpose and trip length,
generally reliant on MWCOG
travel demand model data
None
Examples of Application
None recommended
55
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
The objective of high levels of street network connectivity is to
improve walkability through short block lengths and more direct
connections between potential origins and destinations. Better
connectivity between adjacent subdivisions also increases the ability
for trips by all modes to be made without burdening the arterial
roadway network.
Streamlining transportation
project implementation
Strengths
Intent is to improve walkability
through more robust, dense
street networks
None
None
Weaknesses
Topological requirements alone
do not guarantee effective
connectivity
Definitional challenges
associated with connectivity
increase level of required
negotiation
None
Examples of Application
The concept of street connectivity is useful for developing general guidelines for design elements such
as maximum block lengths and cul-de-sac lengths. Several jurisdictions include street connectivity in
their subdivision design standards, although they are generally not part of a transportation adequacy or
concurrency test. The most common approach is a connectivity ratio defined as the number of street
56
Prepared by Renaissance Planning Group
November 30, 2014
intersections divided by the number of street segments, with a ratio of 1.4 often defined as a desired or
required ratio.
The state of Delaware adopted a connectivity ratio requirement of 1.4 in Title 2 of the Delaware
Administrative Code in 2009.
The City of Durham, NC has a connectivity ratio requirement of 1.4 in Section 13 of their Unified
Development Ordinance, adopted in 2006.
The state of Virginia enacted a connectivity requirement in the inaugural Secondary Street
Acceptance Requirements (SSAR) legislation in spring 2009, with compact areas requiring a
connectivity ratio of 1.6, suburban areas a ratio of 1.4, and no requirement for rural areas. The
requirement was removed in the 2011 edition and replaced with a requirement for a multiple
subdivision entrances for each 200 dwelling units or 2,000 ADT trip generation.
A key objective of a connectivity ratio or index is to promote internal and external connectivity in cases
where community opposition or market preferences would tend to result in a greater reliance on cul-desacs. A challenge for connectivity requirements is the recognition that site constraints often preclude
achievement of the desired connectivity ratios, particularly for smaller subdivisions. The short-lived
Virginia requirement recognized exceptions for constraints created by railroads, freeways, bodies of
water greater than 4 feet deep, grades greater than 20%, and protected government lands or
conservation easements. The connectivity ratio was found to be somewhat confusing and raised
concern that it did not actually increase cross-subdivision easements (as artificial internal street
connections could be designed to meet the connectivity ratio requirements without significantly
affecting actual mobility.
57
Prepared by Renaissance Planning Group
November 30, 2014
Concept in a Nutshell:
Definition of significant auto travel
impact based on the amount of traffic
traversing a specific roadway segment
as opposed to an intersection analysis.
Primary Purpose:
The use of screenline analyses to
identify area capacity is a simplifying
approach to identifying capacity
constraints, particularly where traffic
may distribute itself across several
parallel routes, so that identification of
an impact on Road A may not need to be mitigated if parallel Road B has additional roadway capacity to
accommodate diverted trips.
Improving predictability
Streamlining transportation
project implementation
Strengths
Intent is to avoid adding
vehicular capacity on any given
route when capacity may exist
on parallel routes
Remaining system capacity on
screenlines easy to calculate
None
Weaknesses
Does not account for congestion
due to intersection performance.
None
None
transportation facility planning. The screenline analysis is not likely appropriate for development
review, however, as it is a far simpler tool than CLV to assess capacity and the prevailing stakeholder
sentiment at this time appears to be that CLV is too coarse a tool to assess many intersection
operations.
The establishment and definitions of screenline or cordon line capacity also requires time and effort to
gain consensus. Screenlines and cordon lines are only sensitive to improvements made on the links that
cross the screenline or cordon line themselves, not adjacent intersection or link improvements that may
meaningfully improve operations.
Examples of Application
The City of Seattle uses a screenline approach to track transportation concurrency. Under this approach,
a transportation analysis estimates the auto trips generated by the project that will cross one or more
screenlines near the project site. Project volumes plus background traffic volumes for a screenline are
compared to the established capacity for the screenline.
59
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
To reflect reasonable goals for Traffic Mitigation Agreement mode share goals.
Strengths
Focuses attention towards trip
reduction
Improving predictability
Streamlining transportation
project implementation
None
Weaknesses
Legacy approach outdated and
therefore unused for many
years.
Legacy approach; goals
expressed in imprecise terms
and not maintained to reflect
increasing number of policy
areas with goals set in SSP TL4
None
Setting peak period non-auto driver goals for policy area employees that are the same as the
currently observed non-auto driver share for residents in the policy area
Referencing that the goal above would be superseded by commuting goals specified in the
Growth Policy (sic)
APF-2 notes the Silver Spring CBD goals in TL4.1, but does not note those subsequently added in TL4.2
through TL4.6.
Recent history indicates that most Traffic Mitigation Agreements tend to develop goals that are either
based on master plan or sector plan mode share goals (an intent suggested both by Section 42A-9A and
APF-2) or to achieve specific trip reduction necessary to achieve LATR requirements. To be consistent
60
Prepared by Renaissance Planning Group
November 30, 2014
with the Exempt Second Improvement Mitigating < 5 CLV concept, it seems unreasonable to require
TMAg mode share goals in excess of those required to satisfy LATR (or TPAR) requirements.
Any historic Traffic Mitigation Agreements whose goals were predicated on APF-2 should, if still in
operation, be presumed able to stand on their own merits for trip reduction goal achievement so that
the removal of APF-2 from the next Subdivision Staging Policy will not have any adverse effects.
Examples of Application
N/A
61
Prepared by Renaissance Planning Group
November 30, 2014
Primary Purpose:
Placing areawide restrictions on parking or vehicle trips
reduces the propensity for vehicle trip generation. Establishing a cap and trade system where capacity
for vehicle trips or parking spaces is a scarce resource would incentivize developers to use less of their
allotted resource
Improving predictability
Streamlining implementation
Strengths
Potential for aggregating and
simplifying vehicle trip impacts
across multiple shared
applications
Areawide parking constraints (as
currently applied in Silver Spring
CBD) provide known levels of
additional capacity.
None
Weaknesses
Cap and trade systems can be
difficult to establish and manage.
62
Prepared by Renaissance Planning Group
November 30, 2014
Examples of Application
Several jurisdictions are exploring the concept of trip caps or parking caps with the concept of allowing
development applicants to share or trade capacity in either an open or regulated market, but the
practice is not yet sufficiently established to be implementable in Montgomery County during the
timeframe of this study.
63
Prepared by Renaissance Planning Group
November 30, 2014