Use of Force incidents at the Benefits Access Centers and SNAP Centers, disaggregated by: (a) The date the use of force incident occurred; (b) The job center or SNAP center where the use of force incident occurred; (c) The category of the use of force incident; (d) The number and category of injuries to a peace officer or security guard; (e) The number and category of injuries to any other individual; (f) The basis for the encounter; (g) Whether or not an arrest was made.

The physical boundary between two road reserve segments that prevents vehicular access; or the boundary of applicability of a road name between two road reserve segments that do not belong to the same road where one road runs into another (and hence there is no physical boundary or indication). The type of physical boundary relevant in each case is defined by the VEHICULAR_ACCESSS_FLAG attribute. The second use of the ACCESS_RESTRICTION table, as a barrier between applicability of road name is used simply for the purposes of graphical presentation. The difference in road name applicability can be determined from the links between the road reserve segment and the road to which it belongs. However, in most cases the barrier between roads would not be displayed on a map because it is obvious from the shapes of surrounding roads. This second use of the table caters for the case where it is not visibly obvious where one road ends and the next begins.

Creative Commons License Creative Common By Attribution 4.0 (Australian Capital Territory), Please read Data Terms and Conditions statement before data use.

The authoritative source of Acts, Bills, and secondary legislation. Dataset accessible as: Directory structure containing all versions of New Zealand Acts, Bills, secondary legislation published by the Parliamentary Counsel Office, and Supplementary Order Papers, that have been published to the New Zealand Legislation website (the Subscriber website) and the DTDs used by the XML data. Legislation RSS containing updates on Acts, Bills, and secondary legislation published by the Parliamentary Counsel Office, published on the New Zealand Legislation website. Custom ATOM/RSS feed builder tool. Note that, in contrast to legislation, in which there is no copyright, the feeds are licensed on the terms of the copyright statement on the New Zealand Legislation website.

The CRoW Act provides for public access on foot to certain types of land, amends the law relating to public rights of way, increases measures for the management and protection for Sites of Special Scientific Interest (SSSI) and strengthens wildlife enforcement legislation, and provides for better management of Areas of Outstanding Natural Beauty (AONB).

Under Section 4 of the CRoW Act it states the following: It shall be the duty of the Countryside Council for Wales (CCW now forms part of Natural Resources Wales (NRW)) to prepare, in respect of Wales, maps which together show; (a) all registered common land, and (b) all open country.

This dataset contains all Common Land with a higher right of access (Urban Commons, Commons with Deeds for Access, 1899 Commons Act) for areas of Wales, and Elan Valley Estate. This dataset does not include the Registered Common Land dataset.

Digitisation took place in 2014 for all Wales.

When using this data for Open Access, it should be used in conjunction with Open Country, Registered Common Land and Public Forests from the same years. Contact your local authority for access to and information about Registers of Common Land.

Code used to produce the results from the article "To Act or Not to Act? How Client Progression Affects Purposeful Performance Information Use at the Frontlines". Data was made available by the Danish Ministry of Childrent and Education. Restrictions apply to the availability of these data, which were used under license for the article. Researchers can apply for access to the data.

The DHS Data Inventory is a list of datasets used in and by the department. The dataset details include a verbose set of metadata identifying the source, quality, governance, publication, size and characteristics of the data, with pointers to the data access URL(s) and access rights for use within the department. The Data Inventory was created in response to legislative requirements of the Evidence Act (and Open Government Data Act). Metadata about datasets that are marked as 'public' are sent to Data.gov on a weekly basis.

This dataset contains counts and rates of young people aged 15–24 years who were not in employment, education, or training (NEET) during the 2015 calendar year. The report containing maps of this data can be found at www.stats.govt.nz/about_us/what-we-do/partnerships....
The data was provided by the Integrated Data Infrastructure (IDI) which brings together a wide range of data from government administrative sources and surveys.
Disclaimer
Any person who has had access to the unit-record data has certified that they have been shown, have read, and have understood section 81 of the Tax Administration Act 1994, which relates to secrecy.
Access to the anonymised data used in this study was provided by Stats NZ in accordance with security and confidentiality provisions of the Statistics Act 1975.
Only people authorised by the Statistics Act 1975 are allowed to see data about a particular person, household, business and or organisation and the results in these tables have been confidentialised to protect these groups from identification.
Careful consideration has been given to the privacy, security and confidentiality issues associated with using administrative and survey data in the IDI.
Any person who has had access to the unit-record data has certified that they have been shown, have read, and have understood section 81 of the Tax Administration Act 1994, which relates to secrecy.
Any discussion of data limitations or weaknesses is in the context of using the IDI for statistical purposes, and is not related to the data's ability to support Inland Revenue's core operational requirements.
Values of -999 are supressed to protect confidentiality.
Citation
Stats NZ (2017). Otago youth not in employment, education, or training (NEET): Collaborative research between Stats NZ Methodist Mission Southern using integrated data. Retrieved from www.stats.govt.nz.

Disclosed in response to a formal request under the Government Information (Public Access) Act 2009.

Information on the use of office space leased by the NSW Government.

This dataset contains counts and rates of young people aged 15–24 years who were not in employment, education, or training (NEET) during the 2015 calendar year. The report containing maps of this data can be found at www.stats.govt.nz/about_us/what-we-do/partnerships.... The data was provided by the Integrated Data Infrastructure (IDI) which brings together a wide range of data from government administrative sources and surveys. Disclaimer Any person who has had access to the unit-record data has certified that they have been shown, have read, and have understood section 81 of the Tax Administration Act 1994, which relates to secrecy. Access to the anonymised data used in this study was provided by Stats NZ in accordance with security and confidentiality provisions of the Statistics Act 1975. Only people authorised by the Statistics Act 1975 are allowed to see data about a particular person, household, business and or organisation and the results in these tables have been confidentialised to protect these groups from identification. Careful consideration has been given to the privacy, security and confidentiality issues associated with using administrative and survey data in the IDI. Any person who has had access to the unit-record data has certified that they have been shown, have read, and have understood section 81 of the Tax Administration Act 1994, which relates to secrecy. Any discussion of data limitations or weaknesses is in the context of using the IDI for statistical purposes, and is not related to the data's ability to support Inland Revenue's core operational requirements. Values of -999 are supressed to protect confidentiality. Citation Stats NZ (2017). Otago youth not in employment, education, or training (NEET): Collaborative research between Stats NZ Methodist Mission Southern using integrated data. Retrieved from www.stats.govt.nz.

Shows the conclusive boundaries of the mapping areas used for the CRoW mapping process.

Attitudes of companies towards data protection issues. Measures of data protection.
Topics: assessment of the level of protection of the national Data Protection Law for citizens as sufficient; familiarity with the provisions of the national Data Protection Law; attitude towards selected statements on the requirements of the data protection law: necessary, too strict, only necessary for certain sectors of activity; attitude towards the following statements: sufficient harmonization of the member states’ data protection laws to consider that personal data can be moved freely within the EU, data protection law in the own country is applied more strictly than in other member states; suitability of existing legislation on data protection with regard to the increasing exchange of personal data; use of Privacy Enhancing Technologies in the company; transfer of personal data via the internet; measures taken to enhance security of data transfer; transfer of personal data to countries outside the European Economic Area; type of transferred data; used means of transferring personal data; awareness of the term ´standard contractual clauses´ with regard to personal data transfer to countries outside the European Economic Area; regular contact of the company with national data protection authority; reasons for contact: notifications, asking for guidances, complaints against company, inspections, other reasons; maintenance and update of privacy policy notices by the company; monitoring of the examination of policy notes by the public; approximate number of requests for access to personal data received in 2006; complaints from people whose personal data are being currently processed; preferred actions to improve the implementation of the legal framework on data protection; attitude towards selected measures to fight international terrorism: monitor telephone calls, monitor internet use, monitor credit card use, monitor flight passenger data.

Demography: position of respondent at the company; information about the company (limited to activities in the own country): number of employees, independent or part of national or international group; company sector.

Additionally coded was: respondent ID; language of the interview; date of interview; time of the beginning of the interview; duration of the interview; country; weighting factor.

The Privacy Act gives individuals the right to access information about themselves that is held by the Office of the Auditor General of Canada (OAG), subject to certain specific and limited exceptions. The Privacy Act also protects the privacy of individuals by giving them substantial control over the collection, use, and disclosure of their personal information and by preventing others from having access to that information. This annual report on the Privacy Act at the OAG describes how we administered our responsibilities under the act during the 2019–20 fiscal year.

The Supervised Access Program provides separated and divorced families with a safe, neutral, child-focused meeting place. This is used for visits and exchanges between children and non-custodial parents or other adults, such as grandparents, where there are safety concerns. Contact is supervised by trained staff and volunteers.

These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed. This study contains Uniform Crime Report geocoded data obtained from St. Petersburg Police Department, Orlando Police Department, and Miami-Dade Police Department for the years between 2010 and 2014. The three primary goals of this study were: to determine whether Florida law HB 7095 (signed into law on June 3, 2011) and related legislation reduced the number of pain clinics abusively dispensing opioid prescriptions in the State to examine the spatial overlap between pain clinic locations and crime incidents to assess the logistics of administering the law The study includes: 3 Excel files: MDPD_Data.xlsx (336,672 cases; 6 variables), OPD_Data.xlsx (160,947 cases; 11 variables), SPPD_Data.xlsx (211,544 cases; 14 variables) 15 GIS Shape files (95 files total) Data related to respondents' qualitative interviews and the Florida Department of Health are not available as part of this collection. For access to data from the Florida Department of Health, interested researchers should apply directory to the FDOH.

The Privacy Act provides Canadian citizens, permanent residents and individuals present in Canada with the right to access personal information held about them by federal government institutions, such as FinDev Canada. It also protects against unauthorized disclosure of that personal information. The Privacy Act strictly controls how federal government institutions collect, use, store, disclose and dispose of personal information. Our Access to Information and Privacy Office is responsible for receiving and responding to all requests submitted under the Access to Information Act and the Privacy Act. Annual Report on the Administration of the Privacy Act 2022-2023

Collection of definitions of terms in English, French, German, Italian and Spanish extracted from the following data-related European laws:

1. Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE)

2. Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (Text with EEA relevance)

3. Commission Recommendation (EU) 2018/790 of 25 April 2018 on access to and preservation of scientific information

4. Regulation (EU) 2018/1807 of the European Parliament and of the Council of 14 November 2018 on a framework for the free flow of non-personal data in the European Union (Text with EEA relevance)

5. Directive (EU) 2019/790 of the European Parliament and of the Council of 17 April 2019 on copyright and related rights in the Digital Single Market and amending Directives 96/9/EC and 2001/29/EC (Text with EEA relevance)

6. Directive (EU) 2019/1024 of the European Parliament and of the Council of 20 June 2019 on open data and the re-use of public sector information (recast) (Open Data Directive)

7. Regulation (EU) 2022/868 of the European Parliament and of the Council of 30 May 2022 on European data governance and amending Regulation (EU) 2018/1724 (Data Governance Act) (Text with EEA relevance)

8. Regulation (EU) 2022/1925 of the European Parliament and of the Council of 14 September 2022 on contestable and fair markets in the digital sector and amending Directives (EU) 2019/1937 and (EU) 2020/1828 (Digital Markets Act) (Text with EEA relevance)

9. Regulation (EU) 2022/2065 of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services and amending Directive 2000/31/EC (Digital Services Act) (Text with EEA relevance)

10. Commission Implementing Regulation (EU) 2023/138 of 21 December 2022 laying down a list of specific high-value datasets and the arrangements for their publication and re-use (Text with EEA relevance)

11. Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 on harmonised rules on fair access to and use of data and amending Regulation (EU) 2017/2394 and Directive (EU) 2020/1828 (Data Act)

12. Regulation (EU) 2024/903 of the European Parliament and of the Council of 13 March 2024 laying down measures for a high level of public sector interoperability across the Union (Interoperable Europe Act)

13. Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence and amending Regulations (EC) No 300/2008, (EU) No 167/2013, (EU) No 168/2013, (EU) 2018/858, (EU) 2018/1139 and (EU) 2019/2144 and Directives 2014/90/EU, (EU) 2016/797 and (EU) 2020/1828 (Artificial Intelligence Act) Text with EEA relevance.

We assess which waters the Clean Water Act protects and how Supreme Court and White House rules change this regulation. We train a deep learning model using aerial imagery and geophysical data to predict 150,000 jurisdictional determinations from the Army Corps of Engineers, each deciding regulation for one water resource. Under a 2006 Supreme Court ruling, the Clean Water Act protects two-thirds of US streams and over half of wetlands; under a 2020 White House rule, it protects under half of streams and a fourth of wetlands, implying deregulation of 690,000 stream miles, 35 million wetland acres, and 30% of waters around drinking water sources. Our framework can support permitting, policy design, and use of machine learning in regulatory implementation problems., This dataset contains model outputs that were analyzed to produce the main results of the paper., , # Prediction data from: Machine learning predicts which rivers, streams, and wetlands the Clean Water Act regulates

This dataset contains data used to produce the predictions and other results reported in Greenhill et al. (2023). All data are publicly available and can be accessed either through Google Earth Engine or directly from the data providers, as described in Table S3 of the Supplementary Material. In addition, we are providing access to a subset of the data used for prediction, as well as all data needed for reproducing the results of the paper via this repository. We are also providing access to all data used to train the models in another Dryad repository: . All code written for the project is available at https://doi.org/10.5281/zenodo.10108709.

Description of the data and file structure

The files here include:

• Model predictions, inclu...

Collection of definitions of terms in English, French, German, Italian and Spanish extracted from the following data-related European laws:

Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE)

Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (Text with EEA relevance)

Commission Recommendation (EU) 2018/790 of 25 April 2018 on access to and preservation of scientific information

Regulation (EU) 2018/1807 of the European Parliament and of the Council of 14 November 2018 on a framework for the free flow of non-personal data in the European Union (Text with EEA relevance)

Directive (EU) 2019/790 of the European Parliament and of the Council of 17 April 2019 on copyright and related rights in the Digital Single Market and amending Directives 96/9/EC and 2001/29/EC (Text with EEA relevance)

Directive (EU) 2019/1024 of the European Parliament and of the Council of 20 June 2019 on open data and the re-use of public sector information (recast) (Open Data Directive)

Regulation (EU) 2021/695 of the European Parliament and of the Council of 28 April 2021 establishing Horizon Europe – the Framework Programme for Research and Innovation, laying down its rules for participation and dissemination, and repealing Regulations (EU) No 1290/2013 and (EU) No 1291/2013 (Text with EEA relevance)

Regulation (EU) 2022/868 of the European Parliament and of the Council of 30 May 2022 on European data governance and amending Regulation (EU) 2018/1724 (Data Governance Act) (Text with EEA relevance)

Regulation (EU) 2022/1925 of the European Parliament and of the Council of 14 September 2022 on contestable and fair markets in the digital sector and amending Directives (EU) 2019/1937 and (EU) 2020/1828 (Digital Markets Act) (Text with EEA relevance)

Regulation (EU) 2022/2065 of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services and amending Directive 2000/31/EC (Digital Services Act) (Text with EEA relevance)

Commission Implementing Regulation (EU) 2023/138 of 21 December 2022 laying down a list of specific high-value datasets and the arrangements for their publication and re-use (Text with EEA relevance)

Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 on harmonised rules on fair access to and use of data and amending Regulation (EU) 2017/2394 and Directive (EU) 2020/1828 (Data Act)

Regulation (EU) 2024/903 of the European Parliament and of the Council of 13 March 2024 laying down measures for a high level of public sector interoperability across the Union (Interoperable Europe Act)

Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence and amending Regulations (EC) No 300/2008, (EU) No 167/2013, (EU) No 168/2013, (EU) 2018/858, (EU) 2018/1139 and (EU) 2019/2144 and Directives 2014/90/EU, (EU) 2016/797 and (EU) 2020/1828 (Artificial Intelligence Act) Text with EEA relevance.

On October 15, 2013, Louisville Mayor Greg Fischer announced the signing of an open data policy executive order in conjunction with his compelling talk at the 2013 Code for America Summit. In nonchalant cadence, the mayor announced his support for complete information disclosure by declaring, "It's data, man."Sunlight Foundation - New Louisville Open Data Policy Insists Open By Default is the Future Open Data Annual ReportsSection 5.A. Within one year of the effective Data of this Executive Order, and thereafter no later than September 1 of each year, the Open Data Management Team shall submit to the Mayor an annual Open Data Report.The Open Data Management team (also known as the Data Governance Team is currently led by the city's Data Officer Andrew McKinney in the Office of Civic Innovation and Technology. Previously (2014-16) it was led by the Director of IT.Full Executive OrderEXECUTIVE ORDER NO. 1, SERIES 2013AN EXECUTIVE ORDERCREATING AN OPEN DATA PLAN. WHEREAS, Metro Government is the catalyst for creating a world-class city that provides its citizens with safe and vibrant neighborhoods, great jobs, a strong system of education and innovation, and a high quality of life; andWHEREAS, it should be easy to do business with Metro Government. Online government interactions mean more convenient services for citizens and businesses and online government interactions improve the cost effectiveness and accuracy of government operations; andWHEREAS, an open government also makes certain that every aspect of the built environment also has reliable digital descriptions available to citizens and entrepreneurs for deep engagement mediated by smart devices; andWHEREAS, every citizen has the right to prompt, efficient service from Metro Government; andWHEREAS, the adoption of open standards improves transparency, access to public information and improved coordination and efficiencies among Departments and partner organizations across the public, nonprofit and private sectors; andWHEREAS, by publishing structured standardized data in machine readable formats the Louisville Metro Government seeks to encourage the local software community to develop software applications and tools to collect, organize, and share public record data in new and innovative ways; andWHEREAS, in commitment to the spirit of Open Government, Louisville Metro Government will consider public information to be open by default and will proactively publish data and data containing information, consistent with the Kentucky Open Meetings and Open Records Act; andNOW, THEREFORE, BE IT PROMULGATED BY EXECUTIVE ORDER OF THE HONORABLE GREG FISCHER, MAYOR OF LOUISVILLE/JEFFERSON COUNTY METRO GOVERNMENT AS FOLLOWS:Section 1. Definitions. As used in this Executive Order, the terms below shall have the following definitions:(A) “Open Data” means any public record as defined by the Kentucky Open Records Act, which could be made available online using Open Format data, as well as best practice Open Data structures and formats when possible. Open Data is not information that is treated exempt under KRS 61.878 by Metro Government.(B) “Open Data Report” is the annual report of the Open Data Management Team, which shall (i) summarize and comment on the state of Open Data availability in Metro Government Departments from the previous year; (ii) provide a plan for the next year to improve online public access to Open Data and maintain data quality. The Open Data Management Team shall present an initial Open Data Report to the Mayor within 180 days of this Executive Order.(C) “Open Format” is any widely accepted, nonproprietary, platform-independent, machine-readable method for formatting data, which permits automated processing of such data and is accessible to external search capabilities.(D) “Open Data Portal” means the Internet site established and maintained by or on behalf of Metro Government, located at portal.louisvilleky.gov/service/data or its successor website.(E) “Open Data Management Team” means a group consisting of representatives from each Department within Metro Government and chaired by the Chief Information Officer (CIO) that is responsible for coordinating implementation of an Open Data Policy and creating the Open Data Report.(F) “Department” means any Metro Government department, office, administrative unit, commission, board, advisory committee, or other division of Metro Government within the official jurisdiction of the executive branch.Section 2. Open Data Portal.(A) The Open Data Portal shall serve as the authoritative source for Open Data provided by Metro Government(B) Any Open Data made accessible on Metro Government’s Open Data Portal shall use an Open Format.Section 3. Open Data Management Team.(A) The Chief Information Officer (CIO) of Louisville Metro Government will work with the head of each Department to identify a Data Coordinator in each Department. Data Coordinators will serve as members of an Open Data Management Team facilitated by the CIO and Metro Technology Services. The Open Data Management Team will work to establish a robust, nationally recognized, platform that addresses digital infrastructure and Open Data.(B) The Open Data Management Team will develop an Open Data management policy that will adopt prevailing Open Format standards for Open Data, and develop agreements with regional partners to publish and maintain Open Data that is open and freely available while respecting exemptions allowed by the Kentucky Open Records Act or other federal or state law.Section 4. Department Open Data Catalogue.(A) Each Department shall be responsible for creating an Open Data catalogue, which will include comprehensive inventories of information possessed and/or managed by the Department.(B) Each Department’s Open Data catalogue will classify information holdings as currently “public” or “not yet public”; Departments will work with Metro Technology Services to develop strategies and timelines for publishing open data containing information in a way that is complete, reliable, and has a high level of detail.Section 5. Open Data Report and Policy Review.(A) Within one year of the effective date of this Executive Order, and thereafter no later than September 1 of each year, the Open Data Management Team shall submit to the Mayor an annual Open Data Report.(B) In acknowledgment that technology changes rapidly, in the future, the Open Data Policy should be reviewed and considered for revisions or additions that will continue to position Metro Government as a leader on issues of openness, efficiency, and technical best practices.Section 6. This Executive Order shall take effect as of October 11, 2013.Signed this 11th day of October, 2013, by Greg Fischer, Mayor of Louisville/Jefferson County Metro Government.GREG FISCHER, MAYOR

On October 15, 2013, Louisville Mayor Greg Fischer announced the signing of an open data policy executive order in conjunction with his compelling talk at the 2013 Code for America Summit. In nonchalant cadence, the mayor announced his support for complete information disclosure by declaring, "It's data, man."Sunlight Foundation - New Louisville Open Data Policy Insists Open By Default is the Future Open Data Annual ReportsSection 5.A. Within one year of the effective Data of this Executive Order, and thereafter no later than September 1 of each year, the Open Data Management Team shall submit to the Mayor an annual Open Data Report.The Open Data Management team (also known as the Data Governance Team is currently led by the city's Data Officer Andrew McKinney in the Office of Civic Innovation and Technology. Previously (2014-16) it was led by the Director of IT.Full Executive OrderEXECUTIVE ORDER NO. 1, SERIES 2013AN EXECUTIVE ORDERCREATING AN OPEN DATA PLAN. WHEREAS, Metro Government is the catalyst for creating a world-class city that provides its citizens with safe and vibrant neighborhoods, great jobs, a strong system of education and innovation, and a high quality of life; andWHEREAS, it should be easy to do business with Metro Government. Online government interactions mean more convenient services for citizens and businesses and online government interactions improve the cost effectiveness and accuracy of government operations; andWHEREAS, an open government also makes certain that every aspect of the built environment also has reliable digital descriptions available to citizens and entrepreneurs for deep engagement mediated by smart devices; andWHEREAS, every citizen has the right to prompt, efficient service from Metro Government; andWHEREAS, the adoption of open standards improves transparency, access to public information and improved coordination and efficiencies among Departments and partner organizations across the public, nonprofit and private sectors; andWHEREAS, by publishing structured standardized data in machine readable formats the Louisville Metro Government seeks to encourage the local software community to develop software applications and tools to collect, organize, and share public record data in new and innovative ways; andWHEREAS, in commitment to the spirit of Open Government, Louisville Metro Government will consider public information to be open by default and will proactively publish data and data containing information, consistent with the Kentucky Open Meetings and Open Records Act; andNOW, THEREFORE, BE IT PROMULGATED BY EXECUTIVE ORDER OF THE HONORABLE GREG FISCHER, MAYOR OF LOUISVILLE/JEFFERSON COUNTY METRO GOVERNMENT AS FOLLOWS:Section 1. Definitions. As used in this Executive Order, the terms below shall have the following definitions:(A) “Open Data” means any public record as defined by the Kentucky Open Records Act, which could be made available online using Open Format data, as well as best practice Open Data structures and formats when possible. Open Data is not information that is treated exempt under KRS 61.878 by Metro Government.(B) “Open Data Report” is the annual report of the Open Data Management Team, which shall (i) summarize and comment on the state of Open Data availability in Metro Government Departments from the previous year; (ii) provide a plan for the next year to improve online public access to Open Data and maintain data quality. The Open Data Management Team shall present an initial Open Data Report to the Mayor within 180 days of this Executive Order.(C) “Open Format” is any widely accepted, nonproprietary, platform-independent, machine-readable method for formatting data, which permits automated processing of such data and is accessible to external search capabilities.(D) “Open Data Portal” means the Internet site established and maintained by or on behalf of Metro Government, located at portal.louisvilleky.gov/service/data or its successor website.(E) “Open Data Management Team” means a group consisting of representatives from each Department within Metro Government and chaired by the Chief Information Officer (CIO) that is responsible for coordinating implementation of an Open Data Policy and creating the Open Data Report.(F) “Department” means any Metro Government department, office, administrative unit, commission, board, advisory committee, or other division of Metro Government within the official jurisdiction of the executive branch.Section 2. Open Data Portal.(A) The Open Data Portal shall serve as the authoritative source for Open Data provided by Metro Government(B) Any Open Data made accessible on Metro Government’s Open Data Portal shall use an Open Format.Section 3. Open Data Management Team.(A) The Chief Information Officer (CIO) of Louisville Metro Government will work with the head of each Department to identify a Data Coordinator in each Department. Data Coordinators will serve as members of an Open Data Management Team facilitated by the CIO and Metro Technology Services. The Open Data Management Team will work to establish a robust, nationally recognized, platform that addresses digital infrastructure and Open Data.(B) The Open Data Management Team will develop an Open Data management policy that will adopt prevailing Open Format standards for Open Data, and develop agreements with regional partners to publish and maintain Open Data that is open and freely available while respecting exemptions allowed by the Kentucky Open Records Act or other federal or state law.Section 4. Department Open Data Catalogue.(A) Each Department shall be responsible for creating an Open Data catalogue, which will include comprehensive inventories of information possessed and/or managed by the Department.(B) Each Department’s Open Data catalogue will classify information holdings as currently “public” or “not yet public”; Departments will work with Metro Technology Services to develop strategies and timelines for publishing open data containing information in a way that is complete, reliable, and has a high level of detail.Section 5. Open Data Report and Policy Review.(A) Within one year of the effective date of this Executive Order, and thereafter no later than September 1 of each year, the Open Data Management Team shall submit to the Mayor an annual Open Data Report.(B) In acknowledgment that technology changes rapidly, in the future, the Open Data Policy should be reviewed and considered for revisions or additions that will continue to position Metro Government as a leader on issues of openness, efficiency, and technical best practices.Section 6. This Executive Order shall take effect as of October 11, 2013.Signed this 11th day of October, 2013, by Greg Fischer, Mayor of Louisville/Jefferson County Metro Government.GREG FISCHER, MAYOR