Learn state-of-the-art skills to build compelling, useful, and fun Web GIS apps easily, with no programming experience required.Building on the foundation of the previous three editions, Getting to Know Web GIS, fourth edition,features the latest advances in Esri’s entire Web GIS platform, from the cloud server side to the client side.Discover and apply what’s new in ArcGIS Online, ArcGIS Enterprise, Map Viewer, Esri StoryMaps, Web AppBuilder, ArcGIS Survey123, and more.Learn about recent Web GIS products such as ArcGIS Experience Builder, ArcGIS Indoors, and ArcGIS QuickCapture. Understand updates in mobile GIS such as ArcGIS Collector and AuGeo, and then build your own web apps.Further your knowledge and skills with detailed sections and chapters on ArcGIS Dashboards, ArcGIS Analytics for the Internet of Things, online spatial analysis, image services, 3D web scenes, ArcGIS API for JavaScript, and best practices in Web GIS.Each chapter is written for immediate productivity with a good balance of principles and hands-on exercises and includes:A conceptual discussion section to give you the big picture and principles,A detailed tutorial section with step-by-step instructions,A Q/A section to answer common questions,An assignment section to reinforce your comprehension, andA list of resources with more information.Ideal for classroom lab work and on-the-job training for GIS students, instructors, GIS analysts, managers, web developers, and other professionals, Getting to Know Web GIS, fourth edition, uses a holistic approach to systematically teach the breadth of the Esri Geospatial Cloud.AUDIENCEProfessional and scholarly. College/higher education. General/trade.AUTHOR BIOPinde Fu leads the ArcGIS Platform Engineering team at Esri Professional Services and teaches at universities including Harvard University Extension School. His specialties include web and mobile GIS technologies and applications in various industries. Several of his projects have won specialachievement awards. Fu is the lead author of Web GIS: Principles and Applications (Esri Press, 2010).Pub Date: Print: 7/21/2020 Digital: 6/16/2020 Format: Trade paperISBN: Print: 9781589485921 Digital: 9781589485938 Trim: 7.5 x 9 in.Price: Print: $94.99 USD Digital: $94.99 USD Pages: 490TABLE OF CONTENTSPrefaceForeword1 Get started with Web GIS2 Hosted feature layers and storytelling with GIS3 Web AppBuilder for ArcGIS and ArcGIS Experience Builder4 Mobile GIS5 Tile layers and on-premises Web GIS6 Spatial temporal data and real-time GIS7 3D web scenes8 Spatial analysis and geoprocessing9 Image service and online raster analysis10 Web GIS programming with ArcGIS API for JavaScriptPinde Fu | Interview with Esri Press | 2020-07-10 | 15:56 | Link.

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!

In addition to displaying earthquakes by magnitude, this service also provide earthquake impact details. Impact is measured by population as well as models for economic and fatality loss. For more details, see: PAGER Alerts. Consumption Best Practices:

As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cache-able relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cache-able.Update Frequency: Events are updated as frequently as every 5 minutes and are available up to 30 days with the following exceptions:

Events with a Magnitude LESS than 4.5 are retained for 7 daysEvents with a Significance value, 'sig' field, of 600 or higher are retained for 90 days In addition to event points, ShakeMaps are also provided. These have been dissolved by Shake Intensity to reduce the Layer Complexity.The specific layers provided in this service have been Time Enabled and include: Events by Magnitude: The event’s seismic magnitude value.Contains PAGER Alert Level: USGS PAGER (Prompt Assessment of Global Earthquakes for Response) system provides an automated impact level assignment that estimates fatality and economic loss.Contains Significance Level: An event’s significance is determined by factors like magnitude, max MMI, ‘felt’ reports, and estimated impact.Shake Intensity: The Instrumental Intensity or Modified Mercalli Intensity (MMI) for available events.For field terms and technical details, see: ComCat DocumentationAlternate SymbologiesVisit the Classic USGS Feature Layer item for a Rainbow view of Shakemap features.RevisionsAug 14, 2024: Added a default Minimum scale suppression of 1:6,000,000 on Shake Intensity layer.Jul 11, 2024: Updated event popup, setting 'Tsunami Warning' text to 'Alert Possible' when flag is present. Also included hyperlink to tsunami warning center.Feb 13, 2024: Updated feed logic to remove Superseded eventsThis map is provided for informational purposes and is not monitored 24/7 for accuracy and currency. Always refer to USGS source for official guidance.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!

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 very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.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 Complex

Area 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!

Links to recordings of the Integrated Services Program and 9-1-1 & Geospatial Services Bureau webinar series, including NG9-1-1 GIS topics such as: data preparation; data provisioning and maintenance; boundary best practices; and extract, transform, and load (ETL). Offerings include:Topic: Virginia Next Generation 9-1-1 Dashboard and Resources Update Description: Virginia recently updated the NG9-1-1 Dashboard with some new tabs and information sources and continues to develop new resources to assist the GIS data work. This webinar provides an overview of changes, a demonstration of new functionality, and a guide to finding and using new resources that will benefit Virginia public safety and GIS personnel with roles in their NG9-1-1 projects. Wednesday 16 June 2021. Recording available at: https://vimeo.com/566133775Topic: Emergency Service Boundary GIS Data Layers and Functions in your NG9-1-1 PSAP Description: Law, Fire, and Emergency Medical Service (EMS) Emergency Service Boundary (ESB) polygons are required elements of the NENA NG9-1-1 GIS data model stack that indicate which agency is responsible for primary response. While this requirement must be met in your Virginia NG9-1-1 deployment with AT&T and Intrado, there are quite a few ways you could choose to implement these polygons. PSAPs and their GIS support must work together to understand how this information will come into a NG9-1-1 i3 PSAP and how it will replace traditional ESN information in order to make good choices while implementing these layers. This webinar discusses:the function of ESNs in your legacy 9-1-1 environment, the role of ESBs in NG9-1-1, and how ESB information appears in your NG9-1-1 PSAP. Wednesday, 22 July 2020. Recording available at: https://vimeo.com/441073056#t=360sTopic: "The GIS Folks Handle That": What PSAP Professionals Need to Know about the GIS Project Phase of Next Generation 9-1-1 DeploymentDescription: Next Generation 9-1-1 (NG9-1-1) brings together the worlds of emergency communication and spatial data and mapping. While it may be tempting for PSAPs to outsource cares and concerns about road centerlines and GIS data provisioning to 'the GIS folks', GIS staff are crucial to the future of emergency call routing and location validation. Data required by NG9-1-1 usually builds on data that GIS staff already know and use for other purposes, so the transition requires them to learn more about PSAP operations and uses of core data. The goal of this webinar is to help the PSAP and GIS worlds come together by explaining the role of the GIS Project in the Virginia NG9-1-1 Deployment Steps, exploring how GIS professionals view NG9-1-1 deployment as a project, and fostering a mutual understanding of how GIS will drive NG9-1-1. 29 January 2020. Recording available at: https://vimeo.com/showcase/9791882/video/761225474Topic: Getting Your GIS Data from Here to There: Processes and Best Practices for Extract, Transform and Load (ETL) Description: During the fall of 2019, VITA-ISP staff delivered workshops on "Tools and Techniques for Managing the Growing Role of GIS in Enterprise Software." This session presents information from the workshops related to the process of extracting, transforming, and loading data (ETL), best practices for ETL, and methods for data schema comparison and field mapping as a webinar. These techniques and skills assist GIS staff with their growing role in Next Generation 9-1-1 but also apply to many other projects involving the integration and maintenance of GIS data. 19 February 2020. Recording available at: https://vimeo.com/showcase/9791882/video/761225007Topic: NG9-1-1 GIS Data Provisioning and MaintenanceDescription: VITA ISP pleased to announce an upcoming webinar about the NG9-1-1 GIS Data Provisioning and Maintenance document provided by Judy Doldorf, GISP with the Fairfax County Department of Information Technology and RAC member. This document was developed by members of the NG9-1-1 GIS workgroup within the VITA Regional Advisory Council (RAC) and is intended to provide guidance to local GIS and PSAP authorities on the GIS datasets and associated GIS to MSAG/ALI validation and synchronization required for NG9-1-1 services. The document also provides guidance on geospatial call routing readiness and the short- and long-term GIS data maintenance workflow procedures. In addition, some perspective and insight from the Fairfax County experience in GIS data preparation for the AT&T and West solution will be discussed in this webinar. 31 July 2019. Recording available at: https://vimeo.com/showcase/9791882/video/761224774Topic: NG9-1-1 Deployment DashboardDescription: I invite you to join us for a webinar that will provide an overview of our NG9-1-1 Deployment Dashboard and information about other online ISP resources. The ISP website has been long criticized for being difficult to use and find information. The addition of the Dashboard and other changes to the website are our attempt to address some of these concerns and provide an easier way to find information especially as we undertake NG9-1-1 deployment. The Dashboard includes a status map of all Virginia PSAPs as it relates to the deployment of NG9-1-1, including the total amount of funding requested by the localities and awards approved by the 9-1-1 Services Board. During this webinar, Lyle Hornbaker, Regional Coordinator for Region 5, will navigate through the dashboard and provide tips on how to more effectively utilize the ISP website. 12 June 2019. Recording not currently available. Please see the Virginia Next Generation 9-1-1 Dashboard and Resources Update webinar recording from 16 June 2021. Topic: PSAP Boundary Development Tools and Process RecommendationDescription: This webinar will be presented by Geospatial Program Manager Matt Gerike and VGIN Coordinator Joe Sewash. With the release of the PSAP boundary development tools and PSAP boundary segment compilation guidelines on the VGIN Clearinghouse in March, this webinar demonstrates the development tools, explains the process model, and discusses methods, tools, and resources available for you as you work to complete PSAP boundary segments with your neighbors. 15 May 2019. Recording available at: https://www.youtube.com/watch?v=kI-1DkUQF9Q&feature=youtu.beTopic: NG9-1-1 Data Preparation - Utilizing VITA's GIS Data Report Card ToolDescription: This webinar, presented by VGIN Coordinator Joe Sewash, Geospatial Program Manager Matt Gerike, and Geospatial Analyst Kenny Brevard will provide an overview of the first version of the tools that were released on March 25, 2019. These tools will allow localities to validate their GIS data against the report card rules, the MSAG and ALI checks used in previous report cards, and the analysis listed in the NG9-1-1 migration proposal document. We will also discuss the purpose of the tools, input requirements, initial configuration, how to run them, and how to make sense of your results. 10 April 2019. Recording available at: https://vimeo.com/showcase/9791882/video/761224495Topic: NG9-1-1 PSAP Boundary Best Practice WebinarDescription: During the months of November and December, VITA ISP staff hosted regional training sessions about best practices for PSAP boundaries as they relate to NG9-1-1. These sessions were well attended and very interactive, therefore we feel the need to do a recap and allow those that may have missed the training to attend a makeup session. 30 January 2019. Recording not currently available. Please see the PSAP Boundary Development Tools and Process Recommendation webinar recording from 15 May 2019.Topic: NG9-1-1 GIS Overview for ContractorsDescription: The Commonwealth of Virginia has started its migration to next generation 9-1-1 (NG9-1-1). This migration means that there will be a much greater reliance on geographic information (GIS) to locate and route 9-1-1 calls. VITA ISP has conducted an assessment of current local GIS data and provided each locality with a report. Some of the data from this report has also been included in the localities migration proposal, which identifies what data issues need to be resolved before the locality can migrate to NG9-1-1. Several localities in Virginia utilize a contractor to maintain their GIS data. This webinar is intended for those contractors to review the data in the report, what is included in the migration proposal and how they may be called on to assist the localities they serve. It will still ultimately be up to each locality to determine whether they engage a contractor for assistance, but it is important for the contractor community to understand what is happening and have an opportunity to ask questions about the intent and goals. This webinar will provide such an opportunity. 22 August 2018. Recording not currently available. Please contact us at NG911GIS@vdem.virginia.gov if you are interested in this content.

This layer presents detectable thermal activity from VIIRS satellites for the last 7 days. VIIRS Thermal Hotspots and Fire Activity is a product of NASA’s Land, Atmosphere Near real-time Capability for EOS (LANCE) Earth Observation Data, part of NASA's Earth Science Data.Consumption Best Practices:

As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.Source: NASA LANCE - VNP14IMG_NRT active fire detection - WorldScale/Resolution: 375-meterUpdate Frequency: Hourly using the aggregated live feed methodologyArea Covered: WorldWhat can I do with this layer?This layer represents the most frequently updated and most detailed global remotely sensed wildfire information. Detection attributes include time, location, and intensity. It can be used to track the location of fires from the recent past, a few hours up to seven days behind real time. This layer also shows the location of wildfire over the past 7 days as a time-enabled service so that the progress of fires over that timeframe can be reproduced as an animation.The VIIRS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.Fire points in this service are generally available within 3 1/4 hours after detection by a VIIRS device. LANCE estimates availability at around 3 hours after detection, and esri livefeeds updates this feature layer every 15 minutes from LANCE.Even though these data display as point features, each point in fact represents a pixel that is >= 375 m high and wide. A point feature means somewhere in this pixel at least one "hot" spot was detected which may be a fire.VIIRS is a scanning radiometer device aboard the Suomi NPP, NOAA-20, and NOAA-21 satellites that collects imagery and radiometric measurements of the land, atmosphere, cryosphere, and oceans in several visible and infrared bands. The VIIRS Thermal Hotspots and Fire Activity layer is a livefeed from a subset of the overall VIIRS imagery, in particular from NASA's VNP14IMG_NRT active fire detection product. The downloads are automatically downloaded from LANCE, NASA's near real time data and imagery site, every 15 minutes.The 375-m data complements the 1-km Moderate Resolution Imaging Spectroradiometer (MODIS) Thermal Hotspots and Fire Activity layer; they both show good agreement in hotspot detection but the improved spatial resolution of the 375 m data provides a greater response over fires of relatively small areas and provides improved mapping of large fire perimeters.Attribute informationLatitude and Longitude: The center point location of the 375 m (approximately) pixel flagged as containing one or more fires/hotspots.Satellite: Whether the detection was picked up by the Suomi NPP satellite (N) or NOAA-20 satellite (1) or NOAA-21 satellite (2). For best results, use the virtual field WhichSatellite, redefined by an arcade expression, that gives the complete satellite name.Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel. This value is based on a collection of intermediate algorithm quantities used in the detection process. It is intended to help users gauge the quality of individual hotspot/fire pixels. Confidence values are set to low, nominal and high. Low confidence daytime fire pixels are typically associated with areas of sun glint and lower relative temperature anomaly (<15K) in the mid-infrared channel I4. Nominal confidence pixels are those free of potential sun glint contamination during the day and marked by strong (>15K) temperature anomaly in either day or nighttime data. High confidence fire pixels are associated with day or nighttime saturated pixels.Please note: Low confidence nighttime pixels occur only over the geographic area extending from 11 deg E to 110 deg W and 7 deg N to 55 deg S. This area describes the region of influence of the South Atlantic Magnetic Anomaly which can cause spurious brightness temperatures in the mid-infrared channel I4 leading to potential false positive alarms. These have been removed from the NRT data distributed by FIRMS.FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).DayNight: D = Daytime fire, N = Nighttime fireHours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.Additional information can be found on the NASA FIRMS site FAQ.Note about near real time data:Near real time data is not checked thoroughly before it's posted on LANCE or downloaded and posted to the Living Atlas. NASA's goal is to get vital fire information to its customers within three hours of observation time. However, the data is screened by a confidence algorithm which seeks to help users gauge the quality of individual hotspot/fire points. Low confidence daytime fire pixels are typically associated with areas of sun glint and lower relative temperature anomaly (<15K) in the mid-infrared channel I4. Medium confidence pixels are those free of potential sun glint contamination during the day and marked by strong (>15K) temperature anomaly in either day or nighttime data. High confidence fire pixels are associated with day or nighttime saturated pixels.RevisionsMarch 7, 2024: Updated to include source data from NOAA-21 Satellite.September 15, 2022: Updated to include 'Hours_Old' field. Time series has been disabled by default, but still available.July 5, 2022: Terms of Use updated to Esri Master License Agreement, no longer stating that a subscription is required!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!

MassGIS is working very closely with the State 911 Department in the state’s Executive Office of Public Safety and Security on the Next Generation 911 Emergency Call System. MassGIS developed and is maintaining the map and address information that are at the heart of this new system. Statewide deployment of this new 9-1-1 call routing system was completed in 2018.Address sources include the Voter Registration List from the Secretary of the Commonwealth, site addresses from municipal departments (primarily assessors), and customer address lists from utilities. Addresses from utilities were “anonymized” to protect customer privacy. The MAD was also validated for completeness using the Emergency Service List (a list of telephone land line addresses) from Verizon.The MAD contains both tabular and spatial data, with addresses being mapped as point features. At present, the MAD contains 3.2 million address records and 2.2 million address points. As the database is very dynamic with changes being made daily, the data available for download will be refreshed weekly.A Statewide Addressing Standard for Municipalities is another useful asset that has been created as part of this ongoing project. It is a best practices guide for the creation and storage of addresses for Massachusetts Municipalities.Points features with each point having an address to the building/floor/unit level, when that information is available. Where more than one address is located at a single location multiple points are included (i.e. "stacked points"). The points for the most part represent building centroids. Other points are located as assessor parcel centroids.Points will display at scales 1:75,000 and closer.MassGIS' service does not contain points for Boston; they may be accessed at https://data.boston.gov/dataset/live-street-address-management-sam-addresses/resource/873a7659-68b6-4ac0-98b7-6d8af762b6f1.More details about the MAD and Master Address Points.Map service also available.

The Ontario Road Network (ORN) Composite product is a segmented derivative of the ORN Road Net Element (ORNELEM) data class. You can use it for mapping and general spatial analysis. Road segment information includes:addressingfull street namealternate street namespeed limitnumber of lanespavement statusroad classjurisdictionroute numberdirection of traffic flowshield type informationThe ORN is a provincewide geographic database of over 250,000 km of:municipal roadsprovincial highwaysresource and recreational roadsThe ORN is the authoritative source of roads data for the Government of Ontario. This product is derived from the  ORN Road Net Element  data class. It combines three types of geometry:road elementsferry connectionsvirtual roadsThis product also includes additional road feature layers including:blocked passagesunderpassestoll pointsstructuresAdditional DocumentationOntario Road Network (ORN) Composite - User Guide (Word)Data Capture Specifications for Road Net Elements - Guide to Best Practices for Acquisition (Word)GO-ITS 29 - Ontario Road Network StandardOntario Road Network - List of Partners (Word)StatusOn going: data is being continually updatedMaintenance and Update FrequencyMonthly: data is updated on a monthly basisContactOntario Ministry of Natural Resources - Geospatial Ontario, geospatial@ontario.ca

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 very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.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 Complex

Area 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!

This filtered version of the layer represents all IRWIN-tracked fires that originated in California or are are less than 100% contained.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 very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.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!

Our Recent Earthquakes - Live Feed Service updated with the new 'Feature Display Order' capability, now available when using the new Map Viewer. Allowing it to render features based on the Magnitude Order for Quake Events, and Intensity Order for Shakemap features. This brings attention to critical events and greatly improves Feature visibility!In addition to displaying earthquakes by magnitude, this service also provide earthquake impact details. Impact is measured by population as well as models for economic and fatality loss. For more details, see: PAGER Alerts.
Consumption Best Practices:

As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cache-able relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cache-able.Update Frequency: Events are updated as frequently as every 5 minutes and are available up to 30 days with the following exceptions:

Events with a Magnitude LESS than 4.5 are retained for 7 daysEvents with a Significance value, 'sig' field, of 600 or higher are retained for 90 days In addition to event points, ShakeMaps are also provided. These have been dissolved by Shake Intensity to reduce the Layer Complexity.The specific layers provided in this service have been Time Enabled and include: Events by Magnitude: The event’s seismic magnitude value.Contains PAGER Alert Level: USGS PAGER (Prompt Assessment of Global Earthquakes for Response) system provides an automated impact level assignment that estimates fatality and economic loss.Contains Significance Level: An event’s significance is determined by factors like magnitude, max MMI, ‘felt’ reports, and estimated impact.Shake Intensity: The Instrumental Intensity or Modified Mercalli Intensity (MMI) for available events.For field terms and technical details, see: ComCat DocumentationRevisionsJul 11, 2024: Updated event popup, setting 'Tsunami Warning' text to 'Alert Possible' when flag is present. Also included hyperlink to tsunami warning center.This map is provided for informational purposes and is not monitored 24/7 for accuracy and currency. Always refer to USGS source for official guidance.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!

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 very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.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 Complex

Area 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!

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 very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.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 Complex

Area 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!

This layer presents detectable thermal activity from VIIRS satellites for the last 7 days. VIIRS Thermal Hotspots and Fire Activity is a product of NASA’s Land, Atmosphere Near real-time Capability for EOS (LANCE) Earth Observation Data, part of NASA's Earth Science Data.Consumption Best Practices:

As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.Source: NASA LANCE - VNP14IMG_NRT active fire detection - WorldScale/Resolution: 375-meterUpdate Frequency: Hourly using the aggregated live feed methodologyArea Covered: WorldWhat can I do with this layer?This layer represents the most frequently updated and most detailed global remotely sensed wildfire information. Detection attributes include time, location, and intensity. It can be used to track the location of fires from the recent past, a few hours up to seven days behind real time. This layer also shows the location of wildfire over the past 7 days as a time-enabled service so that the progress of fires over that timeframe can be reproduced as an animation.The VIIRS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.Fire points in this service are generally available within 3 1/4 hours after detection by a VIIRS device. LANCE estimates availability at around 3 hours after detection, and esri livefeeds updates this feature layer every 15 minutes from LANCE.Even though these data display as point features, each point in fact represents a pixel that is >= 375 m high and wide. A point feature means somewhere in this pixel at least one "hot" spot was detected which may be a fire.VIIRS is a scanning radiometer device aboard the Suomi NPP, NOAA-20, and NOAA-21 satellites that collects imagery and radiometric measurements of the land, atmosphere, cryosphere, and oceans in several visible and infrared bands. The VIIRS Thermal Hotspots and Fire Activity layer is a livefeed from a subset of the overall VIIRS imagery, in particular from NASA's VNP14IMG_NRT active fire detection product. The downloads are automatically downloaded from LANCE, NASA's near real time data and imagery site, every 15 minutes.The 375-m data complements the 1-km Moderate Resolution Imaging Spectroradiometer (MODIS) Thermal Hotspots and Fire Activity layer; they both show good agreement in hotspot detection but the improved spatial resolution of the 375 m data provides a greater response over fires of relatively small areas and provides improved mapping of large fire perimeters.Attribute informationLatitude and Longitude: The center point location of the 375 m (approximately) pixel flagged as containing one or more fires/hotspots.Satellite: Whether the detection was picked up by the Suomi NPP satellite (N) or NOAA-20 satellite (1) or NOAA-21 satellite (2). For best results, use the virtual field WhichSatellite, redefined by an arcade expression, that gives the complete satellite name.Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel. This value is based on a collection of intermediate algorithm quantities used in the detection process. It is intended to help users gauge the quality of individual hotspot/fire pixels. Confidence values are set to low, nominal and high. Low confidence daytime fire pixels are typically associated with areas of sun glint and lower relative temperature anomaly (<15K) in the mid-infrared channel I4. Nominal confidence pixels are those free of potential sun glint contamination during the day and marked by strong (>15K) temperature anomaly in either day or nighttime data. High confidence fire pixels are associated with day or nighttime saturated pixels.Please note: Low confidence nighttime pixels occur only over the geographic area extending from 11 deg E to 110 deg W and 7 deg N to 55 deg S. This area describes the region of influence of the South Atlantic Magnetic Anomaly which can cause spurious brightness temperatures in the mid-infrared channel I4 leading to potential false positive alarms. These have been removed from the NRT data distributed by FIRMS.FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).DayNight: D = Daytime fire, N = Nighttime fireHours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.Additional information can be found on the NASA FIRMS site FAQ.Note about near real time data:Near real time data is not checked thoroughly before it's posted on LANCE or downloaded and posted to the Living Atlas. NASA's goal is to get vital fire information to its customers within three hours of observation time. However, the data is screened by a confidence algorithm which seeks to help users gauge the quality of individual hotspot/fire points. Low confidence daytime fire pixels are typically associated with areas of sun glint and lower relative temperature anomaly (<15K) in the mid-infrared channel I4. Medium confidence pixels are those free of potential sun glint contamination during the day and marked by strong (>15K) temperature anomaly in either day or nighttime data. High confidence fire pixels are associated with day or nighttime saturated pixels.RevisionsMarch 7, 2024: Updated to include source data from NOAA-21 Satellite.September 15, 2022: Updated to include 'Hours_Old' field. Time series has been disabled by default, but still available.July 5, 2022: Terms of Use updated to Esri Master License Agreement, no longer stating that a subscription is required!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!

Purpose: Displays the location of Traffic control markings. Pavement Markings Inventory is a configuration of Collector for ArcGIS that can be used by Engineering and/or Public Works field staff to inventory pavement markings that delineate vehicular paths of travel and convey directional or lane usage requirements.Intended Use: This data was collected by DTS video survey under the direction of Engineering Department. Users of this data should use the data carefully and try to verify the information..Department: Engineering Department - Transportation DivisionData Source: referenced feature service on Enterprise portalHow was the Data Manipulated: Originally data was collected by DTS video survey .In 2018 DTS did another video survey and it's unclear if the data was updated from the 2018 survey. How the Data is Modified: The best practice is for thee Engineering / Transportation group to take ownership of this layer and update as needed. The GIS team is not updating this layer. Update Frequency: As-Needed by Engineering,/ Transportation group

This filtered version of the layer represents all IRWIN-tracked fires that originated in California or are are less than 100% contained.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 very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.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!

This live webmap is a subset of Global Recent Earthquakes feature layer.This Web Map displays earthquakes by magnitude, this service also provide earthquake impact details. Impact is measured by population as well as models for economic and fatality loss. For more details, see: PAGER Alerts.Consumption Best Practices:As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cache-able relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest 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 efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cache-able.Update Frequency: Events are updated as frequently as every 5 minutes and are available up to 30 days with the following exceptions:Events with a Magnitude LESS than 4.5 are retained for 7 daysEvents with a Significance value, 'sig' field, of 600 or higher are retained for 90 daysIn addition to event points, ShakeMaps are also provided. These have been dissolved by Shake Intensity to reduce the Layer Complexity.The specific layers provided in this service have been Time Enabled and include:Events by Magnitude: The event’s seismic magnitude value.Contains PAGER Alert Level: USGS PAGER (Prompt Assessment of Global Earthquakes for Response) system provides an automated impact level assignment that estimates fatality and economic loss.Contains Significance Level: An event’s significance is determined by factors like magnitude, max MMI, ‘felt’ reports, and estimated impact.Shake Intensity: The Instrumental Intensity or Modified Mercalli Intensity (MMI) for available events.For field terms and technical details, see: ComCat DocumentationAlternate SymbologiesVisit the Classic USGS Feature Layer item for a Rainbow view of Shakemap features.RevisionsFeb 13, 2024: Updated feed logic to remove Superseded eventsThis map is provided for informational purposes and is not monitored 24/7 for accuracy and currency. Always refer to USGS source for official guidance.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!

Esri's Water Resources GIS Platform offers a comprehensive suite of tools and resources designed to modernize water resource management. It emphasizes geospatial solutions for monitoring, analyzing, and modeling water systems, helping decision-makers tackle challenges like drought resilience, flood mitigation, and environmental protection. By leveraging the capabilities of ArcGIS, users can transform raw water data into actionable insights, ensuring more efficient and effective water resource management.A central feature of the platform is Arc Hydro, a specialized data model and toolkit developed for GIS-based water resource analysis. This toolset allows users to integrate, analyze, and visualize water datasets for applications ranging from live stream gauge monitoring to pollution control. Additionally, the platform connects users to the ArcGIS Living Atlas of the World, which offers extensive water-related datasets such as rivers, wetlands, and soils, supporting in-depth analyses of hydrologic conditions. The Hydro Community further enhances collaboration, enabling stakeholders to share expertise, discuss challenges, and build innovative solutions together.Esri’s platform also provides training opportunities and professional services to empower users with technical knowledge and skills. Through instructor-led courses, documentation, and best practices, users gain expertise in using ArcGIS and Arc Hydro for their specific water management needs. The combination of tools, datasets, and community engagement makes Esri's water resources platform a powerful asset for advancing sustainable water management initiatives across public and private sectors.

This feature layer indicates the canyon locations where the 2011 Texas Tanglewood Fire first entered the south Palisades Community. The 2011 Tanglewood fire was assessed through a joint effort by the National Institute of Standards and Technology (NIST), U.S. Forest Service (USFS), and Texas A&M Forest Service (TFS)was conducted as part of the NIST/USFS Wildland-Urban Interface (WUI) Fire Exposure Data Collection and Modeling Project.

The Tanglewood Fire started February 27, 2011, about 10 mi south of Amarillo in the Timbercreek Canyon community about 2 mi west of Lake Tanglewood. The Tanglewood Fire was part of a larger complex of fires that included the Willow Creek Fire and Country Club Fire, all of which began February 27, 2011, on the outskirts of Amarillo. For this assessment, limited resources permitted study of only one incident, for which the Tanglewood Fire was chosen. This study began with detailed collection of postfire information by NIST and TFS according to the NIST/USFS WUI Assessment Methodology (Maranghides et al. 2011). Training of TFS staff in methods of field data collection occurred before the incident, and mobile data collection equipment for this effort was pre-staged in Texas. NIST and USFS began gathering electronic data for the incident within 6 hours of the fire’s onset. Within 48 hours, NIST and TFS integrated a field data collection team into the Incident Command System (ICS) to conduct the post-fire assessment. The deployment also worked in conjunction with state and local damage assessment efforts.

The objective of the WUI Fire Exposure Data Collection and Modeling Project is to develop the measurement science needed to mitigate the effects of WUI fires by providing technical guidance on building components, landscaping elements, and community designs that resist the ignition and limit the spread of such fires. The project’s overall vision is to help reduce structure and community vulnerability to WUI fires through development of fire-resistant design and materials, based on reliable post-fire data and promoted through incorporation into codes, standards, and best practices. Post-fire analysis of WUI fires such as that conducted for the Tanglewood Fire provides the knowledge to focus experiments and modeling on critical vulnerabilities of structures, landscaping, and materials. Standard data collection methodologies will also help generate reliable post-fire data. Two reports provide additional information on the overall Tanglewood Fire postfire assessment. A report entitled 2011 Wildland Urban Interface Amarillo Fires Report #2—Assessment of Fire Behavior and WUI Measurement Science (Maranghides and McNamara, 2016) provides the most detailed information on the Tanglewood Fire assessment, whereas Initial Reconnaissance of the 2011 Wildland-Urban Interface Fires in Amarillo, Texas (Maranghides et al. 2011) provides an overview of deployment procedures and initial assessment results. Finally, the U.S. Department of Agriculture Forest Service Research Data Archive contains the full set of published data.

This webmap features the USGS GAP application of the vegetation cartography design based on NVCS mapping being done at the Alliance level by the California Native Plant Society (CNPS), the California Dept of Fish and Game (CDFG), and the US National Park Service, combined with Ecological Systems Level mapping being done by USGS GAP, Landfire and Natureserve. Although the latter are using 3 different approaches to mapping, this project adopted a common cartography and a common master crossover in order to allow them to be used intercheangably as complements to the detailed NVCS Alliance & Macrogroup Mapping being done in Calif by the California Native Plant Society (CNPS) and Calif Dept of Fish & Wildlife (CDFW). A primary goal of this project was to develop ecological layers to use as overlays on top of high-resolution imagery, in order to help interpret and better understand the natural landscape. You can see the source national GAP rasters by clicking on either of the "USGS GAP Landcover Source RASTER" layers at the bottom of the contents list.Using polygons has several advantages: Polygons are how most conservation plans and land decisions/managment are done so polygon-based outputs are more directly useable in management and planning. Unlike rasters, Polygons permit webmaps with clickable links to provide additional information about that ecological community. At the analysis level, polygons allow vegetation/ecological systems depicted to be enriched with additional ecological attributes for each polygon from multiple overlay sources be they raster or vector. In this map, the "Gap Mac base-mid scale" layers are enriched with links to USGS/USNVC macrogroup summary reports, and the "Gap Eco base scale" layers are enriched with links to the Naturserve Ecological Systems summary reports.Comparsion with finer scale ground ecological mapping is provided by the "Ecol Overlay" layers of Alliance and Macrogroup Mapping from CNPS/CDFW. The CNPS Vegetation Program has worked for over 15 years to provide standards and tools for identifying and representing vegetation, as an important feature of California's natural heritage and biodiversity. Many knowledgeable ecologists and botanists support the program as volunteers and paid staff. Through grants, contracts, and grass-roots efforts, CNPS collects field data and compiles information into reports, manuals, and maps on California's vegetation, ecology and rare plants in order to better protect and manage them. We provide these services to governmental, non-governmental and other organizations, and we collaborate on vegetation resource assessment projects around the state. CNPS is also the publisher of the authoritative Manual of California Vegetation, you can purchase a copy HERE. To support the work of the CNPS, please JOIN NOW and become a member!The CDFG Vegetation Classification and Mapping Program develops and maintains California's expression of the National Vegetation Classification System. We implement its use through assessment and mapping projects in high-priority conservation and management areas, through training programs, and through working continuously on best management practices for field assessment, classification of vegetation data, and fine-scale vegetation mapping.HOW THE OVERLAY LAYERS WERE CREATED:Nserve and GapLC Sources: Early shortcomings in the NVC standard led to Natureserve's development of a mid-scale mapping-friendly "Ecological Systems" standard roughly corresponding to the "Group" level of the NVC, which facilitated NVC-based mapping of entire continents. Current scientific work is leading to the incorporation of Ecological Systems into the NVC as group and macrogroup concepts are revised. Natureserve and Gap Ecological Systems layers differ slightly even though both were created from 30m landsat data and both follow the NVC-related Ecological Systems Classification curated by Natureserve. In either case, the vector overlay was created by first enforcing a .3ha minimum mapping unit, that required deleting any classes consisting of fewer than 4 contiguous landsat cells either side-side or cornerwise. This got around the statistical problem of numerous single-cell classes with types that seemed improbable given their matrix, and would have been inaccurate to use as an n=1 sample compared to the weak but useable n=4 sample. A primary goal in this elimination was to best preserve riparian and road features that might only be one pixel wide, hence the use of cornerwise contiguous groupings. Eliminated cell groups were absorbed into whatever neighboring class they shared the longest boundary with. The remaining raster groups were vectorized with light simplification to smooth out the stairstep patterns of raster data and hopefully improve the fidelity of the boundaries with the landscape. The resultant vectors show a range of fidelity with the landscape, where there is less apparent fidelity it must be remembered that ecosystems are normally classified with a mixture of visible and non-visible characteristics including soil, elevation and slope. Boundaries can be assigned based on the difference between 10% shrub cover and 20% shrub cover. Often large landscape areas would create "godzilla" polygons of more than 50,000 vertices, which can affect performance. These were eliminated using SIMPLIFY POLYGONS to reduce vertex spacing from 30m down to 50-60m where possible. Where not possible DICE was used, which bisects all large polygons with arbitrary internal divisions until no polygon has more than 50,000 vertices. To create midscale layers, ecological systems were dissolved into the macrogroups that they belonged to and resymbolized on macrogroup. This was another frequent source for godzillas as larger landscape units were delineate, so simplify and dice were then run again. Where the base ecol system tiles could only be served up by individual partition tile, macrogroups typically exhibited a 10-1 or 20-1 reduction in feature count allowing them to be assembled into single integrated map services by region, ie NW, SW. CNPS / CDFW / National Park Service Sources: (see also base service definition page) Unlike the Landsat-based raster modelling of the Natureserve and Gap national ecological systems, the CNPS/CDFW/NPS data date back to the origin of the National Vegetation Classification effort to map the US national parks in the mid 1990's.
These mapping efforts are a hybrid of photo-interpretation, satellite and corollary data to create draft ecological land units, which are then sampled by field crews and traditional vegetation plot surveys to quantify and analyze vegetation composition and distribution into the final vector boundaries of the formal NVC classes identified and classified. As such these are much more accurate maps, but the tradeoff is they are only done on one field project area at a time so there is not yet a national or even statewide coverage of these detailed maps.
However, with almost 2/3d's of California already mapped, that time is approaching. The challenge in creating standard map layers for this wide diversity of projects over the 2 decades since NVC began is the extensive evolution in the NVC standard itself as well as evolution in the field techniques and tools. To create a consistent set of map layers, a master crosswalk table was built using every different classification known at the time each map was created and then crosswalking each as best as could be done into a master list of the currently-accepted classifications. This field is called the "NVC_NAME" in each of these layers, and it contains a mixture of scientific names and common names at many levels of the classification from association to division, whatever the ecologists were able to determine at the time. For further precision, this field is split out into scientific name equivalents and common name equivalents.MAP LAYER NAMING: The data sublayers in this webmap are all based on the US National Vegetation Classification, a partnership of the USGS GAP program, US Forest Service, Ecological Society of America and Natureserve, with adoption and support from many federal & state agencies and nonprofit conservation groups. The USNVC grew out of the US National Park Service Vegetation Mapping Program, a mid-1990's effort led by The Nature Conservancy, Esri and the University of California. The classification standard is now an international standard, with associated ecological mapping occurring around the world. NVC is a hierarchical taxonomy of 8 levels, from top down: Class, Subclass, Formation, Division, Macrogroup, Group, Alliance, Association. The layers in this webmap represent 4 distinct programs: 1. The California Native Plant Society/Calif Dept of Fish & Wildlife Vegetation Classification and Mapping Program (Full Description of these layers is at the CNPS MS10 Service Registration Page and Cnps MS10B Service Registration Page . 2. USGS Gap Protected Areas Database, full description at the PADUS registration page . 3. USGS Gap Landcover, full description below 4. Natureserve Ecological Systems, full description belowLAYER NAMING: All Layer names follow this pattern: Source - Program - Level - Scale - RegionSource - Program = who created the data: Nserve = Natureserve, GapLC = USGS Gap Program Landcover Data PADUS = USGS Gap Protected Areas of the USA program Cnps/Cdfw = California Native Plant Society/Calif Dept of Fish & Wildlife, often followed by the project name such as: SFhill = Sierra Foothills, Marin Open Space, MMWD = Marin Municipal Water District etc. National Parks are included and may be named by their standard 4-letter code ie YOSE = Yosemite, PORE = Point Reyes.Level: The level in the NVC Hierarchy which this layer is based on: Base = Alliances and Associations Mac =