This dataset was used for the paper "Face mask use during the COVID-19 pandemic: how risk perception, experience with COVID-19, and attitude towards government interact with country-wide policy stringency" forthcoming in BMC Public Health

Abstract Background: During the 2020 COVID-19 pandemic, governments imposed numerous regulations to protect public health, particularly the (mandatory) use of face masks. However, the appropriateness and effectiveness of face mask regulations have been widely discussed, as is apparent from the divergent measures taken across and within countries over time, including mandating, recommending, and discouraging their use. In this study, we analyse how country-level policy stringency and individual-level predictors associate with face mask use during the early stages of the global COVID-19 pandemic. Method: First, we study how (self and other-related) risk perception, (direct and indirect) experience with COVID-19, attitude towards government and policy stringency shape face mask use. Second, we study whether there is an interaction between policy stringency and the individual-level variables. We conduct multilevel analyses exploiting variation in face mask regulations across countries and using data from approximately 7,000 students collected in the beginning of the pandemic (weeks 17 through 19 2020) Results: We show that policy stringency is strongly positively associated with face mask use. We find a positive association between self-related risk perception and mask use, but no relationship of mask use with experience with COVID-19 and attitudes towards government. However, in the interaction analyses, we find that government trust and perceived clarity of communication moderate the link between stringency and mask use, with positive government perceptions relating to higher use in countries with regulations and to lower use in countries without regulations. Conclusions: We highlight that those countries that aim for widespread use of face masks should set strict measures, stress self-related risks of COVID-19, and use clear communication.

Dataset containing information related to non-NYPD Subjects involved in Force Incidents.

The Threat, Resistance, or Injury (TRI) Report is the primary means by which the NYPD records use of force incidents. All reportable instances of force – whether used by a member of the Department, or against the member – are recorded on a TRI Report. Data provided here are a result of the information captured on TRI Reports. Each record corresponds to a non-NYPD subject involved in a force incident. The data can be used to explore the various categories of force incidents and when and in which precinct they occurred. For any given incident, there may be one or more members of service involved. Since NYPD policy requires two-person patrols, most incidents will have at least two members. The data is used to populate the public facing Force Dashboard. (https://app.powerbigov.us/view?r=eyJrIjoiOGNhMjVhYTctMjk3Ny00MTZjLTliNDAtY2M2ZTQ5YWI3N2ViIiwidCI6IjJiOWY1N2ViLTc4ZDEtNDZmYi1iZTgzLWEyYWZkZDdjNjA0MyJ9).

The LAFD updated the public facing metrics to include Operational Response Time in April 2017. This dataset is an archive of the metrics beginning January 2016.

The Department of Health Care Services (DHCS) Long-Term Services and Supports (LTSS) Data Dashboard is an initiative of the Home and Community Based Services Spending Plan. The initiative's primary goal is to create a public-facing LTSS data dashboard to track demographic, utilization, quality, and cost data related to LTSS services. This dashboard will link statewide long-term care and home and community-based services (HCBS) data with the goal of increased transparency to make it possible for regulators, policymakers, and the public to be informed while the state continues to expand, enhance, and improve the quality of LTSS in all home, community, and congregate settings.

The first iteration of the LTSS Dashboard was released in December 2022 as an Open Data Portal file with 40 measures pertaining to LTSS beneficiaries, which includes ten different demographics, plan-related dimensions, and dual stratification. The December 2023 Data Release includes 16 new measures on the Medi-Cal LTSS Dashboard and Open Data Portal (Select “View Underlying Data”); and additional measures and dimensions, including dual stratification, will be added to the Open Data Portal in 2024.

Note: The LTSS Dashboard measures are based on certified eligible beneficiaries who were enrolled in Medi-Cal for one or more months during the reporting interval. Most of the DHCS LTSS dashboard measures report the annual number of certified eligible Medi-Cal beneficiaries who have used LTSS services within a year. Other departments may report on these programs differently. For example, the Department of Social Services (CDSS) reports monthly IHSS recipient/consumer counts. The California Department of Aging (CDA) reports monthly CBAS Medi-Cal participants. DHCS’ annual utilization / enrollment counts of IHSS and CBAS beneficiaries are larger than CDSS/CDA's monthly counts because of data source differences and new enrollment or program attrition over time. Monthly snap-shot measures (average monthly utilization) for IHSS and CBAS have been added to the LTSS Dashboard to align with CDSS and CDA monthly reporting.

Refer to the LTSS-Dashboard (ca.gov) program page for: 1) a Fact Sheet with highlights from the initial data release including changes over time in use of Home and Community-Based Services as well as select demographic information; 2) the Measure Specifications document – that describes business rules and inclusion/exclusion criteria related to age groups, plan types, aid code, geographic, or other important program/waiver-specific eligibility criteria; and 3) User guide – that shows how to navigate the Open Data Portal data file with specific examples.

This dataset has now been Retired as it has been replaced by "Administrative Boundaries - Environment Agency and Natural England Public Face Areas". This is for Approval for Access product AfA015 Environment Agency Administrative Boundaries set at 1:10,000 scale. These consist of 2 discrete data layers showing: Water Management Areas and Public Face Areas. Water management and Public Face boundaries are attributed with the name and address for each head office. This dataset is for Environment Agency Public Face Areas. Attribution statement: © Environment Agency copyright and/or database right 2015. All rights reserved.

Background: The analysis of clinical free text from patient records for research has potential to contribute to the medical evidence base but access to clinical free text is frequently denied by data custodians who perceive that the privacy risks of data-sharing are too high. Engagement activities with patients and regulators, where views on the sharing of clinical free text data for research have been discussed, have identified that stakeholders would like to understand the potential clinical benefits that could be achieved if access to free text for clinical research were improved. We aimed to systematically review all UK research studies which used clinical free text and report direct or potential benefits to patients, synthesizing possible benefits into an easy to communicate taxonomy for public engagement and policy discussions.Methods: We conducted a systematic search for articles which reported primary research using clinical free text, drawn from UK health record databases, which reported a benefit or potential benefit for patients, actionable in a clinical environment or health service, and not solely methods development or data quality improvement. We screened eligible papers and thematically analyzed information about clinical benefits reported in the paper to create a taxonomy of benefits.Results: We identified 43 papers and derived five themes of benefits: health-care quality or services improvement, observational risk factor-outcome research, drug prescribing safety, case-finding for clinical trials, and development of clinical decision support. Five papers compared study quality with and without free text and found an improvement of accuracy when free text was included in analytical models.Conclusions: Findings will help stakeholders weigh the potential benefits of free text research against perceived risks to patient privacy. The taxonomy can be used to aid public and policy discussions, and identified studies could form a public-facing repository which will help the health-care text analysis research community better communicate the impact of their work.

Many Happy Returns (MHR) is a multidisciplinary project funded by UK Research and Innovation (UKRI), as part of UKRI’s Enabling Research competition in its Smart Sustainable Plastic Packaging Challenge. MHR aims to encourage reusable plastic packaging systems as a means of reducing single-use plastic waste. The linguistics work package of MHR aims: (i) to understand how people think about plastic (re)use by examining their language; (ii) to assess how well public perceptions appear to align with public-facing information on reuse; and (iii) to inform best-practice recommendations for communication around plastic reuse. The project built a corpus of relevant language, analysed it using corpus software, and interpreted it in relation to a project ecosophy.

This is the controlled list of 14 operational area names, codes and descriptions of the Environment Agency and Natural England. This is the standard list for re-use across the Environment Agency and Natural England. The previous version contained only Environment Agency Area Names, but was updated to merge with Natural England public facing Areas. Attribution statement: © Environment Agency copyright and/or database right 2017. All rights reserved.

Public Facing Administrative Boundaries set at 1:10,000 scale. Public Face boundaries are attributed with standardised names and codes for each area. This dataset is for Environment Agency and Natural England Public Face Areas. Full metadata can be viewed on data.gov.uk.

Public Facing Administrative Boundaries set at 1:10,000 scale. Public Face boundaries are attributed with standardised names and codes for each area. This dataset is for Environment Agency and Natural England Public Face Areas.Derived from OS Boundary Line data and The Environment Agency and Natural England Boundaries are based on amalgamations of the Mean High Water Mark and local authority boundaries (OS Boundary-Line). Many Local Authorities have been merged others to create the areas for operational needs.Click Here to go straight to the DSP Metadata Page for this Dataset.

The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service includes perimeters for wildland fire incidents that meet the following criteria:Categorized in the IRWIN (Integrated Reporting of Wildland Fire Information) integration service as a Wildfire (WF) or Prescribed Fire (RX) recordFire Discovery Date is in the year 2025Is Valid and not "quarantined" in IRWIN due to potential conflicts with other recordsAttribution of the source polygon is set to a Feature Access of Public, a Feature Status of Approved, and an Is Visible setting of YesPerimeters are not available for every incident. For a complete set of features that meet the same IRWIN criteria, see the 2025 Wildland Fire Incident Locations to Date service.No "fall-off" rules are applied to this service. Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed every 5 minutes. Changes in the perimeter source may take up to 15 minutes to display.Perimeters are pulled from multiple sources with rules in place to ensure the most current or most authoritative shape is used.Attributes and their definitions can be found below. More detail about the NWCG Wildland Fire Event Polygon standard can be found here.Attributes:poly_SourceOIDThe OBJECTID value of the source record in the source dataset providing the polygon.poly_IncidentNameThe incident name as stored in the polygon source record.poly_MapMethodThe mapping method with which the polygon was derived.poly_GISAcresThe acreage of the polygon as stored in the polygon source record.poly_CreateDateSystem generated date for the date time the source polygon record was created (stored in UTC).poly_DateCurrentSystem generated date for the date time the source polygon record was last edited (stored in UTC).poly_PolygonDateTimeRepresents the date time that the polygon data was captured.poly_IRWINIDIRWIN ID stored in the polygon record.poly_FORIDFORID stored in the polygon record.poly_Acres_AutoCalcSystem calculated acreage of the polygon (geodesic WGS84 acres).poly_SourceGlobalIDThe GlobalID value of the source record in the source dataset providing the polygon.poly_SourceThe source dataset providing the polygon.attr_SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.attr_ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.attr_ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.attr_ContainmentDateTimeThe date and time a wildfire was declared contained. attr_ControlDateTimeThe date and time a wildfire was declared under control.attr_CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.attr_IncidentSizeReported for a fire. The minimum size is 0.1.attr_DiscoveryAcresAn estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.attr_EstimatedCostToDateThe total estimated cost of the incident to date.attr_FinalAcresReported final acreage of incident.attr_FFReportApprovedByTitleThe title of the person that approved the final fire report for the incident.attr_FFReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.attr_FFReportApprovedDateThe date that the final fire report was approved for the incident.attr_FireBehaviorGeneralA general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. attr_FireBehaviorGeneral1A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral2A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral3A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. attr_FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. attr_FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. attr_FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. attr_FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.attr_FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.attr_FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. attr_FireOutDateTimeThe date and time when a fire is declared out. attr_FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.attr_FireStrategyFullSuppPrcntIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.attr_FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.attr_FireStrategyPointZonePrcntIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.attr_FSJobCodeA code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.attr_FSOverrideCodeA code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.attr_GACCA code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.attr_ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.attr_ICS209RptForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.attr_ICS209RptForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. attr_ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates, and even multiple finals (as determined by business rules).attr_IncidentManagementOrgThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.attr_IncidentNameThe name assigned to an incident.attr_IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. attr_IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category further breaks down the Event Kind into more specific event categories.attr_IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.attr_InitialLatitudeThe latitude location of the initial reported point of origin specified in decimal degrees.attr_InitialLongitudeThe longitude location of the initial reported point of origin specified in decimal degrees.attr_InitialResponseAcresAn estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The minimum size must be 0.1. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_InitialResponseDateTimeThe date/time of the initial response to the incident. More specifically when the IC arrives and performs initial size up. attr_IrwinIDUnique identifier assigned to each incident record in IRWIN.attr_IsFireCauseInvestigatedIndicates if an investigation is underway or was completed to determine the cause of a fire.attr_IsFSAssistedIndicates if the Forest Service provided assistance on an incident outside their jurisdiction.attr_IsMultiJurisdictionalIndicates if the

This is the Environment Agency controlled list of old (pre-April 2014) Environment Agency Area Names and current Environment Agency and Natural England Area Names. It is for cross-reference purposes. Attribution statement: © Environment Agency copyright and/or database right 2017. All rights reserved.

Replication Data for: Talk or Type? The Effect of Digital Interfaces on Citizens’ Satisfaction with Standardized Public Services. Dataset, do Abstract: Although digital interfaces are increasingly pervading public administration, little is known about how replacing face-to-face interaction with digital interfaces affects citizens’ satisfaction with public service encounters. This study presents evidence from a vignette experiment conducted on a sample of German citizens (N=1.234) whereby we randomly varied the type of public-service request with regard to its psychological costs, service quality, and the type of interaction (face-to-face, self-service terminal, or app). We found that replacing face-to-face communication with a digital interface has no effect on citizens’ satisfaction, nor does it mitigate the effect of psychological costs, service failure, and recovery. Corroborating previous research on service recovery, we find that explaining and apologizing partially compensates for failure. Based on these results, we conclude that using digital interfaces does not undermine the goal to enhance citizen satisfaction with public services.

The ETJ Hosted View is a public-facing, read-only view of the ETJ Data Layer. This view has been filtered to allow for public access and use in applications and for data download. It represents the same ETJ boundaries as the full dataset, but it is streamlined for viewing purposes and is accessible to the public, making it easier for users to interact with the data without needing full access to the original feature layer.Data Includes:ETJ Boundaries (Polygon Data): A public view of the ETJ boundaries for all cities and towns within Montgomery County.City/Town and ETJ Information: The view includes basic data on cities and their ETJ boundaries for informational use.Data Source:The view is derived from the original ETJ Data Layer, which was created from city/town websites, city contacts, and Houston-Galveston Area Council data.Access:The ETJ Hosted View is publicly accessible, available for download, and can be embedded in public-facing applications.Update Frequency:The view is updated whenever the underlying ETJ Data Layer is updated, ensuring that the data remains current.

This project folder contains supplementary data files and software codes (Stata and Matlab) to replicate the estimation and simulation results documented in:"Face Masks Considerably Reduce COVID-19 Cases in Germany", written by Mitze, T., Kosfeld, R., Rode, J. and Wälde, K. (2020).The paper has been published in the Proceedings of the National Academy of Sciences (PNAS), 117 (51), 32293-32301 with DOI: https://doi.org/10.1073.An older working paper version of this research can be download as CESifo Working Paper No. 8479 from: https://www.cesifo.org/DocDL/cesifo1_wp8479.pdf.

The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service contains all wildland fire incidents from the IRWIN (Integrated Reporting of Wildland Fire Information) integration service that meet the following criteria:Categorized in IRWIN as a Wildfire (WF), Prescribed Fire (RX), or Incident Complex (CX) recordHas not been declared contained, controlled, nor outHas not had fire report record completed (certified)Is Valid and not "quarantined" in IRWIN due to potential conflicts with other records"Fall-off" rules are used to ensure that stale records are not retained. Records are removed from this service under the following conditions:Fire size is less than 10 acres (Size Class A or B), and fire information has not been updated in more than 3 daysFire size is between 10 and 100 acres (Size Class C), and fire information hasn't been updated in more than 8 daysFire size is larger than 100 acres (Size Class D-L), but fire information hasn't been updated in more than 14 days.Fire size used in the fall off rules is from the IncidentSize field.Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed from IRWIN every 5 minutes.Fall-off rules are enforced hourly.Attributes:SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency IA fire suppression on A, B, C & D size class fires on FS lands.ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.ContainmentDateTimeThe date and time a wildfire was declared contained.ControlDateTimeThe date and time a wildfire was declared under control.CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.IncidentSizeReported for a fire. The minimum size is 0.1.DiscoveryAcresAn estimate of acres burning when the fire is first reported by the first person to call in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.EstimatedCostToDateThe total estimated cost of the incident to date.FinalAcresReported final acreage of incident.FinalFireReportApprovedByTitleThe title of the person that approved the final fire report for the incident.FinalFireReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.FinalFireReportApprovedDateThe date that the final fire report was approved for the incident.FireBehaviorGeneralA general category describing how the fire is currently reacting to the influences of fuel, weather, and topography.FireBehaviorGeneral1A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography).FireBehaviorGeneral2A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography). FireBehaviorGeneral3A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography).FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. FireOutDateTimeThe date and time when a fire is declared out. FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.FireStrategyFullSuppPercentIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.FireStrategyPointZonePercentIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.FSJobCodeSpecific to the Forest Service, code use to indicate the FS job accounting code for the incident. Usually displayed as 2 char prefix on FireCode.FSOverrideCodeSpecific to the Forest Service, code used to indicate the FS override code for the incident. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.GACC"A code that identifies the wildland fire geographic area coordination center (GACC) at the point of origin for the incident. A GACC is a facility used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic area."ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.ICS209ReportForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.ICS209ReportForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates and multiple finals (as determined by business rules).IncidentManagementOrganizationThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.IncidentNameThe name assigned to an incident.IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category breaks down the Event Kind into more specific event categories.IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.InitialLatitudeThe latitude of the initial reported point of origin specified in decimal degrees.InitialLongitudeThe longitude of the initial reported point of origin specified in decimal degrees.InitialResponseAcresAn estimate of acres burning at the time of initial response (when the IC arrives and performs initial size up) The minimum size must be 0.1. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.InitialResponseDateTimeThe date/time of the initial response to the incident (when the IC arrives and performs initial size up)IrwinIDUnique identifier assigned to each incident record in IRWIN.IsFireCauseInvestigatedIndicates if an investigation is underway or was completed to determine the cause of a fire.IsFSAssistedIndicates if the Forest Service provided assistance on an incident outside their jurisdiction.IsMultiJurisdictionalIndicates if the incident covers multiple jurisdictions.IsReimbursableIndicates the cost of an incident may be another agency’s responsibility.IsTrespassIndicates if the incident is a trespass claim or if a bill will be pursued.IsUnifiedCommandIndicates whether the incident is being managed under Unified Command. Unified Command is an application of the ICS used when there is more than one agency with incident jurisdiction or when incidents cross political jurisdictions. Under Unified Command, agencies work together through their designated IC at a single incident command post to establish common objectives and issue a single Incident Action Plan.LocalIncidentIdentifierA number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year.ModifiedBySystemArcGIS Server username of system that last modified the IRWIN Incident record.PercentContainedIndicates the percent of incident area that is no longer active. Reference definition in fire line handbook when developing standard.PercentPerimeterToBeContainedIndicates the percent of perimeter left to be completed. This entry is appropriate for full suppression, point/zone protection, and confine fires, or any combination of these strategies. This entry is not used for wildfires managed entirely under a monitor strategy. (Note: Value is not currently being passed by ICS-209)POOCityThe closest city to the incident point of origin.POOCountyThe County Name

The LAFD updated the public facing metrics to include Operational Response Time in April 2017. This dataset is an archive of the metrics beginning January 2016.

This data aligns with WWC Certification requirements, and serves as the basis for our data warehouse and open data roadmap. It's a continual work in progress across all departments.Louisville Metro Technology Services builds data and technology platforms to ready our government for our community’s digital future.Data Dictionary:

Field Name

Description

Dataset Name

The official title of the dataset as listed in the inventory.

Brief Description of Data

A short summary explaining the contents and purpose of the dataset.

Data Source

The origin or system from which the data is collected or generated.

Home Department

The primary department responsible for the dataset.

Home Department Division

The specific division within the department that manages the dataset.

Data Steward (Business) Name

The name of person responsible for the dataset’s accuracy and relevance.

Data Custodian (Technical) Name)

The technical contact responsible for maintaining and managing the dataset infrastructure.

Data Classification

The sensitivity level of the data (e.g., Public, Internal, Confidential)

Data Format

The file format(s) in which the dataset is available (e.g., CSV, JSON, Shapefile).

Frequency of Data Change

How often the dataset is updated (e.g., Daily, Weekly, Monthly, Annually).

Time Spam

The overall time period the dataset covers.

Start Date

The beginning date of the data collection period.

End Date

The end date of the data collection period

Geographic Coverage

The geographic area that the dataset pertains to (e.g., Louisville Metro).

Geographic Granularity

The level of geographic detail (e.g., parcel, neighborhood, ZIP code).

Link to Existing Publication

A URL linking to the dataset’s public-facing page or open data portal entry.

The Police-Public Contact Survey (PPCS) provides detailed information on the nature and characteristics of face-to-face contacts between police and the public, including the reason for and outcome of the contact and the respondent's satisfaction with the contact. The data can be used to estimate the likelihood of different types of contact for residents with different demographic characteristics, including contacts involving the use of nonfatal force by police. The PPCS is used to collect data from a nationally representative sample of U.S. residents age 16 or older as a supplement to the National Crime Victimization Survey. To date, the PPCS has been conducted eight times by BJS: 1. 1996. Described in the BJS publication Police Use of Force: Collection of National Data (NCJ 165040). 2. 1999. Described in Contacts between Police and the Public: Findings from the 1999 National Survey (NCJ 184957). These data are archived as POLICE-PUBLIC CONTACT SURVEY, 1999: UNITED STATES. 3. 2002. Described in Contacts between Police and the Public: Findings from the 2002 National Survey (NCJ 207845). These data are archived as POLICE-PUBLIC CONTACT SURVEY, 2002: UNITED STATES. 4. 2005. Described in the BJS publication Contacts between Police and the Public, 2005 (NCJ 215243). These data are archived as POLICE-PUBLIC CONTACT SURVEY, 2005: UNITED STATES. 5. 2008. Described in the BJS publication Contacts between Police and the Public, 2008 (NCJ 234599). These data are archived as POLICE-PUBLIC CONTACT SURVEY, 2008 (ICPSR 32022). 6. 2011. Split sample design due to instrument changes. New instrument findings described in two publications: Police Behavior During Traffic and Street Stops, 2011 (NCJ 242937) and Requests for Police Assistance, 2011 (NCJ 242938). These data are archived as POLICE-PUBLIC CONTACT SURVEY, 2011 (ICPSR 34276). 7. 2015. Described in the BJS publication Contacts between Police and Public, 2015 (NCJ 251145). These data are archived as POLICE-PUBLIC CONTACT SURVEY, 2015 (ICPSR 36653). 8. 2018.Described in the BJS publication Contacts between Police and Public, 2018. These data are archived as POLICE-PUBLIC CONTACT SURVEY, 2018 (ICPSR 37916).

Number of customer transactions on County public-facing systems that provide or improve transparency into County operations. Data includes transactions on the Open Pierce County portal, the Public Records Request portal, the Remote Piloted Aircract System Program (RPAS) website for drone activity, the GIS open data portal, the Public GIS system, and the Public Nuisance portal.