Data were created from Tennessee National Toxic Substance Incidents Program (NTSIP) database. Tennessee’s NTSIP performs acute chemical incidents surveillance. Since 2010, data have been aggregated from the National Response Center, Tennessee Emergency Management Agency, U.S. Department of Transportation, Tennessee Meth & Pharmaceutical Task Force, law enforcement records, and media reports. Usually within 48 hours, incident information was entered into the (national) database. Qualifying incidents according to the specifications of National Toxic Substance Incidents program (http://tn.gov/health/article/ntsip). This dataset was extracted from the Tennessee National Toxic Substance Incidents Program database. To learn more about the qualifying incidents and chemicals, please read the following documents:http://health.tn.gov/Environmental/PDFs/NTSIP/Event_Definition.pdfhttp://health.tn.gov/Environmental/PDFs/NTSIP/Chemicals.pdfATSDR’s Geospatial Research, Analysis & Services Program (GRASP) has created a tool to help public health officials and emergency response planners identify and map the communities that will most likely need support before, during, and after a hazardous event. The Social Vulnerability Index (SVI) indicates the relative vulnerability of every U.S. Census tract. Census tracts are subdivisions of counties for which the U.S. Census collects statistical data. The SVI ranks the tracts on 14 social factors, including; unemployment, lack of vehicle access, crowded housing, then further groups them into four related themes. Thus, each tract receives a ranking for each Census variable and for each of the four themes - as well as an overall ranking.

The Tempe Police Department prides itself in its continued efforts to reduce harm within the community and is providing this dataset on hate crime incidents that occur in Tempe.The Tempe Police Department documents the type of bias that motivated a hate crime according to those categories established by the FBI. These include crimes motivated by biases based on race and ethnicity, religion, sexual orientation, disability, gender and gender identity.The Bias Type categories provided in the data come from the Bias Motivation Categories as defined in the Federal Bureau of Investigation (FBI) National Incident-Based Reporting System (NIBRS) manual, version 2020.1 dated 4/15/2021. The FBI NIBRS manual can be found at https://www.fbi.gov/file-repository/ucr/ucr-2019-1-nibrs-user-manua-093020.pdf with the Bias Motivation Categories found on pages 78-79.Although data is updated monthly, there is a delay by one month to allow for data validation and submission.Information about Tempe Police Department's collection and reporting process for possible hate crimes is included in https://storymaps.arcgis.com/stories/a963e97ca3494bfc8cd66d593eebabaf.Additional InformationSource: Data are from the Law Enforcement Records Management System (RMS)Contact: Angelique BeltranContact E-Mail: angelique_beltran@tempe.govData Source Type: TabularPreparation Method: Data from the Law Enforcement Records Management System (RMS) are entered by the Tempe Police Department into a GIS mapping system, which automatically publishes to open data.Publish Frequency: MonthlyPublish Method: New data entries are automatically published to open data. Data Dictionary

Mapping incident locations from a CSV file in a web map (YouTube video).

Map Direct focus to show Subsidence Incident Reports. Please refer to https://floridadep.gov/fgs/sinkholes for more information. Originally created 02/04/2011, and moved to Map Direct Lite on 03/17/2015 Please contact GIS.Librarian@floridadep.gov for more information.

All BPD data on Open Baltimore is preliminary data and subject to change. The information presented through Open Baltimore represents Part I victim based crime data. The data do not represent statistics submitted to the FBI's Uniform Crime Report (UCR); therefore any comparisons are strictly prohibited. For further clarification of UCR data, please visit http://www.fbi.gov/about-us/cjis/ucr/ucr. Please note that this data is preliminary and subject to change. Prior month data is likely to show changes when it is refreshed on a monthly basis. All data is geocoded to the approximate latitude/longitude location of the incident and excludes those records for which an address could not be geocoded. Any attempt to match the approximate location of the incident to an exact address is strictly prohibited.

As a first step in understanding law enforcement agencies' use and knowledge of crime mapping, the Crime Mapping Research Center (CMRC) of the National Institute of Justice conducted a nationwide survey to determine which agencies were using geographic information systems (GIS), how they were using them, and, among agencies that were not using GIS, the reasons for that choice. Data were gathered using a survey instrument developed by National Institute of Justice staff, reviewed by practitioners and researchers with crime mapping knowledge, and approved by the Office of Management and Budget. The survey was mailed in March 1997 to a sample of law enforcement agencies in the United States. Surveys were accepted until May 1, 1998. Questions asked of all respondents included type of agency, population of community, number of personnel, types of crimes for which the agency kept incident-based records, types of crime analyses conducted, and whether the agency performed computerized crime mapping. Those agencies that reported using computerized crime mapping were asked which staff conducted the mapping, types of training their staff received in mapping, types of software and computers used, whether the agency used a global positioning system, types of data geocoded and mapped, types of spatial analyses performed and how often, use of hot spot analyses, how mapping results were used, how maps were maintained, whether the department kept an archive of geocoded data, what external data sources were used, whether the agency collaborated with other departments, what types of Department of Justice training would benefit the agency, what problems the agency had encountered in implementing mapping, and which external sources had funded crime mapping at the agency. Departments that reported no use of computerized crime mapping were asked why that was the case, whether they used electronic crime data, what types of software they used, and what types of Department of Justice training would benefit their agencies.

Step by step workflow the describes how to grant NIFC Org member accounts access to groups that house incident web maps for NPS park groups.

PurposeThis job aid will lead the GIS analyst through the process of manually creating an incident map journal and how to create additional pages for the journal. This process should be used at the beginning of an incident and then the journal should be maintained to assure it remains viable. The incident map journal serves as a curated center to place maps, apps, and dashboards relevant to the incident.

This job aid assumes a working knowledge of how to create maps, apps, and dashboards on ArcGIS Online. For a tutorial, go to the Create apps from maps - ArcGIS Tutorial.Example workflow for the Geo-Enabled Plans Session at InSPIRE. Job Aid developed by FEMA GIS to enable GIS analysts to rapidly spin-up a standardized incident journal.

The RMS Crime Incidents dataset consists of crime reports from the Detroit Police Department Records Management System (RMS). This data reflects reported criminal offenses that have occurred in the City of Detroit. Incident-based offense data is extracted from the Detroit Police Department's records management system hourly. This data set contains the most recent data available and is updated anytime DPD sends official crime records contributing to the Michigan Incident Crime Reporting (MICR) or the National Incident Based Reporting systems (reflected by the IBR Date field). It should be noted that some incidents involve the commission of multiple offenses, such as a domestic assault where property was also vandalized. In such cases, there is a row in the dataset for each offense, and the related offenses share a common Crime ID and Report Number.

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RDAnalysis@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data are updated daily. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

The FPD Incidents - Crimes Against Society contains incidents that were reported from 2010 to present to the Fayetteville Police Department, were responded to and from which a report was generated. This data is provided for informational purposes only. Totals in this file may vary from official totals following investigation of the incident. This data is not to be relied upon for official purposes. The date and time provided reflect when the incident was reported, not necessarily when it happened. There is a small margin of error when processing the data for mapping purposes; therefore, some incidents may either be omitted from, or inaccurately mapped.

This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire.Consumption Best Practices:As a service that is subject to Viral loads (very high usage), avoid adding Filters that use a Date/Time type field. These queries are not cacheable and WILL be subject to Rate Limiting by ArcGIS Online. To accommodate filtering events by Date/Time, we encourage using the included "Age" fields that maintain the number of Days or Hours since a record was created or last modified compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be supplied to many users without adding load on the service.When ingesting this service in your applications, avoid using POST requests, these requests are not cacheable and will also be subject to Rate Limiting measures.Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC). Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute.Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations.Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident ComplexArea Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed.Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed.Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires.Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives.Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities.IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers.Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands.Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes. Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created.GACC: A code that identifies one of the wildland fire geographic area coordination centers. 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.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event.Incident Management Organization: The 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.Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters)RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters.This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

The Regional Crime Analysis GIS (RCAGIS) is an Environmental Systems Research Institute (ESRI) MapObjects-based system that was developed by the United States Department of Justice Criminal Division Geographic Information Systems (GIS) Staff, in conjunction with the Baltimore County Police Department and the Regional Crime Analysis System (RCAS) group, to facilitate the analysis of crime on a regional basis. The RCAGIS system was designed specifically to assist in the analysis of crime incident data across jurisdictional boundaries. Features of the system include: (1) three modes, each designed for a specific level of analysis (simple queries, crime analysis, or reports), (2) wizard-driven (guided) incident database queries, (3) graphical tools for the creation, saving, and printing of map layout files, (4) an interface with CrimeStat spatial statistics software developed by Ned Levine and Associates for advanced analysis tools such as hot spot surfaces and ellipses, (5) tools for graphically viewing and analyzing historical crime trends in specific areas, and (6) linkage tools for drawing connections between vehicle theft and recovery locations, incident locations and suspects' homes, and between attributes in any two loaded shapefiles. RCAGIS also supports digital imagery, such as orthophotos and other raster data sources, and geographic source data in multiple projections. RCAGIS can be configured to support multiple incident database backends and varying database schemas using a field mapping utility.

Intended for the Public Use of these routes in cases of emergency and for Public planning

Please click here to view the Data Dictionary, a description of the fields in this table.The police incident report generates from the police department Record Management System (RMS) and includes one rolling year of data. Information automatically updates Sunday night. The most recent data available will begin one week prior from the updated date to allow for report approvals, ensuring the most accurate information available. Incidents included may not directly correlate to information found in other data sets nor should this data be considered for official Uniform Crime Reporting. For all official crime statistics please refer to the FBI and Arizona Department of Public Safety.Some information has been excluded and addresses shortened to the hundred block to protect privacy of victims and juveniles.

The FPD Incidents - Crimes Against Property contains incidents that were reported from 2010 to present to the Fayetteville Police Department, were responded to and from which a report was generated. This data is provided for informational purposes only. Totals in this file may vary from official totals following investigation of the incident. This data is not to be relied upon for official purposes. The date and time provided reflect when the incident was reported, not necessarily when it happened. There is a small margin of error when processing the data for mapping purposes; therefore, some incidents may either be omitted from, or inaccurately mapped.

The dataset contains a subset of locations and attributes of incidents reported in the ASAP (Analytical Services Application) crime report database by the District of Columbia Metropolitan Police Department (MPD). Visit https://crimecards.dc.gov for more information. This data is shared via an automated process where addresses are geocoded to the District's Master Address Repository and assigned to the appropriate street block. Block locations for some crime points could not be automatically assigned resulting in 0,0 for x,y coordinates. These can be interactively assigned using the MAR Geocoder.On February 1 2020, the methodology of geography assignments of crime data was modified to increase accuracy. From January 1 2020 going forward, all crime data will have Ward, ANC, SMD, BID, Neighborhood Cluster, Voting Precinct, Block Group and Census Tract values calculated prior to, rather than after, anonymization to the block level. This change impacts approximately one percent of Ward assignments.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structures.For more information about the wildfire response efforts, visit the CAL FIRE incident page.

Feature layer showing all the fires tracked by Cal OES GIS for the year to date.