Medical Emergency Response StructuresThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Geological Survey, displays hospitals, medical centers, ambulance services, fire stations and EMS stations in the U.S. Per the USGS, "Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations."Greendale Fire DepartmentData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Medical & Emergency Response) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 135 (USGS National Structures Dataset - USGS National Map Downloadable Data Collection)OGC API Features Link: (Medical Emergency Response Structures - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: The National MapFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Theme CommunityThis data set is part of the NGDA Real Property Theme Community. Per the Federal Geospatial Data Committee (FGDC), Real Property is defined as "the spatial representation (location) of real property entities, typically consisting of one or more of the following: unimproved land, a building, a structure, site improvements and the underlying land. Complex real property entities (that is "facilities") are used for a broad spectrum of functions or missions. This theme focuses on spatial representation of real property assets only and does not seek to describe special purpose functions of real property such as those found in the Cultural Resources, Transportation, or Utilities themes."For other NGDA Content: Esri Federal Datasets

Fire brigade locations in Innsbruck

Fire Rescue Districts are areas which represent Cambridge Rescue teams housed in fire stations and areas which each rescue truck will be dispatched. Each fire station has Engine companies. Some have Rescue teams. Each Rescue District is used by the Emergency Communication Center (ECC) to dispatch emergency vehicles and first responders. Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription DIVISION type: Stringwidth: 16precision: 0

Please click here to view the Data Dictionary, a description of the fields in this table.Feature layer depicting Fire Station locations within the City of Scottsdale.

Fire Engine Districts are areas which represent both Cambridge Engine companies housed in fire stations and areas which each engine will be dispatched. Some fire stations have Ladder companies and Rescue units which are represented in a different layer. Each Engine District is used by the Emergency Communication Center (ECC) to dispatch emergency vehicles and first responders. Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription ENGINE type: Stringwidth: 16precision: 0

This GIS dataset shows the locations of fire hydrants at Casey Station. The data are formatted according to the SCAR Feature Catalogue (see Related URL below). Enter the Qinfo number of any feature at the 'Search datasets and quality' tab to search for data quality information about the feature: for example, the source of the data.

This dataset contains point features representing building locations of fire stations in the United States, District of Columbia, Puerto Rico and the U.S. Virgin Islands. The purpose of this collection is to represent the fire station locations on general purpose cartographic products. The data includes manned fire stations and buildings from which a fire response occurs, such as a volunteer fire department building to which fire fighters report for duty, but which is not continuously manned. The data includes both private and governmental entities. In some cases, where fire stations are known to exist but could not be located on a specific building, such as on a military base, airport or manufacturing location, a point was placed at the entrance or the general center of the facility or complex. Some fire locations are approximate, most prevalently in rural areas. Fire training facilities are not included unless these locations also have an active fire station. Locations solely for storing or maintaining fire equipment, or fire stations without a permanent location, were generally excluded.

This point layer contains the eight fire stations within the City of Cambridge.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription SITE_NAME type: Stringwidth: 50precision: 0 Fire station name

ADDRESS type: Stringwidth: 40precision: 0 Fire station address

PHONE type: Stringwidth: 16precision: 0 Fire station phone number

This GIS dataset shows the locations of fire hydrants at Davis Station. The data are formatted according to the SCAR Feature Catalogue (see Related URL below). Enter the Qinfo number of any feature at the 'Search datasets and quality' tab to search for data quality information about the feature: for example, the source of the data.

A point feature class of Miami-Dade County Operated Fire and Rescue Stations that provide emergency or administrative services to the public. Not every station has rescue services. Some stations have administrative responsibilities. Each station is responsible for a designated area (grids).Updated: Annually The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

This dataset contains Career and Volunteer Fire Stations in Maryland that are operated at the State level. This dataset was created using information from the 2012 Maryland State Fireman's Association (MSFA) Volunteer Stations dataset, the Maryland Coordination and Analysis Center (MCAC) Career and Volunteer Fire Station dataset, and the Community Anchor Institutions (CAI) Public Safety dataset.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/PublicSafety/MD_Fire/FeatureServer/0

North Chicago Fire Department

[Metadata] Locations of fire stations within the State of Hawaii as of August, 2017. Source: Received from and/or verified by counties in August, 2017. Hawaii Statewide GIS staff merged county layers into one statewide layer, keeping only the fire station name field from the individual county files. For additional attribute information, see the individual county fire station layers.For additional information, please refer to complete metadata at https://files.hawaii.gov/dbedt/op/gis/data/firestations.pdf or contact the Hawaii Statewide GIS Program, Office of Planning and Sustainable Development, State of Hawaii; PO Box 2359, Honolulu, Hi. 96804; (808) 587-2846; email: gis@hawaii.gov; Website: https://planning.hawaii.gov/gis.

Historical FiresLast updated on 06/17/2022OverviewThe national fire history perimeter data layer of conglomerated Agency Authoratative perimeters was developed in support of the WFDSS application and wildfire decision support for the 2021 fire season. The layer encompasses the final fire perimeter datasets of the USDA Forest Service, US Department of Interior Bureau of Land Management, Bureau of Indian Affairs, Fish and Wildlife Service, and National Park Service, the Alaska Interagency Fire Center, CalFire, and WFIGS History. Perimeters are included thru the 2021 fire season. Requirements for fire perimeter inclusion, such as minimum acreage requirements, are set by the contributing agencies. WFIGS, NPS and CALFIRE data now include Prescribed Burns. Data InputSeveral data sources were used in the development of this layer:Alaska fire history USDA FS Regional Fire History Data BLM Fire Planning and Fuels National Park Service - Includes Prescribed Burns Fish and Wildlife ServiceBureau of Indian AffairsCalFire FRAS - Includes Prescribed BurnsWFIGS - BLM & BIA and other S&LData LimitationsFire perimeter data are often collected at the local level, and fire management agencies have differing guidelines for submitting fire perimeter data. Often data are collected by agencies only once annually. If you do not see your fire perimeters in this layer, they were not present in the sources used to create the layer at the time the data were submitted. A companion service for perimeters entered into the WFDSS application is also available, if a perimeter is found in the WFDSS service that is missing in this Agency Authoratative service or a perimeter is missing in both services, please contact the appropriate agency Fire GIS Contact listed in the table below.AttributesThis dataset implements the NWCG Wildland Fire Perimeters (polygon) data standard.https://www.nwcg.gov/sites/default/files/stds/WildlandFirePerimeters_definition.pdfIRWINID - Primary key for linking to the IRWIN Incident dataset. The origin of this GUID is the wildland fire locations point data layer. (This unique identifier may NOT replace the GeometryID core attribute)INCIDENT - The name assigned to an incident; assigned by responsible land management unit. (IRWIN required). Officially recorded name.FIRE_YEAR (Alias) - Calendar year in which the fire started. Example: 2013. Value is of type integer (FIRE_YEAR_INT).AGENCY - Agency assigned for this fire - should be based on jurisdiction at origin.SOURCE - System/agency source of record from which the perimeter came.DATE_CUR - The last edit, update, or other valid date of this GIS Record. Example: mm/dd/yyyy.MAP_METHOD - Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality.GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; Digitized-Topo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; OtherGIS_ACRES - GIS calculated acres within the fire perimeter. Not adjusted for unburned areas within the fire perimeter. Total should include 1 decimal place. (ArcGIS: Precision=10; Scale=1). Example: 23.9UNQE_FIRE_ - Unique fire identifier is the Year-Unit Identifier-Local Incident Identifier (yyyy-SSXXX-xxxxxx). SS = State Code or International Code, XXX or XXXX = A code assigned to an organizational unit, xxxxx = Alphanumeric with hyphens or periods. The unit identifier portion corresponds to the POINT OF ORIGIN RESPONSIBLE AGENCY UNIT IDENTIFIER (POOResonsibleUnit) from the responsible unit’s corresponding fire report. Example: 2013-CORMP-000001LOCAL_NUM - Local incident identifier (dispatch number). A number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year. Field is string to allow for leading zeros when the local incident identifier is less than 6 characters. (IRWIN required). Example: 123456.UNIT_ID - NWCG Unit Identifier of landowner/jurisdictional agency unit at the point of origin of a fire. (NFIRS ID should be used only when no NWCG Unit Identifier exists). Example: CORMPCOMMENTS - Additional information describing the feature. Free Text.FEATURE_CA - Type of wildland fire polygon: Wildfire (represents final fire perimeter or last daily fire perimeter available) or Prescribed Fire or UnknownGEO_ID - Primary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature. Globally Unique Identifier (GUID).Cross-Walk from sources (GeoID) and other processing notesAK: GEOID = OBJECT ID of provided file geodatabase (4580 Records thru 2021), other federal sources for AK data removed. CA: GEOID = OBJECT ID of downloaded file geodatabase (12776 Records, federal fires removed, includes RX)FWS: GEOID = OBJECTID of service download combined history 2005-2021 (2052 Records). Handful of WFIGS (11) fires added that were not in FWS record.BIA: GEOID = "FireID" 2017/2018 data (416 records) provided or WFDSS PID (415 records). An additional 917 fires from WFIGS were added, GEOID=GLOBALID in source.NPS: GEOID = EVENT ID (IRWINID or FRM_ID from FOD), 29,943 records includes RX.BLM: GEOID = GUID from BLM FPER and GLOBALID from WFIGS. Date Current = best available modify_date, create_date, fire_cntrl_dt or fire_dscvr_dt to reduce the number of 9999 entries in FireYear. Source FPER (25,389 features), WFIGS (5357 features)USFS: GEOID=GLOBALID in source, 46,574 features. Also fixed Date Current to best available date from perimeterdatetime, revdate, discoverydatetime, dbsourcedate to reduce number of 1899 entries in FireYear.Relevant Websites and ReferencesAlaska Fire Service: https://afs.ak.blm.gov/CALFIRE: https://frap.fire.ca.gov/mapping/gis-dataBIA - data prior to 2017 from WFDSS, 2017-2018 Agency Provided, 2019 and after WFIGSBLM: https://gis.blm.gov/arcgis/rest/services/fire/BLM_Natl_FirePerimeter/MapServerNPS: New data set provided from NPS Fire & Aviation GIS. cross checked against WFIGS for any missing perimeters in 2021.https://nifc.maps.arcgis.com/home/item.html?id=098ebc8e561143389ca3d42be3707caaFWS -https://services.arcgis.com/QVENGdaPbd4LUkLV/arcgis/rest/services/USFWS_Wildfire_History_gdb/FeatureServerUSFS - https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_FireOccurrenceAndPerimeter_01/MapServerAgency Fire GIS ContactsRD&A Data ManagerVACANTSusan McClendonWFM RD&A GIS Specialist208-258-4244send emailJill KuenziUSFS-NIFC208.387.5283send email Joseph KafkaBIA-NIFC208.387.5572send emailCameron TongierUSFWS-NIFC208.387.5712send emailSkip EdelNPS-NIFC303.969.2947send emailJulie OsterkampBLM-NIFC208.258.0083send email Jennifer L. Jenkins Alaska Fire Service 907.356.5587 send email

This map layer shows the boundary of fire station first-in districts in the City of Columbus. First-in districts represent the zone of first response for each Columbus fire station. They represent logical places a particular station can respond to faster than all other surrounding stations within the city of Columbus. These zones are re-evaluated and re-created, if necessary, each time a fire station is closed or opened.These polygons are also used for internal reporting purposes (number of runs, average response times...etc.)

Fire stations within Fairfax County.

The Tempe Fire Medical Rescue Department (TFMR) is an “all-hazards” department that responds to all types of calls for service. The City of Tempe collects data from an annual Community Survey and the monthly TFMR Customer Service Survey to gauge resident perceptions about the quality and satisfaction of city services, programs and direction. The survey results help to determine priorities for the community as part of the City's ongoing strategic management process. This page provides data for the Fire Services Satisfaction performance measure. The performance measure dashboard is available at 1.04 Fire Services Satisfaction Includes detailed responses to Tempe Fire Medical Rescue Customer Satisfaction Survey. Surveys involving medical patients are sent out weekly to Tempe Medical Fire Rescue patients who provided email address at time of treatment. Results are calculated monthly for the prior months responses for review by Tempe Fire Medical Rescue administrators. Respondents are asked to answer several questions about their experience. Detailed information about the questions are included in the data dictionary for this dataset. Additional Information Source: Tempe Fire Medical Rescue Customer Satisfaction SurveyContact: Wydale Holmes / Hans Silberschlag (Fire Customer Survey)Contact E-Mail: wydale_holmes@tempe.govData Source Type: ExcelPreparation Method: Data downloaded from website (Survey Monkey)Publish Frequency: Monthly (Fire Customer Survey)Publish Method: ManualData Dictionary

This layer serves as an inventory of fire stations within Stark County, Ohio. It is part of the Stark County Community Features umbrella of layers, which includes CommunityFeatures, LiveWorkLocate, and EmergencyResponseFacilities. These layers depict places of interest throughout the county, including Airfields and Helipads, Colleges and Universities, Corporate Headquarters, EMS Facilities, Event Venues, Fire Stations, Golf Courses, Hospitals and Health Clinics, Museums and Historic Landmarks, Parks and Recreation Areas, Places of Worship, Police Stations, Post Offices, Public Libraries, Retail Centers, Schools and Daycares, and Senior Citizen Centers. These "community features" were first inventoried and digitized by the Stark County Regional Planning Commission (RPC) in 2008. The initial inventory was a collaborative effort between RPC and each community within the county, who provided lists of their respective features. Since then, each layer is periodically updated by RPC and Stark County GIS.

October 2022