Facebook
TwitterDescription: This Notebook will prompt the user for a basemap they would like to replace, and a basemap to replace it with. Then the notebook will loop through all of the web maps the user has access to, it will look for the selected basemap, and replace it with the selected replacement basemap.Created on: 7/1/24Purpose: The purpose of this notebook is to streamline the workflow of updating the basemaps that are used in web maps. Many users have selected our local imagery as the basemap in their web maps, and as that imagery ages, it is important to update it with the updated imagery. This will allow the user to define the basemap they want to replace, a basemap to replace it with, then loop through all of the web maps the user has access to, and update the web maps with the selected replacement basemap.Parameters:Title of the basemap you want to replace.ItemID of the basemap you want to replace it with.Authored By: Joe GuziPrevious Production Date: 7/1/24Production Date: 7/18/24Note: The previous version of this notebook, was written specifically to replace Esri's Raster basemaps that were being deprecated. It can be downloaded here: https://www.arcgis.com/home/item.html?id=90cc2d7419f947d3ae55b44fd3090b24
Facebook
TwitterMap of Environmental Resource Permit boundaries or locations for the Florida Dept. Of Environmental Protection (FDEP) and the five Florida water management districts:Northwest Florida Water Management District (NWFWMD)South Florida Water Management District (SFWMD)Southwest Florida Water Management District (SWFWMD)St. Johns River Water Management District (SJRWMD)Suwannee River Water Management District (SRWMD) Clicking on a permit will present a pop-up with basic information for that permit. Additional information, including access to all permit-related documents, can be obtained by selecting the "More info" link in the pop-up.Boundaries for SFWMD, SWFWMD, and SJRWMD are independently served by each agency via web services. Point locations for FDEP are served by FDEP via a web service. Boundaries or locations for SRWMD and NWFWMD are served by SJRWMD web services.This web map was developed for the Florida Shared Services Project. The goals of the project are to: Develop a collaborative framework that the water management districts can use for joint application development effortsEstablish a common understanding of the technology associated with using Esri’s ArcGIS Online productEstablish a governance model for shared application developmentUpdated March 2014 with FDEP data.Updated May 15, 2014 with new SWFWMD service url.Updated August 15, 2014 with new SFWMD service url.Updated September 25, 2014 to repair transparency settings that had changed to 0 instead of 25% - perhaps after service updates?Updated January 7, 2015 to address problems with pop-ups not appearing or not being correct for both SFWMD and SWFWMD.Updated May 7, 2015 with new NWFWMD service url.Updated May 14, 2015 with new SRWMD service url.Updated July 25, 2016 through ago-assistant.esri.com, using JSON editor. Corrected item IDs for NWFWMD.Updated August 1, 2016 with new SWFWMD service url. Created brand new web map.Updated August 17, 2016 with replacement SFWMD service url. Created brand new web map.Updated September 12, 2018 with SSL site references and REST service connections for SWFWMD, SJRWMD, SRWMD and NWFWMD.Update February 26, 2019 through https://ago-assistant.esri.com/: new service urls for SJRWMD, SRWMD and NWFWMD.Update August 29, 2019 to include PERMITTING_PROGRAM = BEACH AND COASTAL SYSTEMS.Updated spring 2024 to use new SFWMD service urls, with native projected coordinate system.Updated August 8, 2024 for overwrite of SFWMD service url, to again use Web Mercator.
Facebook
TwitterThis map is intended to provide general awareness of severe weather. It is not intended to replace authoritative government websites but rather to provide situational awareness. This map can be used as a template for agencies wanting to add their own custom data. This map contains layers from Esri's Living Atlas of the World including Storm Reports, Short-Term Weather Warnings, Weather Watches and Warnings, and Snowfall Forecast. Click on the title of the layers below for more information about each layer and it's source as well as update frequency. Weather Radar Data courtesy of Baron Weather, for more info click here.This map is provided by the Esri Disaster Response Program. For other severe weather related content and data, please visit the DRP Hub Severe Weather Page.
Facebook
TwitterNOTE: Due to the size of this file, it can only be downloaded as a File Geodatabase.This statewide shapefile contains the freshwater surface water classifications for all named streams in North Carolina. This data was first uploaded on March 6, 2015 and originally pulled from BIMS in November 2014. To learn more about what classifications are, see the Classifications and Standards/Rule Review Branch website. Download this dataset from the DEQ Open Data PageThe Tile Layer for this Feature Layer is DWR Surface Water Classifications.Attributes:BIMS_INDEX: Index number BIMS_Names: Stream Name BIMS_Descr: Description of stream segment (from - to) BIMS_Class: Surface Water Classification BIMS_Date: Date the classification was given to that segment ClassURL: Link to the Classifications website that defines each classification Name: River Basin Contacts:Data Contact: Chris VentaloroLayer/Service Contact: Melanie Williams Updates: 05/24/2016: Changed the URL for the classifications page; fixed the Clear Creek (FBR) line segment; re-uploaded this as a new feature service with the ability to overwrite. 6/1/2017: Geometry for Index Numbers 18-(71) of the Cape Fear River and 18-88-1 of Walden Creek were missing from the feature service. The geometry was corrected with the existing file on local servers and the online feature service was overwritten. This feature layer can be found in the NC Surface Water Classification map application.
Facebook
TwitterThe Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service includes perimeters for wildland fire incidents that meet the following criteria:
Categorized in the IRWIN (Integrated Reporting of Wildland Fire Information) integration service as a valid Wildfire (WF) or Prescribed Fire (RX)
Has not been declared contained, controlled, nor out
Has not had fire report records completed (certified)
Is not "quarantined" in IRWIN due to potential conflicts with other records
Attribution of the source polygon is set to a Feature Access of Public, a Feature Status of Approved, and an Is Visible setting of Yes
Perimeters are not available for every incident. For a complete set of features that meet the same IRWIN criteria, see the Current Wildland Fire Locations service.
"Fall-off" rules are used to ensure that stale records are not retained. Records are removed from this service under the following conditions:
If the fire size is less than 10 acres (Size Class A or B) and fire information has not been updated in more than 3 days
Fire size is between 10 and 100 acres (Size Class C) and fire information hasn't been updated in more than 8 days
Fire size is larger than 100 acres (Size Class D-L) but fire information hasn't been updated in more than 14 days.
Fires from previous calendar years are excluded.Fire size used in the fall off rules is from the IRWIN Daily Acres field.
Fires that are no longer in the Current Wildland Fire Perimeter service will be displayed in the Wildland Fire Perimeters to Date and the Full History services.
Criteria were determined by an NWCG Geospatial Subcommittee task group.
Data are refreshed every 5 minutes. Changes in the perimeter source may take up to 15 minutes to display.
Perimeters are pulled from multiple sources with rules in place to ensure the most current or most authoritative shape is used.
Fall-off rules are enforced hourly.Warning: Please refrain from repeatedly querying the service using a relative date range. This includes using the “(not) in the last” operators in a Web Map filter and any reference to CURRENT_TIMESTAMP. This type of query puts undue load on the service and may render it temporarily unavailable.
Attributes and their definitions can be found below. More detail about the NWCG Wildland Fire Event Polygon standard can be found here.
Attributes:
Incident Name (Polygon)
The Incident Name from the source polygon.
Feature Category
Type of wildland fire perimeter set for the source polygon.
Map Method
Controlled vocabulary to define how the source polygon was derived. Map Method may help define data quality.
GIS Acres
User-calculated acreage on the source polygon.
Polygon Create Date
System field. Time stamp for the source polygon feature creation.
Polygon Modified Date
System field. Time stamp for the most recent edit to the source polygon feature.
Polygon Collection Date Time
Date time for the source polygon feature collection.
Acres Auto Calculated
Automated calculation of the source polygon acreage.
Polygon Source
Data source of the perimeter geometry.{Year} NIFS: Annual National Incident Feature ServiceFFP: Final Fire Perimeter Service (Certified Perimeters)
ABCD Misc
A FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.
ADS Permission State
Indicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.
IRWIN Archived On
A date set by IRWIN that indicates when an incident's data has met the rules defined for the record to become part of the historical fire records rather than an operational incident record. The value will be set the current date/time if any of the following criteria are met: 1. ContainmentDataTime or ControlDateTime or FireOutDateTime or ModifiedOnDateTime > 12 months from the current DateTime2. FinalFireReportDate is not null and ADSPermissionState is 'certified'.
Calculated Acres
A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire. More specifically, the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands. The minimum size must be 0.1.
Containment Date Time
The date and time a wildfire was declared contained.
Control Date Time
The date and time a wildfire was declared under control.
Created By System
ArcGIS Server Username of system that created the IRWIN Incident record.
IRWIN Created On Date Time
Date/time that the IRWIN Incident record was created.
IRWIN Daily Acres
A measure of acres reported for a fire. More specifically, the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands. The minimum size must be 0.1.
Discovery Acres
An estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.
Dispatch Center ID
A unique identifier for a dispatch center responsible for supporting the incident.
Final Fire Report Approved By Title
The title of the person that approved the final fire report for the incident.
Final Fire Report Approved By Unit
NWCG Unit ID associated with the individual who approved the final report for the incident.
Final Fire Report Approved Date
The date that the final fire report was approved for the incident.
Fire Behavior General
A general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography.
Fire Behavior General 1
A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography).
Fire Behavior General 2
A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography).
Fire Behavior General 3
A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography).
Fire Cause
Broad classification of the reason the fire occurred identified as human, natural or unknown.
Fire Cause General
Agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes.
Fire Cause Specific
A further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition.
Fire Code
A code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident.
Fire Department ID
The U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.
Fire Discovery Date Time
The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.
Fire Mgmt Complexity
The highest management level utilized to manage a wildland fire event.
Fire Out Date Time
The date and time when a fire is declared out.
Fire Strategy Confine Percent
Indicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.
Fire Strategy Full Supp Percent
Indicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.
Fire Strategy Monitor Percent
Indicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.
Fire Strategy Point Zone Percent
Indicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.
FS Job Code
A code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.
FS Override Code
A code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.
GACC
A code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for
Facebook
TwitterLandforms are large recognizable features such as mountains, hills and plains; they are an important determinant of ecological character, habitat definition and terrain analysis. Landforms are important to the distribution of life in natural systems and are the basis for opportunities in built systems, and therefore landforms play a useful role in all natural science fields of study and planning disciplines. Dataset SummaryPhenomenon Mapped: LandformsGeographic Extent: GlobalProjection: WGS 1984Mosaic Projection: Web Mercator Auxiliary SphereUnits: MetersCell Size: 231.91560581932 metersPixel Depth: 8-bit unsigned integerAnalysis: Restricted single source analysis. Maximum size of analysis is 30,000 x 30,000 pixels.Source: EsriPublication Date: May 2016ArcGIS Server URL: https://landscape7.arcgis.com/arcgis/ In February 2017, Esri updated the World Landforms - Improved Hammond Method service with two display functions: Ecological Land Units landform classes and Ecological Facets landform classes. This layer represents Ecological Facets landform classes. You can view the Ecological Land Units landform classes by choosing Image Display, and changing the Renderer. This layer was produced using the Improved Hammond Landform Classification Algorithm produced by Esri in 2016. This algorithm published and described by Karagulle et al. 2017: Modeling global Hammond landform regions from 250-m elevation data in Transactions in GIS. The algorithm, which is based on the most recent work in this area by Morgan, J. & Lesh, A. 2005: Developing Landform Maps Using Esri’s Model Builder., Esri converted Morgan’s model into a Python script and revised it to work on global 250-meter resolution GMTED2010 elevation data. Hammond’s landform classification characterizes regions rather than identifying individual features, thus, this layer contains sixteen classes of landforms:Nearly flat plains Smooth plains with some local relief Irregular plains with moderate relief Irregular plains with low hills Scattered moderate hills Scattered high hills Scattered low mountains Scattered high mountains Moderate hills High hills Tablelands with moderate relief Tablelands with considerable relief Tablelands with high relief Tablelands with very high relief Low mountains High mountains To produce these classes, Esri staff first projected the 250-meter resolution GMTED elevation data to the World Equidistant Cylindrical coordinate system. Each cell in this dataset was assigned three characteristics: slope based on 3-km neighborhood, relief based on 6 km neighborhood, and profile based on 6-km neighborhood. The last step was to overlay the combination of these three characteristics with areas that are exclusively plains. Slope is the percentage of the 3-km neighborhood occupied by gentle slope. Hammond specified 8% as the threshold for gentle slope. Slope is used to define how flat or steep the terrain is. Slope was classified into one of four classes: Percent of neighborhood over 8% of slopeSlope Classes0 - 20%40021% -50%30051% - 80%200>81% 100Local Relief is the difference between the maximum and minimum elevation within in the 6-km neighborhood. Local relief is used to define terrain how rugged or the complexity of the terrain"s texture. Relief was assigned one of six classes:Change in elevationRelief Class ID0 – 30 meters1031 meter – 90 meters2091 meter – 150 meters30151 meter – 300 meters40301 meter – 900 meters50>900 meters60The combination of slope and relief begin to define terrain as mountains, hills and plains. However, the difference between mountains or hills and tablelands cannot be distinguished using only these parameters. Profile is used to determine tableland areas. Profile identifies neighborhoods with upland and lowland areas, and calculates the percent area of gently sloping terrain within those upland and lowland areas. A 6-km circular neighborhood was used to calculate the profile parameter. Upland/lowland is determined by the difference between average local relief and elevation. In the 6-km neighborhood window, if the difference between maximum elevation and cell’s elevation is smaller than half of the local relief it’s an upland. If the difference between maximum elevation and cell’s elevation is larger than half of the local relief it’s a lowland. Profile was assigned one of five classes:Percent of neighborhood over 8% slope in upland or lowland areasProfile ClassLess than 50% gentle slope is in upland or lowland0More than 75% of gentle slope is in lowland150%-75% of gentle slope is in lowland250-75% of gentle slope is in upland3More than 75% of gentle slope is in upland4Early reviewers of the resulting classes noted one confusing outcome, which was that areas were classified as "plains with low mountains", or "plains with hills" were often mostly plains, and the hills or mountains were part of an adjacent set of exclusively identified hills or mountains. To address this areas that are exclusively plains were produced, and used to override these confusing areas. The hills and mountains within those areas were converted to their respective landform class. The combination of slope, relief and profile merged with the areas of plains, can be better understood using the following diagram, which uses the colors in this layer to show which classes are present and what parameter values produced them: What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop. Restricted single source analysis means this layer has size constraints for analysis and it is not recommended for use with other layers in multisource analysis. This layer is part of a larger collection of landscape layers that you can use to perform a wide variety of mapping and analysis tasks. The Living Atlas of the World provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Geonet is a good resource for learning more about landscape layers and the Living Atlas of the World. To get started see the Living Atlas Discussion Group. The Esri Insider Blog provides an introduction to the Ecophysiographic Mapping project.
Facebook
TwitterThis is a publicly available map image service with limited GIS attributes. A downloadable version of this data is now available through the MDOT GIS Open Data Portal: Download MDOT SHA Right-of-Way Polygons (Open Data Portal) The following related versions of this data are available here:MDOT SHA Right-of-Way (Secured)Line dataFull attribute tableAccessible to only MDOT employees and contractors upon requestMDOT SHA Right-of-Way (Map Image Service)Read-only map serviceLine dataLimited attributes (quality level)Accessible to publicMDOT SHA Right-of-Way data is a composite layer of PSD field-collected survey sources, PSD in-house computations, traced PSD hardcopy materials, and historical Maryland Department of Planning (MDP) parcel boundaries.This data product was intended to replace MDOT SHA Planning Level Right-of-Way (Tax Map Legacy), which is an increasingly obsolete legacy product for MDOT SHA Right-of-Way information that in some areas remains the most comprehensive. For continuity, many MDP parcel boundaries found in MDOT SHA Planning Level Right-of-Way (Tax Map Legacy) have been incorporated into MDOT SHA Right-of-Way data with an "Estimated" quality level. Please see below for a description of the primary attribute.-----------------------------------------------------The polygons in this layer are divided into 318 arbitrary grid zones across the State of Maryland. Updates to the parent ROW boundary line data set [MDOT SHA Right-of-Way (Secured)] are made by grid and reflected in this polygon layer.For more information or to report errors in this data, please contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov
Facebook
TwitterArcGIS Online Map of the USGS 3D Hydrography Program (3DHP) ArcGIS REST service (3DHP_all) from The National Map is the first of several data services that will be delivered by the 3D Hydrography Program. The 3DHP_all service comprises a national network of flowlines, hydrolocations, and water bodies, and will include catchments, drainage areas, and flow network derivatives as they are populated in the future. The 3DHP_all service will provide access to a 3D-enabled geospatial hydrography vector dataset built from 3DHP data and intended to provide the most comprehensive but general rendering of 3DHP data. 3DHP data is derived from elevation-derived hydrography (EDH) Elevation-Derived Hydrography Specifications where available. Where EDH has not been collected, 3DHP data will be supplemented by data from the National Hydrography Dataset (NHD) National Hydrography Dataset. As further EDH data is collected, the EDH data will replace the NHD data in that data collection area. 3DHP data ingested from EDH sources will include catchments, drainage areas derived from catchments, and flowline network attribute derivatives.
Facebook
TwitterSolar power is a clean source of energy. To replace conventional power sources, solar power generation must be scaled. This is being done by creating large solar photovoltaic parks. Some of large parks even span up to thousands of acres and are equipped with millions of solar panels. This information can serve government, policy makers, international organizations, companies, researchers in various ways.Traditional ways of obtaining information on solar photo voltaic parks, such as surveys and on-site visits, are time consuming and error prone. Deep learning models are highly capable of learning complex semantics and can produce superior results. Use this deep learning model to automate the task of creating classified maps indicating concentration of solar parks, reducing time and effort required significantly.Using the modelFollow the guide to use the model. Before using this model, ensure that the supported deep learning libraries are installed. For more details, check Deep Learning Libraries Installer for ArcGIS.Fine-tuning the modelThis model can be fine-tuned using the Train Deep Learning Model tool. Follow the guide to fine-tune this model.InputSentinel-2 L2A imagery (bottom of atmosphere) having 12 bands and 10 meter resolution in form of a raster product, mosaic dataset, or image service. OutputClassified raster denoting solar photovoltaic parks.Applicable geographiesThe model is expected to work well globaly.Model architectureThis model uses the UNet model architecture implemented in ArcGIS API for Python.Accuracy metricsThis model has an overall accuracy of 99.0 %. Solar photovoltaic park class has a precision of 0.966, recall of 0.967 and F1 score of 0.967.Training dataThis model has been trained on an Esri proprietary solar photovoltaic park classification dataset.Limitations • False positives are observed near costal areas, mountains and cloudy regions.Sample resultsHere are a few results from the model. To view more, see this web map.
Facebook
TwitterThis feature layer provides digital tax parcels for the Organized Towns of the State of Maine. Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. "Maine Parcels Organized Towns Feature" and "Maine Parcels Organized Towns ADB" are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, which affects the currency of Maine GeoLibrary parcels data. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions. In Unorganized Territories (defined as those regions of the state without a local government that assesses real property and collects property tax), the Maine Revenue Service is the authoritative source for parcel data. "Maine Parcels Unorganized Territory Feature" is the authoritative GIS data layer for the Unorganized Territories. However, it must always be used with auxiliary data obtained from the online resources of Maine Revenue Services (https://www.maine.gov/revenue/taxes/property-tax) to compile up-to-date parcel ownership information. Property maps are a fundamental base for many municipal activities. Although GIS parcel data cannot replace detailed ground surveys, the data can assist municipal officials with functions such as accurate property tax assessment, planning and zoning. Towns can link maps to an assessor's database and display local information, while town officials can show taxpayers how proposed development or changes in municipal services and regulations may affect the community. In many towns, parcel data also helps to provide public notices, plan bus routes, and carry out other municipal services.
This dataset contains municipality-submitted parcel data along with previously developed parcel data acquired through the Municipal Grants Project supported by the Maine Library of Geographic Information (Maine GeoLibrary). Grant recipient parcel data submissions were guided by standards presented to the Maine GeoLibrary Board on May 21, 2005, which are outlined in the "Standards for Digital Parcel Files" document available on the Maine GeoLibrary publications page (https://www.maine.gov/geolib/policies/standards.html). This dataset also contains municipal parcel data acquired through other sources; the data sources are identified (where available) by the field “FMSCORG”. Note: Join this feature layer with the "Maine Parcels Organized Towns ADB" table (https://maine.hub.arcgis.com/maps/maine::maine-parcels-organized-towns-feature/about?layer=1) for available ownership information. A date field, “FMUPDAT”, is attributed with the most recent update date for each individual parcel if available. The "FMUPDAT" field will not match the "Updated" value shown for the layer. "FMUPDAT" corresponds with the date of update for the individual data, while "Updated" corresponds with the date of update for the ArcGIS Online layer as a whole. Many parcels have not been updated in several years; use the "FMUPDAT" field to verify currency.
Facebook
TwitterCoral reefs are one of the most diverse and ecologically important areas of the world. However, many reefs, are threatened by ocean temperatures that are increasingly becoming warmer than the coral animals' natural tolerance. According to NOAA, when water is too warm, corals will expel the algae (zooxanthellae) living in their tissues causing the coral to turn completely white. This is called coral bleaching. When a coral bleaches, it is not dead. Corals can survive a bleaching event, but they are under more stress and are subject to mortality.The NOAA Coral Reef Watch program uses satellite data to provide current reef environmental conditions to quickly identify areas at risk for coral bleaching. The station data displayed in this map are derived from satellite based measurements of ocean temperature. These "virtual stations" are not actual buoys or in situ stations transmitting data, rather a spatial analyses for reef locations around the world are derived from 5 km resolution raster data. There are 213 points for the virtual stations around the world along with polygons describing the major tropical coral reef systems. Each station has several variables: Alert Level: an index of the likelihood of coral bleaching, scaled from 0 (no heat stress) to 4 (coral mortality likely) based on the attributes belowSea surface temperature: average temperature of the ocean surface derived from satellite measurementsTemperature anomaly: a comparison of the current surface temperature to the 1981-2010 historical averageHotspots: number of degrees above the coral's threshold toleranceDegree Heating Weeks: accumulated thermal stress experienced by coralsMaintenanceService data is maintained by the Overwrite Feature Service script running as a Scheduled Notebook TaskSee Sample OverwriteFS NotebookRevisionsJan 25, 2024: Updated Legend text for Area Layer, adding clarityJul 28, 2023: Applied updated Symbology and Popups from Coral Reef Bleaching Stations Web Map
Facebook
TwitterThis map is intended to provide general awareness of current and recent tropical weather around the world. It is not intended to replace authoritative government websites but rather to provide situational awareness.This map contains Live Feeds from the Living Atlas including - Active Hurricanes, Recent Hurricanes, Weather Warnings and Watches, Short-Term Weather Warnings, and NOAA Colorized Satellite Imagery. Weather Radar Data is provided courtesy of Baron Weather. This map is provided by the Esri Disaster Response Program using the Public Information Solution template. For other hurricane related content and data, please visit the DRP Hub Hurricane Page.
Facebook
TwitterThis data set is part of an ongoing project to consolidate interagency fire perimeter data. Currently only certified perimeters and new perimeters captured starting in 2021 are included. A process for loading additional perimeters is being evaluated.The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service includes perimeters for wildland fire incidents that meet the following criteria:Categorized in the IRWIN (Integrated Reporting of Wildland Fire Information) integration service as a Wildfire (WF) or Prescribed Fire (RX)Is Valid and not "quarantined" in IRWIN due to potential conflicts with other recordsAttribution of the source polygon is set to a Feature Access of Public, a Feature Status of Approved, and an Is Visible setting of YesPerimeters are not available for every incident. This data set is an ongoing project with the end goal of providing a national interagency fire history feature service of best-available perimeters.No "fall-off" rules are applied to this service. The date range for this service will extend from present day back indefinitely. Data prior to 2021 will be incomplete and incorporated as an ongoing project.Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed every 5 minutes. Changes in the perimeter source may take up to 15 minutes to display.Perimeters are pulled from multiple sources with rules in place to ensure the most current or most authoritative shape is used.Warning: Please refrain from repeatedly querying the service using a relative date range. This includes using the “(not) in the last” operators in a Web Map filter and any reference to CURRENT_TIMESTAMP. This type of query puts undue load on the service and may render it temporarily unavailable.Attributes and their definitions can be found below. More detail about the NWCG Wildland Fire Event Polygon standard can be found here.Attributes:poly_SourceOIDThe OBJECTID value of the source record in the source dataset providing the polygon.poly_IncidentNameThe incident name as stored in the polygon source record.poly_MapMethodThe mapping method with which the polygon was derived.poly_GISAcresThe acreage of the polygon as stored in the polygon source record.poly_CreateDateSystem generated date for the date time the source polygon record was created (stored in UTC).poly_DateCurrentSystem generated date for the date time the source polygon record was last edited (stored in UTC).poly_PolygonDateTimeRepresents the date time that the polygon data was captured.poly_IRWINIDIRWIN ID stored in the polygon record.poly_FORIDFORID stored in the polygon record.poly_Acres_AutoCalcSystem calculated acreage of the polygon (geodesic WGS84 acres).poly_SourceGlobalIDThe GlobalID value of the source record in the source dataset providing the polygon.poly_SourceThe source dataset providing the polygon.attr_SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.attr_ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.attr_ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.attr_ContainmentDateTimeThe date and time a wildfire was declared contained. attr_ControlDateTimeThe date and time a wildfire was declared under control.attr_CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.attr_IncidentSizeReported for a fire. The minimum size is 0.1.attr_DiscoveryAcresAn estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.attr_EstimatedCostToDateThe total estimated cost of the incident to date.attr_FinalAcresReported final acreage of incident.attr_FFReportApprovedByTitleThe title of the person that approved the final fire report for the incident.attr_FFReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.attr_FFReportApprovedDateThe date that the final fire report was approved for the incident.attr_FireBehaviorGeneralA general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. attr_FireBehaviorGeneral1A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral2A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral3A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. attr_FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. attr_FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. attr_FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. attr_FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.attr_FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.attr_FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. attr_FireOutDateTimeThe date and time when a fire is declared out. attr_FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.attr_FireStrategyFullSuppPrcntIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.attr_FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.attr_FireStrategyPointZonePrcntIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.attr_FSJobCodeA code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.attr_FSOverrideCodeA code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.attr_GACCA code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.attr_ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.attr_ICS209RptForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.attr_ICS209RptForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. attr_ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates, and even multiple finals (as determined by business rules).attr_IncidentManagementOrgThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.attr_IncidentNameThe name assigned to an incident.attr_IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. attr_IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category further breaks down the Event Kind into more specific event categories.attr_IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.attr_InitialLatitudeThe latitude location of the initial reported point of origin specified in decimal degrees.attr_InitialLongitudeThe longitude location of the initial reported point of origin specified in decimal degrees.attr_InitialResponseAcresAn estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Contents: This is an ArcGIS Pro zip file that you can download and use for creating map books based on United States National Grid (USNG). It contains a geodatabase, layouts, and tasks designed to teach you how to create a basic map book.Version 1.0.0 Uploaded on May 24th and created with ArcGIS Pro 2.1.3 - Please see the README below before getting started!Updated to 1.1.0 on August 20thUpdated to 1.2.0 on September 7thUpdated to 2.0.0 on October 12thUpdate to 2.1.0 on December 29thBack to 1.2.0 due to breaking changes in the templateBack to 1.0.0 due to breaking changes in the template as of June 11th 2019Updated to 2.1.1 on October 8th 2019Audience: GIS Professionals and new users of ArcGIS Pro who support Public Safety agencies with map books. If you are looking for apps that can be used by any public safety professional, see the USNG Lookup Viewer.Purpose: To teach you how to make a map book with critical infrastructure and a basemap, based on USNG. You NEED to follow the steps in the task and not try to take shortcuts the first time you use this task in order to receive the full benefits. Background: This ArcGIS Pro template is meant to be a starting point for your map book projects and is based on best practices by the USNG National Implementation Center (TUNIC) at Delta State University and is hosted by the NAPSG Foundation. This does not replace previous templates created in ArcMap, but is a new experimental approach to making map books. We will continue to refine this template and work with other organizations to make improvements over time. So please send us your feedback admin@publicsafetygis.org and comments below. Instructions: Download the zip file by clicking on the thumbnail or the Download button.Unzip the file to an appropriate location on your computer (C:\Users\YourUsername\Documents\ArcGIS\Projects is a common location for ArcGIS Pro Projects).Open the USNG Map book Project File (APRX).If the Task is not already open by default, navigate to Catalog > Tasks > and open 'Create a US National Grid Map Book' Follow the instructions! This task will have some automated processes and models that run in the background but you should pay close attention to the instructions so you also learn all of the steps. This will allow you to innovate and customize the template for your own use.FAQsWhat is US National Grid? The US National Grid (USNG) is a point and area reference system that provides for actionable location information in a uniform format. Its use helps achieve consistent situational awareness across all levels of government, disciplines, and threats & hazards – regardless of your role in an incident.One of the key resources NAPSG makes available to support emergency responders is a basic USNG situational awareness application. See the NAPSG Foundation and USNG Center websites for more information.What is an ArcGIS Pro Task? A task is a set of preconfigured steps that guide you and others through a workflow or business process. A task can be used to implement a best-practice workflow, improve the efficiency of a workflow, or create a series of interactive tutorial steps. See "What is a Task?" for more information.Do I need to be proficient in ArcGIS Pro to use this template? We feel that this is a good starting point if you have already taken the ArcGIS Pro QuickStart Tutorials. While the task will automate many steps, you will want to get comfortable with the map layouts and other new features in ArcGIS Pro.Is this template free? This resources is provided at no-cost, but also with no guarantees of quality assurance or support at this time. Can't I just use ArcMap? Ok - here you go. USNG 1:24K Map Template for ArcMapKnown Limitations and BugsZoom To: It appears there may be a bug or limitation with automatically zooming the map to the proper extent, so get comfortable with navigation or zoom to feature via the attribute table.FGDC Compliance: We are seeking feedback from experts in the field to make sure that this meets minimum requirements. At this point in time we do not claim to have any official endorsement of standardization. File Size: Highly detailed basemaps can really add up and contribute to your overall file size, especially over a large area / many pages. Consider making a simple "Basemap" of street centerlines and building footprints.We will do the best we can to address limitations and are very open to feedback!
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
PHS On The Web (POTW) is a web-based, interactive mapping tool for citizens, landowners, local governments, developers, conservation groups and others to find basic information about known locations of Priority Habitats and Species (PHS) in Washington State. PHS is a source of best available science that can inform local planning activities, development projects, conservation strategies, incentive programs, and numerous other applications. The three GIS layers provided in this file geodatabase are the layers displayed in the POTW (Public) online map application. The three layers are scheduled to be updated on the first Monday of each month. These three GIS layers are: WDFWPHSPlusPublicLine, WDFWPHSPlusPublicPoint, and WDFWPHSPlusPublicPolygon. In these three layers, sensitive species are not shown as mapped (as a point, line, or polygon) but the locations are masked as a Section (one square mile), Quarter Township (nine square miles), or Township (thirty-six square miles) polygons.Sensitive species and habitat information are defined in WDFW Policy 5210. Priority habitats and species locations deemed sensitive by WDFW are not publicly displayed beyond a certain resolution (e.g., township or section) due to an increased risk of human interference. Sensitive data is exempt from public disclosure under the Public Records Act; this term is defined in RCW 42.56.430. Sensitive species are any wildlife species likely to become endangered or threatened; this term is defined in WAC 200-200-100. Qualifying landowners, university researchers, government agencies, and tribes may request PHS maps that contain this sensitive data.Since this GIS layer contains non-sensitive species information, it can be used without limitations, but please acknowledge the Washington Department of Fish and Wildlife (WDFW) as the source of this information. Please do not distribute this data, instead refer others to WDFW. If you have any questions about this layer, you can contact PHS at this email address: phsproducts@dfw.wa.gov with a subject line of the email being "POTW Public Dataset Question".Please note, although mapped PHS data is useful for determining the general extent of priority species or habitats, the department has not surveyed the entire state of Washington. PHS map data is meant to serve as a starting point to identify priority habitats and species. It is not meant to replace or preempt more detailed field-based, site-level mapping. Site-specific surveys are usually needed to rule out the presence of priority habitats or species. PHS maps do not provide an official agency determination of the potential impacts to fish and wildlife of a specific project.Additional ResourcesPHS On The Web Application: https://geodataservices.wdfw.wa.gov/hp/phs/PHS On the Web Map Service: https://geodataservices.wdfw.wa.gov/arcgis/rest/services/PHSOnTheWeb/PHSOnTheWebPublic/MapServer
Facebook
TwitterThis interactive map provides geospatial information pertaining to the Lolo National Forest Plan Revision process. The intent of this tool is to provide an interactive experience that allows the user to display different combinations of layers and information. This product is provided to help enhance an understanding of the proposed action and alternatives for the Lolo Plan Revision Process.The Lolo Plan revision process is currently in the phase of developing alternatives, based on issues identified during the scoping period. This WebMap currently contains the layers that were included in the Proposed Action provided for scoping, as well as other contextual layers. Moving forward in the process, we anticipate using this tool to provide additional information of the alternatives for the draft environmental impact statement (DEIS). To understand the definitions and distinctions among terms used in the map layers and the details of the planning process, or to download data and review metadata for data within the dynamic map, we recommend reviewing the Forest Plan Revision document library here.The layers in this WebMap may be subject to change through the revision process, and additional layers may be added. Use of this product does not represent a formal commenting opportunity. This WebMap does not replace 508-compliant map products provided to the public during comment periods.Below is the subset of geospatial information presented in the web map that have been developed thus far during the Forest Plan Revision Process for the Lolo National Forest.Lolo National Forest Geographic AreasProposed Action designated areas, including existing designated wilderness, inventoried roadless areas, research natural areas, special areas, and national trailsProposed Action management areas, including recommended wilderness, suitable wild and scenic rivers, eligible wild and scenic rivers, backcountry, general forest, and focused recreationProposed Action Desired Recreation Opportunity Spectrum, Summer and WinterPreliminary Modified Proposed Action Desired Recreation Opportunity Spectrum, Summer and WinterProposed Action Scenic Integrity ObjectivesProposed Action Conservation Watershed NetworkProposed Action Timber SuitabilityProposed Action Priority WatershedsOther geospatial information presented in this web map is relevant to the revision process but was not created or altered by this Forest Plan Revision Process. This information includes:Wildland urban interface1986 Forest Plan management areas2006 Draft Plan management areasData Dependencies:Parent Experience Product: https://arcg.is/1mLru50Data: https://arcg.is/1q0bmm
Facebook
TwitterThe base for the roads layer was developed by the BLM using BLM data, USFS data, USGS DLG and other sources and is what was referred to as the GTRN dataset. The road layer is comprised of the best available data. This means that when road linework is enhanced through the protection map process or through district or program mapping efforts that the enhanced linework will replace or be integrated with the statewide layer. This road layer has specific designations for Protection Map display.
Facebook
TwitterWeb Instant App of Yard Waste pick up days for the citizens of Rock Island. As you go along making edits, reconcile and post these yard waste stops to be housed inside the default geodatabase. Make adds and deletes as you go and use the python script (location:S:\PW\GIS\Map Requests\2023_07_YardWasteAprxProjectAndRefuseRoutes\YardWasteCustomersTransferPythonTransfer.txt) for to update the yard waste stops () as you receive them in See-Click-Fix. Once that is done, overwrite the web layer in the Share Web layer tab. This will be needed to be updated as See-Click Requests are submitted.location of the APRX: S:\PW\GIS\Map Requests\2023_07_YardWasteAprxProjectAndRefuseRoutes
Facebook
TwitterGeo List is a configurable app template that allows you to present an ordered list of features based on the values of a field. Users can page through the feature one at a time.When authoring the app, keep in mind that the content displayed for each feature in the list is derived from the pop-up that has been authored in the web map. If you do not like the way it is presented then modify the pop-up in the map for the Ranking Layer. For more information on authoring pop-up content see this ArcGIS Help topic or this Get Started Lesson. Configurable OptionsUse Geo List to present a web map and configure it using the following options:Title, Descriptive or narrative text panel.Color theme for description panel, text, and selection symbol, Custom CSS option to override the application stylesheet.Ranking Layer is the feature layer that containes the features which will be ranked.Ranking Field this is the attribute that the ranking will be based upon.Number of feature presented in the list.Rank Order can be ascending or descending. Use this to define your list based on lowest to highest values or highest to lowest values within the ranking field.Zoom level will control the level of detail at which the ranked features will be displayed.Use CasesCreate a top ten list of a key demographic phenomenon.Entice users to explore the world's deadliest volcanos through a listicle type experience.Create a simple tour of locations in your area based on the order of an attribute.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsIn order to rank features for display the specified feature service must support the supportsOrderBy property which is available if the service is version 10.1 or greater.Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.
Facebook
TwitterMap Direct focus to show Mandatory Non-Phosphate (mannon) mine boundaries. These mines include the following resources: limestone, dolomite, shell, heavy minerals, fuller’s earth, peat, clay, gravel and sand. Please refer to https://floridadep.gov/water/mining-mitigation/content/other-resources for more information. If you have questions about the program, please contact the Mining and Mitigaiton Program:Mining and Mitigation Program2600 Blair Stone Road, MS 3577Tallahassee, Florida 32399-2400Email: MiningAndMitigation@dep.state.fl.usPhone: 850-245-8336This web map was created in 2018 to replace the Map Direct focus (mannon).
Facebook
TwitterDescription: This Notebook will prompt the user for a basemap they would like to replace, and a basemap to replace it with. Then the notebook will loop through all of the web maps the user has access to, it will look for the selected basemap, and replace it with the selected replacement basemap.Created on: 7/1/24Purpose: The purpose of this notebook is to streamline the workflow of updating the basemaps that are used in web maps. Many users have selected our local imagery as the basemap in their web maps, and as that imagery ages, it is important to update it with the updated imagery. This will allow the user to define the basemap they want to replace, a basemap to replace it with, then loop through all of the web maps the user has access to, and update the web maps with the selected replacement basemap.Parameters:Title of the basemap you want to replace.ItemID of the basemap you want to replace it with.Authored By: Joe GuziPrevious Production Date: 7/1/24Production Date: 7/18/24Note: The previous version of this notebook, was written specifically to replace Esri's Raster basemaps that were being deprecated. It can be downloaded here: https://www.arcgis.com/home/item.html?id=90cc2d7419f947d3ae55b44fd3090b24