Natasha Mehu, MACo Policy Analyst, testified in opposition to SB 779, Land Use – Proposed Development Project – Transit and Traffic Adequacy Studies, to the Senate Education, Health, and Environmental Affairs Committee on March 1, 2016.
This bill would impose a new transit adequacy study requirement to jurisdictions where it may not even be relevant and increase costs for affected local governments and project developers.
From the MACo testimony,
Under SB 779, a local jurisdiction that requires a traffic adequacy study to be done by a proposed development project must also require a transit adequacy study. Currently, 14 counties and 26 municipalities have adequate public facility ordinances (APFOs) for roads.
The 14 counties include: Anne Arundel, Baltimore, Calvert, Caroline, Carroll, Charles, Frederick, Harford, Howard, Montgomery, Prince George’s, Queen Anne’s, St. Mary’s, and Washington. There are areas in most of these jurisdictions where transit is minimal or nonexistent. The bill’s linkage of traffic adequacy requirements and transit adequacy requirements is illogical.
The transit adequacy study makes no sense in county and municipal areas where transit does not exist. Outside of several densely populated cores, including the DC-metropolitan and Baltimore-metropolitan regions, most areas of the state lack a functioning transit system that would justify an adequacy study.
Where transit does exist, it does so in extremely limited forms, such as downtown trolleys, and is not a primary transportation mode.
The bill would also impose new costs on both project developers (who must pay to prepare the studies) and local governments (who must bear the costs to review the studies or hire outside experts to review the studies). As the bill’s fiscal note indicates, these costs may be significant. The net costs of a study could hamper proper and needed development in economically depressed areas of the state.
The Maryland Department of Transportation supports the bill.
For more on 2016 MACo legislation, visit the Legislative Database.