<?xml version='1.0' encoding='utf-8'?>
<baltimore-city-law heading="Subtitle 40 – Complete Streets">
  <container prefix="Part" num="I" heading="Definitions; Applicability">
    <section prefix="§" num="40-1" heading="Definitions.">
      <para num="(a)" heading="In general.">In this subtitle, the following terms have the meanings indicated.</para>
      <para num="(b)" heading="Complete Streets.">“Complete Streets” means a transportation philosophy that calls for streets to be constructed and operated in a way that considers the needs of all users and enables equitable and safe access.</para>
      <para num="(c)" heading="Advisory Committee.">“Advisory Committee” means the Complete Streets Advisory Committee established by this subtitle.</para>
      <para num="(d)" heading="Public transit vehicle.">“Public transit vehicle” means any vehicle that:<para num="(1)">is of a type used primarily for the transportation of the general public; and</para>
        <para num="(2)">has a seating capacity of 10 or more passengers.</para>
      </para>
      <para num="(e)" heading="Street.">“Street” means any street, boulevard, road, highway, alley, lane, sidewalk, footway, mall, esplanade, or other way or place that is owned by the City or habitually used by the public.</para>
      <para num="(f)" heading="Transportation Department; Department.">“Transportation Department” or “Department” means the Baltimore City Department of Transportation.</para>
      <para num="(g)" heading="Transportation Director; Director.">“Transportation Director” or “Director” means the Director of the Baltimore City Department of Transportation or the Director’s designee.</para>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 22-125</annotation>
    </section>
    <section prefix="§" num="40-2" heading="Applicability of subtitle.">
      <para num="(a)" heading="In general.">Except as otherwise provided in this subtitle, this subtitle applies to all project phases undertaken by or, under the authority of the Transportation Department for the improvement of any street and public right of way, including planning, programming, design, acquisition of land, construction, construction engineering, reconstruction, rehabilitation, resurfacing, retrofit, and operation.</para>
      <para num="(b)" heading="Exceptions – Ordinary maintenance.">This subtitle does not apply to ordinary maintenance, such as mowing, cleaning, sweeping, pothole filling, concrete joint repair, and other regular or seasonal maintenance.  Ordinary maintenance includes local road resurfacing on roadway segments, exclusive of intersections, that experience traffic volumes of fewer than 6,000 vehicles per day, based on the latest available or estimated traffic data.</para>
      <para num="(c)" heading="Exceptions – Preexisting projects.">This subtitle does not apply to a project at or above 30% design or under construction as of January 3, 2020.</para>
      <para num="(d)" heading="Exceptions – Limited-access roads.">This subtitle does not apply to a street where use by both pedestrians and bicyclists is prohibited by law.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§§" num="40-3 to 40-5" reserved="true" />
  </container>
  <container prefix="Part" num="II" heading="Complete Streets Transportation System">
    <section prefix="§" num="40-6" heading="Department to construct and operate system.">
      <text>The Department must construct and operate a comprehensive Complete Streets Transportation System that enables access, mobility, economic development, attractive public spaces, health, and well-being for all people.</text>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
    <section prefix="§" num="40-7" heading="System to ensure safety, etc., and convenience of all users.">
      <text>This Transportation System must be designed and operated in ways that ensure the safety, security, comfort, access, and convenience of all users of the streets, including pedestrians, bicyclists, public transit users, emergency responders, transporters of commercial goods, motor vehicles, and freight providers.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-8" heading="System to include connected facilities accommodating all travel modes.">
      <text>This Transportation System must include integrated networks of connected facilities accommodating all modes of travel.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-9" heading="System to promote walking, biking, and public transit.">
      <text>This Transportation System must, to the greatest extent possible, promote walking, biking, and public transit.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-10" heading="System to promote economic development.">
      <text>This Transportation System must, to the greatest extent possible, promote economic development.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-11" heading="System to ensure equity.">
      <text>This Transportation System must, to the greatest extent possible, ensure equity by actively pursuing the elimination of health, economic, and access disparities.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-12" heading="System may be constructed incrementally.">
      <text>This Transportation System may be achieved through projects that fully implement complete streets or projects that incrementally implement complete streets through a series of smaller improvements over time.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§§" num="40-13 to 40-15" reserved="true" />
  </container>
  <container prefix="Part" num="III" heading="Complete Streets Advisory Committee">
    <section prefix="§" num="40-16" heading="Committee established.">
      <text>There is a Complete Streets Advisory Committee.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-17" heading="Composition.">
      <para num="(a)" heading="In general.">The Advisory Committee comprises the following officials (or their respective designees):<para num="(1)">the Transportation Director;</para>
        <para num="(2)">the Director of the City Department of Planning;</para>
        <para num="(3)">the Director of City Department of Public Works;</para>
        <para num="(4)">The Commissioner of the Department of Housing and Community Development; and</para>
        <para num="(5)">The Chief of the Baltimore City Fire Department.</para>
      </para>
      <para num="(b)" heading="Participation by and collaboration with Maryland Transit Administration.">
        <para num="(1)">The Chair of the Committee must include and extend to the Maryland Transit Administration (MTA) all invitations and opportunities for participation with the Advisory Committee as would be extended to any statutory member, exactly as if MTA were a member of the Committee.</para>
        <para num="(2)">Further, the Chair must, to the greatest extent possible, foster the strongest possible collaboration with MTA to pursue the goals of this subtitle.</para>
      </para>
      <para num="(c)" heading="Chair.">The Transportation Director is the Chair of the Advisory Committee.</para>
      <para num="(d)" heading="Subcommittees.">Subcommittees may be established.</para>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
    <section prefix="§" num="40-18" heading="Meetings; Quorum; Voting.">
      <para num="(a)" heading="Meetings.">The Advisory Committee meets on the call of the Chair as frequently as required to perform its duties and at least once per quarter.</para>
      <para num="(b)" heading="Quorum.">A majority of the members constitutes a quorum for the transaction of business.</para>
      <para num="(c)" heading="Voting.">An affirmative vote of at least a majority of a quorum is needed for any official action.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-19" heading="Minutes.">
      <para num="(a)" heading="Required.">Minutes must be taken of all meetings of the Advisory Committee.</para>
      <para num="(b)" heading="Public availability.">The minutes of every meeting must be made publically available by posting on the Transportation Department’s website within 7 days of the meeting.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-20" heading="Staff.">
      <text>The Transportation Department must provide staff for the Advisory Committee.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-21" heading="Duties.">
      <text>In addition to the other duties specified elsewhere in this subtitle, the Advisory Committee is responsible for:</text>
      <para num="(1)">promoting interagency cooperation in project identification, funding, and planning;</para>
      <para num="(2)">reviewing proposals for projects brought to the Committee by any of its members;</para>
      <para num="(3)">reviewing the status of projects to which this subtitle is applicable;</para>
      <para num="(4)">making recommendations to the Director about prioritization of projects;</para>
      <para num="(5)">reviewing reports on complete streets implementation, compliance, and performance; and</para>
      <para num="(6)">coordinating interagency cooperation in community engagement.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§§" num="40-22 to 40-25" reserved="true" />
  </container>
  <container prefix="Part" num="IV" heading="Design Standards">
    <section prefix="§" num="40-26" heading="Definitions.">
      <para num="(a)" heading="In general.">In this Part IV, the following terms have the meanings indicated.</para>
      <para num="(b)" heading="Transit street.">“Transit street” means any street on which a public transit vehicle provides fixed-route service.</para>
      <para num="(c)" heading="Truck route.">“Truck route” means any street so designated on the Transportation Department’s map of “Official Truck Routes”.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-27" heading="Design vehicles.">
      <para num="(a)" heading="“Design vehicle” defined.">In this section, “design vehicle” means a selected vehicle, with specific weight, dimensions, and operating characteristics, used to establish street design controls.</para>
      <para num="(b)" heading="In general.">The design vehicle used by the Transportation Department for all streets, except for transit streets and truck routes, must be the design vehicle recommended for neighborhood streets by the most recent edition of the National Association of City Transportation Officials, “Urban Street Design Guide”.</para>
      <para num="(c)" heading="Transit streets.">The design vehicle used by the Transportation Department for transit streets must be the design vehicle recommended for designated transit streets by the most recent edition of the National Association of City Transportation Officials, “Transit Street Design Guide”.</para>
      <para num="(d)" heading="Truck routes.">The design vehicle used by the Transportation Department for truck routes must be the design vehicle recommended for designated truck routes by the most recent edition of the National Association of City Transportation Officials, “Urban Street Design Guide”.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-28" heading="Design speed.">
      <para num="(a)" heading="Definitions.">
        <para num="(1)" heading="In general.">In this section, the following terms have the meanings indicated.</para>
        <para num="(2)" heading="Design speed.">“Design speed” means the speed used to determine geometric features of a street during the design phase.</para>
        <para num="(3)" heading="Target speed.">“Target speed” means the desired driver speed recommended by street typology.</para>
      </para>
      <para num="(b)" heading="Standard.">The design speed must be equal to the target speed and posted speed limit on any local, collector, and non-interstate arterial.</para>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
    <section prefix="§" num="40-29" heading="Lane widths.">
      <para num="(a)" heading="“Shared street” defined.">In this section, “shared street” means a street developed for mixed use by low volumes of slow-moving vehicular traffic mixed with high levels of walking.</para>
      <para num="(b)" heading="In general.">Except as provided in this section or otherwise required by law, the lanes of any street may not be more than 10 feet wide, but 9 feet is the preferred width.</para>
      <para num="(c)" heading="Exceptions.">
        <para num="(1)" heading="Local streets.">On a street designated on the Baltimore City Roadway Functional Classification Map as “local”, lanes may not be more than 9 feet wide.</para>
        <para num="(2)" heading="Transit streets and truck routes.">On a transit street or truck route, 1 lane in each direction may be up to 11 feet wide.</para>
        <para num="(3)" heading="Shared streets.">On a street designated as a “shared street”, lane width restrictions do not apply.</para>
      </para>
      <annotation type="History">Ord. 18-197 Ord. 19-332</annotation>
    </section>
    <section prefix="§" num="40-30" heading="DoT to use latest and best standards.">
      <text>In constructing and operating its Complete Streets Transportation System, the Transportation Department must use the latest and best standards, including:</text>
      <para num="(1)">National Association of City Transportation Officials:<para num="(i)">“Global Street Design Guide”.</para>
        <para num="(ii)">“Urban Street Design Guide”.</para>
        <para num="(iii)">“Transit Street Design Guide”.</para>
        <para num="(iv)">“Urban Bikeway Design Guide”.</para>
        <para num="(v)">“Urban Street Stormwater Guide”.</para>
      </para>
      <para num="(2)">American Association of State Highway and Transportation Officials:<para num="(i)">“Guide for Planning Design and Operation of Pedestrian Facilities”.</para>
        <para num="(ii)">“Guide for the Development of Bicycle Facilities”.</para>
      </para>
      <para num="(3)">Federal Highway Administration:<para num="(i)">“Separated Bike Lane Planning and Design Guide”.</para>
        <para num="(ii)">“Report on Incorporating On-Road Bicycle Networks into Resurfacing Projects”.</para>
      </para>
      <para num="(4)">Institute of Transportation Engineers, “Manual for Context Sensitive Solutions in Designing Major Urban Thoroughfares for Walkable Communities”.</para>
      <para num="(5)">National Cooperative Highway Research Program, Report 616, “Multi-Modal Level of Service Analysis for Urban Streets”.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-31" heading="Compliance with State and Federal funding requirements.">
      <text>The technical design standards required for state or federally funded projects will supersede local requirements in this subtitle and the Complete Streets Manual if there is an actual conflict between the local and state or federal standards and if funding will be impacted by adherence to the local standard.</text>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
    <section prefix="§§" num="40-32 to 40-35" reserved="true" />
  </container>
  <container prefix="Part" num="V" heading="Complete Streets Manual">
    <section prefix="§" num="40-36" heading="Director to adopt Complete Streets Manual.">
      <text>The Transportation Director, in consultation with the Complete Streets Advisory Committee, must adopt and may amend from time to time a Complete Streets Manual to carry out this subtitle.</text>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
    <section prefix="§" num="40-37" heading="Modal hierarchy.">
      <text>The Complete Streets Manual must include a hierarchy of the various modes of travel, indicating the priority to be given to each mode.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-38" heading="Street typologies.">
      <para num="(a)" heading="In General.">The Complete Streets Manual must include Complete Streets street typologies for classifying City streets.</para>
      <para num="(b)" heading="Considerations.">In creating street typologies, the Transportation Director, in consultation with the Advisory Committee, must consider:<para num="(1)">roadway form and function, including traffic volume, speed, and functional classification;</para>
        <para num="(2)">intersections and crossings;</para>
        <para num="(3)">bridges and overpasses;</para>
        <para num="(4)">loading zones;</para>
        <para num="(5)">overlays, including for transit streets, truck routes, and fire and emergency routes;</para>
        <para num="(6)">existing land use;</para>
        <para num="(7)">zoning designations;</para>
        <para num="(8)">public space guidelines;</para>
        <para num="(9)">stormwater management;</para>
        <para num="(10)">green infrastructure;</para>
        <para num="(11)">“Main Streets”, as part of the Baltimore Main Streets program;</para>
        <para num="(12)">public art;</para>
        <para num="(13)">arts districts;</para>
        <para num="(14)">historic preservation;</para>
        <para num="(15)">plans formally adopted by the Planning Commission; and</para>
        <para num="(16)">any other necessary considerations.</para>
      </para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-39" heading="Project prioritization process.">
      <para num="(a)" heading="In general.">The Complete Streets Manual must include a process for identifying, screening, and prioritizing projects seeking funding through federal or state grants, the City Capital Improvement Program, or other means.</para>
      <para num="(b)" heading="Process to include equity assessment.">This project prioritization process must include an equity assessment.  The equity assessment must consider transportation disparity trends based on race, gender, sexual orientation, age, disability, ethnicity, national origin, or income and recommend ways to reverse these trends.  It must assess and recommend ways to eliminate structural and institutional discrimination in transportation based on immutable characteristics.</para>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
    <section prefix="§" num="40-40" heading="Project delivery process.">
      <para num="(a)" heading="In general.">The Complete Streets Manual must include a project delivery process.</para>
      <para num="(b)" heading="Requirements.">This project delivery process must include:<para num="(1)">project phases from identification through construction through operation;</para>
        <para num="(2)">a chart listing the types of projects undertaken by, under the authority of, or under the supervision of the Department, and showing project phases for each type, and steps to complete each project phase, and whether, for each project type, a given step is required, optional, or inapplicable;</para>
        <para num="(3)">a decision tree showing how street typology, existing and planned land use, modal hierarchy, and any additional factors determine street design, and whether various elements are required, recommended, optional, or not required; and</para>
        <para num="(4)">a project management checklist.</para>
      </para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-41" heading="Equity in community engagement.">
      <text>The Complete Streets Manual must include community engagement policies that overcome barriers to engagement associated with race, income, age, disability, English language proficiency, and vehicle access of populations affected by a project, including a means of measuring success in overcoming these barriers.</text>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-42" heading="Public comment period.">
      <para num="(a)" heading="Publication of proposed Manual or amendment.">The Transportation Director must publish the proposed Complete Streets Manual or proposed amendment to the Manual by posting a copy of the proposal to the Department’s website at least 45 days before its adoption.</para>
      <para num="(b)" heading="Notice.">
        <para num="(1)">A notice of the proposed Manual or proposed amendment to the Manual must also be posted to the Transportation Department’s website, social media, and other channels of distribution available to the Department.</para>
        <para num="(2)">This notice must include:<para num="(i)">a summary of the proposed Manual or proposed amendment; and</para>
          <para num="(ii)">information on how a person can:<para num="(A)">obtain a copy of the proposal;</para>
            <para num="(B)">obtain a schedule of public hearing(s) to be held on the proposal; and</para>
            <para num="(C)">submit comments before the proposal is finalized and adopted.</para>
          </para>
        </para>
      </para>
      <para num="(c)" heading="Public hearing.">
        <para num="(1)">During the 45-day public comment period, the Director must also advertise and hold 1 or more public hearings on the proposed Manual or proposed amendment.</para>
        <para num="(2)">At least 1 hearing must be held in whole or in part between 6 pm and 8 pm.</para>
      </para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-43" heading="Final adoption.">
      <para num="(a)" heading="In general.">After the 45-day public comment and hearing period, the Director may modify and adopt the Complete Streets Manual.</para>
      <para num="(b)" heading="Filing with Legislative Reference.">A copy of the Complete Streets Manual and, from time to time, any amendment to the Manual must be filed with the Department of Legislative Reference before it becomes effective.</para>
      <para num="(c)" heading="Complete Streets Manual compliance.">DOT guidelines, policies, and procedures must be updated for compliance with the Complete Streets Manual.</para>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
    <section prefix="§§" num="40-44 to 40-45" reserved="true" />
  </container>
  <container prefix="Part" num="VI" heading="Annual Report and Public Accountability">
    <section prefix="§" num="40-46" heading="Annual report required.">
      <text>On or before August 31 of each year, the Director, in consultation with the Advisory Committee, must:</text>
      <para num="(1)">prepare a report assessing the status of the Complete Streets Transportation System; and</para>
      <para num="(2)">submit that report to:<para num="(i)">the Mayor;</para>
        <para num="(ii)">the City Council; and</para>
        <para num="(iii)">the Advisory Committee.</para>
      </para>
    </section>
    <section prefix="§" num="40-47" heading="Performance measures.">
      <para num="(a)" heading="In general.">Performance measures will be established using available data.</para>
      <para num="(b)" heading="Crash data.">
        <para num="(1)" heading="In general.">The annual report must measure year-over-year changes in crash data for all modes of travel as measured by:<para num="(i)">the “Maryland Statewide Vehicle Crashes Data” collected by the Maryland State Police;</para>
          <para num="(ii)">the “Fatality Analysis Reporting System” data collected by the National Highway Traffic Safety Administration; or</para>
          <para num="(iii)">other similar data.</para>
        </para>
        <para num="(2)" heading="Separate reporting by category.">Crash data for all modes of travel must be separately reported by the following categories:<para num="(i)">all crashes;</para>
          <para num="(ii)">injury crashes; and</para>
          <para num="(iii)">fatal crashes.</para>
        </para>
      </para>
      <para num="(c)" heading="Transit on-time performance.">The annual report must measure year-over-year change in transit on-time performance, as measured by:<para num="(1)">the performance data collected by the Maryland Transit Administration and published in the Maryland Department of Transportation’s Annual Attainment Report; or</para>
        <para num="(2)">other similar data collected by the Maryland Transit Administration or the Transportation Department.</para>
      </para>
      <para num="(d)" heading="Commute times.">The annual report must measure commute times for all modes of travel, as measured by the travel-time-to-work data reported in the American Communities Survey’s “Commuting (Journey to Work)”.</para>
      <para num="(e)" heading="Modal share.">The annual report must measure modal share, as measured by the means-of-transportation data reported in the American Communities Survey’s “Commuting (Journey to Work)”.</para>
      <para num="(f)" heading="Infrastructure data.">
        <para num="(1)" heading="In general.">The annual report must measure:<para num="(i)">the amount of transportation infrastructure built, upgraded, replaced, or rehabilitated in the previous 1-year period; and</para>
          <para num="(ii)">the total amount of infrastructure in the City’s overall transportation system.</para>
        </para>
        <para num="(2)" heading="Separate reporting by type.">The measurements required by paragraph (1) of this subsection must be separately reported by type, including:<para num="(i)">infrastructure for walking, biking, and public transit;</para>
          <para num="(ii)">public space infrastructure; and</para>
          <para num="(iii)">green infrastructure.</para>
        </para>
      </para>
      <para num="(g)" heading="Economic development measures.">The annual report must measure year-over-year changes in certain economic development data points and conditions:<para num="(1)">in each of the City’s “Main Streets”, as part of the Baltimore Main Streets program; and</para>
        <para num="(2)">in any other geographical area otherwise designated by the Advisory Committee.</para>
      </para>
      <para num="(h)" heading="Inventory of projects.">The annual report must include an inventory of all ongoing projects in any phase and the projected cost of those projects.</para>
      <para num="(i)" heading="Conflicts between local and state or federal standards.">The annual report must include a list of all instances in which the local standards set forth in this subtitle or in the Complete Streets Manual were or are planned to be superseded by state or federal standards, pursuant to &lt;cite data-path="|26|§40-31"&gt;§ 40-31 of this subtitle&lt;/cite&gt;, as well as citations and causes for the local standard being superseded.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-48" heading="Equity lens.">
      <para num="(a)" heading="Separate reporting by geographic subunit.">In preparing the annual report, the Department must separately report data by geographic subunit (e.g., census tract, traffic analysis zone, or the like).</para>
      <para num="(b)" heading="Separate reporting by race, income, and vehicle access.">The annual report must separately report data into the following categories:<para num="(1)">populations that are above and below the median number of persons of color for Baltimore City.</para>
        <para num="(2)">populations above and below 50% no vehicle access.</para>
        <para num="(3)">populations with a median income above and below the median household income for Baltimore City.</para>
      </para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-49" heading="Report and data to be publically available.">
      <para num="(a)" heading="Report to be posted.">The annual report must be made available to the public by posting it on the Transportation Department’s website.</para>
      <para num="(b)" heading="Data to be made available.">To the greatest extent possible, all underlying data used in preparing the annual report must be made available to the public.</para>
      <annotation type="History">Ord. 18-197</annotation>
    </section>
    <section prefix="§" num="40-50" heading="Accountability to communities.">
      <text>The Transportation Department, in consultation with the Complete Streets Advisory Committee, must conduct public meetings and other community engagement and outreach activities to present the Complete Streets annual report to the public and solicit public input.</text>
      <annotation type="History">Ord. 18-197</annotation>
      <annotation type="History">Ord. 19-332</annotation>
    </section>
  </container>
</baltimore-city-law>
