<?xml version='1.0' encoding='utf-8'?>
<baltimore-city-law heading="Subtitle 9 – Open Data Program">
  <section prefix="§" num="9-1" heading="Definitions.">
    <para num="(a)" heading="In general.">In this subtitle, the following terms have the meanings indicated.</para>
    <para num="(b)" heading="Agency.">“Agency” means:<para num="(1)">any department, authority, office, board, commission, council, committee, or other unit of the City government; and</para>
      <para num="(2)">any individual not embraced in a unit of City Government who exercises authority comparable to that of the head of a unit of City government.</para>
    </para>
    <para num="(c)" heading="City data; Data.">“City data” or “data” means statistical, factual, quantitative, or qualitative information that is regularly maintained or created by or on behalf of:<para num="(1)">a City agency; or</para>
      <para num="(2)">a third-party contractor that creates or acquires information, records, or other data for and on behalf of a City agency.</para>
    </para>
    <para num="(d)" heading="Open data.">“Open data” means data made available online:<para num="(1)">in open format; and</para>
      <para num="(2)">with no legal encumbrances on use or reuse.</para>
    </para>
    <para num="(e)" heading="Open Data Portal; Web Portal.">“Open Data Portal” means the “Open Baltimore” Web Portal as maintained under this subtitle.</para>
    <para num="(f)" heading="Open format.">“Open format” means any widely accepted, nonproprietary, platform-independent, machine-readable method for formatting data that:<para num="(1)">permits automated processing of that data; and</para>
      <para num="(2)">facilitates search capabilities.</para>
    </para>
    <para num="(g)" heading="Dataset.">“Dataset” means a named collection of related records that contains data organized or formatted in a specific or prescribed way, often in tabular form.</para>
    <para num="(h)" heading="Protected information.">“Protected information” means any dataset or part of a dataset to which an agency is required or authorized to deny access pursuant to the Maryland Public Information Act (Title 4 of the State Code &lt;cite data-path="|general"&gt;General Provisions Article&lt;/cite&gt;) or any other applicable law.</para>
    <para num="(i)" heading="Sensitive information.">“Sensitive information” means any data that, if published in open format, could raise privacy, confidentiality, or security concerns, or could have the potential to jeopardize public health, safety, or welfare, to an extent that is exceeds the potential public benefit of publishing that data.</para>
    <para num="(j)" heading="Publishable data.">“Publishable data” means data that is neither protected information nor  sensitive information.</para>
    <annotation type="History">Ord. 16-463</annotation>
  </section>
  <section prefix="§" num="9-2" heading="Rules and regulations.">
    <text>Subject to Title 4 {“Administrative Procedure Act – Regulations”} of the &lt;cite data-path="|general"&gt;City General Provisions Article&lt;/cite&gt;, the City’s Chief Data Officer may adopt rules and regulations to carry out this subtitle.</text>
    <annotation type="History">Ord. 16-463</annotation>
    <annotation type="History">Text Conformed 05/5/21</annotation>
    <annotation type="Editor's Notes">By authority of Ordinance 20-431, Section 5, the Director of Legislative Reference, in consultation with the Law Department, has conformed the text of this section to refer expressly to the requirements of the recently-enacted Administrative Procedure Act that, effective January 15, 2021, governs the proposal, adoption, and publication of administrative rules and regulations.</annotation>
  </section>
  <section prefix="§" num="9-3" heading="Short Title.">
    <text>This subtitle may be cited as the “Baltimore City Open Data Program”.</text>
    <annotation type="History">Ord. 16-463</annotation>
  </section>
  <section prefix="§§" num="9-4 to 9-5" reserved="true" />
  <section prefix="§" num="9-6" heading="Program initiative.">
    <text>The Chief Data Officer shall oversee the development and adoption by the City of a program that allows the City to:</text>
    <para num="(1)">proactively release all publishable data, making it freely available in open formats, with no restrictons on use or reuse, and fully accessible to the broadest range of users for varying purposes;</para>
    <para num="(2)">publish high quality, updated data, with documentation and permanence to encourage maximal use;</para>
    <para num="(3)">continue and maintain the “Open Baltimore” Web Portal as the central location for publishable open data;</para>
    <para num="(4)">minimize limitations on the disclosure of public information, while appropriately safeguarding protected and sensitive information; and</para>
    <para num="(5)">encourage innovative uses of the City’s publishable data by agencies, the public, and other partners.</para>
    <annotation type="History">Ord. 16-463</annotation>
  </section>
  <section prefix="§" num="9-7" heading="Program implementation and governance.">
    <para num="(a)" heading="In general.">The Chief Data Officer shall work with the City’s agencies and officials to:<para num="(1)">identify for each agency a lead open data coordinator who will be responsible for managing that agency’s participation in the Open Data Program;</para>
      <para num="(2)">establish a comprehensive inventory of datasets held by each agency and to be published on the Open Data Portal and regularly updated;</para>
      <para num="(3)">develop and implement a process for determining the relative level of risk and public benefit associated with potentially sensitive, non-protected information, so as to make a determination about whether and how to publish that information;</para>
      <para num="(4)">develop and implement a process for prioritizing the publication of datasets on the Open Data Portal, taking into account:<para num="(i)">new and existing signals of interest from the public (such as the frequency of Public Information Act  requests);</para>
        <para num="(ii)">the City’s programmatic priorities;</para>
        <para num="(iii)">existing opportunities for data use in the public interest; and</para>
        <para num="(iv)">cost;</para>
      </para>
      <para num="(5)">establish processes for publishing datasets on the Open Data Portal, including processes for ensuring that datasets are reviewed for use-appropriate formats, quality, timeliness, and exclusion of protected and sensitive information;</para>
      <para num="(6)">develop and routinely update a public timeline for new dataset publication; and</para>
      <para num="(7)">ensure that published datasets are available for bulk download.</para>
    </para>
    <para num="(b)" heading="Feedback and collaboration.">In order to increase and improve use of the City’s open data, the Chief Data Officer shall actively encourage agency and public participation by providing regular opportunities for feedback and collaboration.</para>
    <annotation type="History">Ord. 16-463</annotation>
  </section>
  <section prefix="§" num="9-8" heading="Open Data Portal.">
    <para num="(a)" heading="City to maintain.">The City shall maintain the “Open Baltimore” Web Portal as  the Open Data Portal where the City’s publishable data will be publicly available.</para>
    <para num="(b)" heading="Dataset to be on open license.">Datasets published on the Open Data Portal shall be available to the public on an open license basis, with no restrictions on copying, publishing, further distributing, modifying, or using the data for any non-commercial or commercial purpose.</para>
    <annotation type="History">Ord. 16-463</annotation>
  </section>
  <section prefix="§" num="9-9" heading="Annual report.">
    <para num="(a)" heading="In general.">On or before June 30 of each year, the Chief Data Officer shall prepare and submit to the Mayor and the  City Council an annual Open Data Report.</para>
    <para num="(b)" heading="Contents.">The report shall include:<para num="(1)">an assessment of progress towards achievement of the goals of the Open Data Program;</para>
      <para num="(2)">an assessment of the current scope of agency compliance;</para>
      <para num="(3)">a list of datasets currently available on the Open Data Portal; and</para>
      <para num="(4)">a description of and publication timeline for datasets envisioned to be published on the Open Data Portal in the enduing year.</para>
    </para>
    <annotation type="History">Ord. 16-463</annotation>
  </section>
  <section prefix="§§" num="9-10 to 9-14" reserved="true" />
  <section prefix="§" num="9-15" heading="Program disclaimers.">
    <para num="(a)" heading="Data provided for informational purposes.">Data is made available on the Open Data Portal for informational purposes only.</para>
    <para num="(b)" heading="No warranties.">
      <para num="(1)">The City makes no express or implied warranty as to the completeness, accuracy, content, merchantability, or fitness for any particular use or purpose of any dataset made available on the Open Data Portal.</para>
      <para num="(2)">The City is not liable for any deficiency in the completeness, accuracy, content, merchantability, or fitness for any particular use or purpose of any dataset or of any third-party application using a dataset.</para>
    </para>
    <para num="(c)" heading="No private cause of action.">
      <para num="(1)">Neither this subtitle nor any Open Data Program plan or practice create a private right of action to enforce their provisions.</para>
      <para num="(2)">Failure to comply with this subtitle or any Open Data Program plan or practice does not result in any liability by the City.</para>
    </para>
    <para num="(d)" heading="Display of disclaimers.">The City shall conspicuously publish on the Open Data Portal the disclaimers contained in subsections (a) through (c) of this section.</para>
    <annotation type="History">Ord. 16-463</annotation>
  </section>
</baltimore-city-law>
