The maps and tables presented here represent potential variability of projected climate change across the conterminous United States during three 30-year periods in this century and emphasizes the importance of evaluating multiple signals of change across large spatial domains. Maps of growing degree days, plant hardiness zones, heat zones, and cumulative drought severity depict the potential for markedly shifting conditions and highlight regions where changes may be multifaceted across these metrics. In addition to the maps, the potential change in these climate variables are summarized in tables according to the seven regions of the fourth National Climate Assessment to provide additional regional context. Viewing these data collectively further emphasizes the potential for novel climatic space under future projections of climate change and signals the wide disparity in these conditions based on relatively near-term human decisions of curtailing (or not) greenhouse gas emissions. More information available at https://www.fs.usda.gov/nrs/pubs/rmap/rmap_nrs9.pdf. This dataset represents heat zones, or the mean number of days over 30 C, in 4 time periods (1980-2009, 2010-2039, 2040-2069, and 2070-2099), using two emissions scenarios (RCP 4.5 and 8.5, the medium and high scenarios, respectively).

All data displayed on this map is near real-time. There are two ways in which this happens: Web service based data and a mobile mapping application called Field Maps. Web services are updated regularly ranging from every minute to once a month. All web services in this map are refreshed automatically to ensure the latest data being provided is displayed. Data collected through the use of Field Maps is done so by firefighters on the ground. The Field Maps application is consuming, creating, and editing data that are stored in ArcGIS Online. These data are then fed directly in to this map. To learn more about these web mapping technologies, visit the links below:Web ServicesArcGIS Field MapsArcGIS OnlineWeb Services used in this map:(visit link to learn more about each service)IRWIN - A central hub that orchestrates data between various fire reporting applications. When a new incident is created and/or updated by a dispatch center or other fire reporting system, it is then displayed on the map using the Integrated Reporting of Wildland-Fire Information (IRWIN) service. All layers below are derived from the same IRWIN service and automatically refresh every five minutes:New Starts (last 24hrs) - Any incident that has occurred within the last rolling 24 hour time period.Current Large Incidents - Incidents that have created an ICS 209 document at the type 3 Incident Commander (IC) level and above and are less than 100% contained.Ongoing - Incidents that do not have a containment, control, or out date.Contained - Incidents with a containment date but no control or out date.Controlled/Out (last 24hrs) - Incidents with a containment, control, and/or out date within the last rolling 24 hour time period.Controlled/Out - Incidents with a containment, control, and/or out date. Layer turned off by default.Season Summary - All incidents year to date. Layer turned off by default.ArcGIS Online/Field Maps - Part of the Esri Geospatial Cloud, ArcGIS Online and Collector enables firefighters to use web maps created in ArcGIS Online on mobile devices using the Collector application to capture and edit data on the fireline. Data may be captured and edited in both connected and disconnected environments. When data is submitted back to the web service in ArcGIS Online, it is then checked for accuracy and approved for public viewing.Fire Perimeter - Must be set to 'Approved' and 'Public' to be displayed on the map. Automatically refreshes every five minutes.NOAA nowCOAST - Provides web services of near real-time observations, analyses, tide predictions, model guidance, watches/warnings, and forecasts for the coastal United States by integrating data and information across NOAA, other federal agencies and regional ocean and weather observing systems (source). All layers below automatically refresh every five minutes.Tornado Warning - National Weather Service warning for short duration hazard.Severe Thunderstorm Warning - National Weather Service warning for short duration hazard.Flash Flood Warning - National Weather Service warning for short duration hazard.Red Flag Warning - National Weather Service warning for long duration hazard.nowCOAST Lightning Strike Density - 15-minute Satellite Emulated Lightning Strike Density imagery for the last several hours.nowCOAST Radar - Weather Radar (NEXRAD) Reflectivity Mosaics from NOAA MRMS for Alaska, CONUS, Puerto Rico, Guam, and Hawaii for last several hours.

The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Geographic Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map. Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Last Revised: February 2016 Map InformationThis nowCOAST™ time-enabled map service provides maps depicting the latest surface weather and marine weather observations at observing sites using the international station model. The station model is a method for representing information collected at an observing station using symbols and numbers. The station model depicts current weather conditions, cloud cover, wind speed, wind direction, visibility, air temperature, dew point temperature, sea surface water temperature, significant wave height, air pressure adjusted to mean sea level, and the change in air pressure over the last 3 hours. The circle in the model is centered over the latitude and longitude coordinates of the station. The total cloud cover is expressed as a fraction of cloud covering the sky and is indicated by the amount of circle filled in; however, all cloud cover values are presently displayed using the "Missing" symbol due to a problem with the source data. Present weather information is also not available for display at this time. Wind speed and direction are represented by a wind barb whose line extends from the cover cloud circle towards the direction from which the wind is blowing. The short lines or flags coming off the end of the long line are called barbs, which indicate wind speed in knots. Each normal barb represents 10 knots, while short barbs indicate 5 knots. A flag represents 50 knots. If there is no wind barb depicted, an outer circle around the cloud cover symbol indicates calm winds.Due to software limitations, the observations included in this map service are organized into three separate group layers: 1) Wind velocity (wind barb) observations, 2) Cloud Cover observations, and 3) All other observations, which are displayed as numerical values (e.g. Air Temperature, Wind Gust, Visibility, Sea Surface Temperature, etc.).Additionally, due to the density of weather/ocean observations in this map service, each of these group data layers has been split into ten individual "Scale Band" layers, with each one visible for a certain range of map scales. Thus, to ensure observations are displayed at any scale, users should make sure to always specify all ten corresponding scale band layers in every map request. This will result in the scale band most appropriate for your present zoom level being shown, resulting in a clean, uncluttered display. As you zoom in, additional observations will appear.The observations in this nowCOAST™ map service are updated approximately every 10 minutes. However, since the reporting frequency varies by network or station, the observations for a particular station may update only once per hour. For more detailed information about layer update frequency and timing, please reference the nowCOAST™ Dataset Update Schedule.Background InformationThe maps of near-real-time surface weather and ocean observations are based on non-restricted data obtained from the NWS Family of Services courtesy of NESDIS/OPSD and also the NWS Meteorological Assimilation Data Ingest System (MADIS). The data includes observations from terrestrial and maritime observing stations from the U.S.A. and other countries. For terrestrial networks, the platforms include but are not limited to ASOS, AWOS, RAWS, non-automated stations, U.S. Climate Reference Networks, many U.S. Geological Survey Stations via NWS HADS, several state DOT Road Weather Information Systems, and U.S. Historical Climatology Network-Modernization. For maritime areas, the platforms include NOS/CO-OPS National Water Level Observation Network (NWLON), NOS/CO-OPS Physical Oceanographic Real-Time System (PORTS), NWS/NDBC Fixed Buoys, NDBC Coastal-Marine Automated Network (C-MAN), drifting buoys, ferries, Regional Ocean Observing System (ROOS) coastal stations and buoys, and ships participating in the Voluntary Ship Observing (VOS) Program. Observations from MADIS are updated approximately every 10 minutes in the map service and those from NESDIS are updated every hour. However, not all stations report that frequently. Many stations only report once per hour sometime between 15 minutes before the hour and 30 minutes past the hour. For these stations, new observations will not appear until approximately 23 minutes past top of the hour for land-based stations and 33 minutes past the top of the hour for maritime stations.Time InformationThis map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:Issue a returnUpdates=true request (ArcGIS REST protocol only) for an individual layer or for the service itself, which will return the current start and end times of available data, in epoch time format (milliseconds since 00:00 January 1, 1970). To see an example, click on the "Return Updates" link at the bottom of the REST Service page under "Supported Operations". Refer to the ArcGIS REST API Map Service Documentation for more information.Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against the proper layer corresponding with the target dataset. For raster data, this would be the "Image Footprints with Time Attributes" layer in the same group as the target "Image" layer being displayed. For vector (point, line, or polygon) data, the target layer can be queried directly. In either case, the attributes returned for the matching raster(s) or vector feature(s) will include the following:validtime: Valid timestamp.starttime: Display start time.endtime: Display end time.reftime: Reference time (sometimes referred to as issuance time, cycle time, or initialization time).projmins: Number of minutes from reference time to valid time.desigreftime: Designated reference time; used as a common reference time for all items when individual reference times do not match.desigprojmins: Number of minutes from designated reference time to valid time.Query the nowCOAST™ LayerInfo web service, which has been created to provide additional information about each data layer in a service, including a list of all available "time stops" (i.e. "valid times"), individual timestamps, or the valid time of a layer's latest available data (i.e. "Product Time"). For more information about the LayerInfo web service, including examples of various types of requests, refer to the nowCOAST™ LayerInfo Help DocumentationReferencesNWS, 2013: Sample Station Plot, NWS/NCEP/WPC, College Park, MD (Available at http://www.wpc.ncep.noaa.gov/html/stationplot.shtml).NWS, 2013: Terminology and Weather Symbols, NWS/NCEP/OPC, College Park, MD (Available at http://www.opc.ncep.noaa.gov/product_description/keyterm.shtml).NWS, 2013: How to read Surface weather maps, JetStream an Online School for Weather (Available at http://www.srh.noaa.gov/jetstream/synoptic/wxmaps.htm).

This map displays the Quantitative Precipitation Forecast (QPF) for the next 72 hours across the contiguous United States. Data are updated hourly from the National Digital Forecast Database produced by the National Weather Service.The dataset includes incremental and cumulative precipitation data in 6-hour intervals. In the ArcGIS Online map viewer you can enable the time animation feature and select either the "Amount by Time" (incremental) layer or the "Accumulation by Time" (cumulative) layer to view a 72-hour animation of forecast precipitation. All times are reported according to your local time zone.Where is the data coming from?The National Digital Forecast Database (NDFD) was designed to provide access to weather forecasts in digital form from a central location. The NDFD produces forecast data of sensible weather elements. NDFD contains a seamless mosaic of digital forecasts from National Weather Service (NWS) field offices working in collaboration with the National Centers for Environmental Prediction (NCEP). All of these organizations are under the administration of the National Oceanic and Atmospheric Administration (NOAA).Source: https://tgftp.nws.noaa.gov/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/AR.conus/VP.001-003/ds.qpf.binWhere can I find other NDFD data?The Source data is downloaded and parsed using the Aggregated Live Feeds methodology to return information that can be served through ArcGIS Server as a map service or used to update Hosted Feature Services in Online or Enterprise.What can you do with this layer?This map service is suitable for data discovery and visualization. Identify features by clicking on the map to reveal the pre-configured pop-ups. View the time-enabled data using the time slider by Enabling Time Animation.This map 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!

Average historical temperature change, between 1948-1968 and 1996-2016 averages, in Celsius. Calculated using averages of minimum and maximum monthly values during these time periods. Values are based on TopoWx data, downloaded from here: http://www.scrimhub.org/resources/topowx/

Note: This LCMS CONUS Cause of Change image service has been deprecated. It has been replaced by the LCMS CONUS Annual Change image service, which provides updated and consolidated change data.Please refer to the new service here: https://usfs.maps.arcgis.com/home/item.html?id=085626ec50324e5e9ad6323c050ac84dThis product is part of the Landscape Change Monitoring System (LCMS) data suite. It shows LCMS change attribution classes for each year. See additional information about change in the Entity_and_Attribute_Information or Fields section below.LCMS is a remote sensing-based system for mapping and monitoring landscape change across the United States. Its objective is to develop a consistent approach using the latest technology and advancements in change detection to produce a "best available" map of landscape change. Because no algorithm performs best in all situations, LCMS uses an ensemble of models as predictors, which improves map accuracy across a range of ecosystems and change processes (Healey et al., 2018). The resulting suite of LCMS change, land cover, and land use maps offer a holistic depiction of landscape change across the United States over the past four decades.Predictor layers for the LCMS model include outputs from the LandTrendr and CCDC change detection algorithms and terrain information. These components are all accessed and processed using Google Earth Engine (Gorelick et al., 2017). To produce annual composites, the cFmask (Zhu and Woodcock, 2012), cloudScore, and TDOM (Chastain et al., 2019) cloud and cloud shadow masking methods are applied to Landsat Tier 1 and Sentinel 2a and 2b Level-1C top of atmosphere reflectance data. The annual medoid is then computed to summarize each year into a single composite. The composite time series is temporally segmented using LandTrendr (Kennedy et al., 2010; Kennedy et al., 2018; Cohen et al., 2018). All cloud and cloud shadow free values are also temporally segmented using the CCDC algorithm (Zhu and Woodcock, 2014). LandTrendr, CCDC and terrain predictors can be used as independent predictor variables in a Random Forest (Breiman, 2001) model. LandTrendr predictor variables include fitted values, pair-wise differences, segment duration, change magnitude, and slope. CCDC predictor variables include CCDC sine and cosine coefficients (first 3 harmonics), fitted values, and pairwise differences from the Julian Day of each pixel used in the annual composites and LandTrendr. Terrain predictor variables include elevation, slope, sine of aspect, cosine of aspect, and topographic position indices (Weiss, 2001) from the USGS 3D Elevation Program (3DEP) (U.S. Geological Survey, 2019). Reference data are collected using TimeSync, a web-based tool that helps analysts visualize and interpret the Landsat data record from 1984-present (Cohen et al., 2010).Outputs fall into three categories: change, land cover, and land use. Change relates specifically to vegetation cover and includes slow loss (not included for PRUSVI), fast loss (which also includes hydrologic changes such as inundation or desiccation), and gain. These values are predicted for each year of the time series and serve as the foundational products for LCMS. References: Breiman, L. (2001). Random Forests. In Machine Learning (Vol. 45, pp. 5-32). https://doi.org/10.1023/A:1010933404324Chastain, R., Housman, I., Goldstein, J., Finco, M., and Tenneson, K. (2019). Empirical cross sensor comparison of Sentinel-2A and 2B MSI, Landsat-8 OLI, and Landsat-7 ETM top of atmosphere spectral characteristics over the conterminous United States. In Remote Sensing of Environment (Vol. 221, pp. 274-285). https://doi.org/10.1016/j.rse.2018.11.012Cohen, W. B., Yang, Z., and Kennedy, R. (2010). Detecting trends in forest disturbance and recovery using yearly Landsat time series: 2. TimeSync - Tools for calibration and validation. In Remote Sensing of Environment (Vol. 114, Issue 12, pp. 2911-2924). https://doi.org/10.1016/j.rse.2010.07.010Cohen, W. B., Yang, Z., Healey, S. P., Kennedy, R. E., and Gorelick, N. (2018). A LandTrendr multispectral ensemble for forest disturbance detection. In Remote Sensing of Environment (Vol. 205, pp. 131-140). https://doi.org/10.1016/j.rse.2017.11.015Foga, S., Scaramuzza, P.L., Guo, S., Zhu, Z., Dilley, R.D., Beckmann, T., Schmidt, G.L., Dwyer, J.L., Hughes, M.J., Laue, B. (2017). Cloud detection algorithm comparison and validation for operational Landsat data products. Remote Sensing of Environment, 194, 379-390. https://doi.org/10.1016/j.rse.2017.03.026Gorelick, N., Hancher, M., Dixon, M., Ilyushchenko, S., Thau, D., and Moore, R. (2017). Google Earth Engine: Planetary-scale geospatial analysis for everyone. In Remote Sensing of Environment (Vol. 202, pp. 18-27). https://doi.org/10.1016/j.rse.2017.06.031Healey, S. P., Cohen, W. B., Yang, Z., Kenneth Brewer, C., Brooks, E. B., Gorelick, N., Hernandez, A. J., Huang, C., Joseph Hughes, M., Kennedy, R. E., Loveland, T. R., Moisen, G. G., Schroeder, T. A., Stehman, S. V., Vogelmann, J. E., Woodcock, C. E., Yang, L., and Zhu, Z. (2018). Mapping forest change using stacked generalization: An ensemble approach. In Remote Sensing of Environment (Vol. 204, pp. 717-728). https://doi.org/10.1016/j.rse.2017.09.029Kennedy, R. E., Yang, Z., and Cohen, W. B. (2010). Detecting trends in forest disturbance and recovery using yearly Landsat time series: 1. LandTrendr - Temporal segmentation algorithms. In Remote Sensing of Environment (Vol. 114, Issue 12, pp. 2897-2910). https://doi.org/10.1016/j.rse.2010.07.008Kennedy, R., Yang, Z., Gorelick, N., Braaten, J., Cavalcante, L., Cohen, W., and Healey, S. (2018). Implementation of the LandTrendr Algorithm on Google Earth Engine. In Remote Sensing (Vol. 10, Issue 5, p. 691). https://doi.org/10.3390/rs10050691Olofsson, P., Foody, G. M., Herold, M., Stehman, S. V., Woodcock, C. E., and Wulder, M. A. (2014). Good practices for estimating area and assessing accuracy of land change. In Remote Sensing of Environment (Vol. 148, pp. 42-57). https://doi.org/10.1016/j.rse.2014.02.015Pedregosa, F., Varoquaux, G., Gramfort, A., Michel, V., Thirion, B., Grisel, O., Blondel, M., Prettenhofer, P., Weiss, R., Dubourg, V., Vanderplas, J., Passos, A., Cournapeau, D., Brucher, M., Perrot, M. and Duchesnay, E. (2011). Scikit-learn: Machine Learning in Python. In Journal of Machine Learning Research (Vol. 12, pp. 2825-2830).Pengra, B. W., Stehman, S. V., Horton, J. A., Dockter, D. J., Schroeder, T. A., Yang, Z., Cohen, W. B., Healey, S. P., and Loveland, T. R. (2020). Quality control and assessment of interpreter consistency of annual land cover reference data in an operational national monitoring program. In Remote Sensing of Environment (Vol. 238, p. 111261). https://doi.org/10.1016/j.rse.2019.111261U.S. Geological Survey. (2019). USGS 3D Elevation Program Digital Elevation Model, accessed August 2022 at https://developers.google.com/earth-engine/datasets/catalog/USGS_3DEP_10mWeiss, A.D. (2001). Topographic position and landforms analysis Poster Presentation, ESRI Users Conference, San Diego, CAZhu, Z., and Woodcock, C. E. (2012). Object-based cloud and cloud shadow detection in Landsat imagery. In Remote Sensing of Environment (Vol. 118, pp. 83-94). https://doi.org/10.1016/j.rse.2011.10.028Zhu, Z., and Woodcock, C. E. (2014). Continuous change detection and classification of land cover using all available Landsat data. In Remote Sensing of Environment (Vol. 144, pp. 152-171). https://doi.org/10.1016/j.rse.2014.01.011This record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService For complete information, please visit https://data.gov.

GIS data is available on the Forest’s FTP site in the form of “shape files” or layers and is available free for downloading. To utilize these data layers you will need a program that uses the Geographic Information System (GIS) such as ESRI’s ArcMap, ArcView or the free map reading program ArcGIS Explorer. ArcGIS Explorer has tools that let you zoom in/out, print the map, and query data. It also has map tips to identify features, and a help menu. ArcGIS Explorer is available as a free download from the ESRI website. Included is a list of GIS data files available for the Shawnee National Forest. These GIS data files are updated on a continuing basis. It should be noted that this data may have been developed from sources of differing accuracy, accurate only at certain scales, based on modeling or interpretation, or incomplete while being created or revised. Overall accuracy, completeness and timeliness may vary. The following geospatial information/data was prepared by the Shawnee National Forests (US Forest Service). The Forest Service reserves the right to correct, update, modify or replace GIS data without notification. Resources in this dataset:Resource Title: Geospatial Data. File Name: Web Page, url: https://www.fs.usda.gov/main/shawnee/landmanagement/gis Information about the geospatial data and a ftp link to download Forest GIS Data Shapefiles.

Crowdsource Polling is a configurable app template that can be used for collecting feedback and assessing public sentiment for a series of proposals, plans, or events. Users are presented with a map and list of features containing the details of each proposal, plan, or event including any attached documents. These users can then submit their feedback in the form of votes and comments. Crowdsource Polling can be accessed anonymously and by authenticating via Twitter.Use CasesCrowdsource Polling can be configured to present information such as:proposed land use changesenvironmental impact pollingpublic comment on capital projectspublic comment on proposed rights of way for transmission systemsevents permit reviewConfigurable OptionsConfigure Crowdsource Polling to present content from any web map and personalize the app by modifying the following options: Display a custom title and logo in the application headerUse a custom color schemeChoose which layer contains the features for which feedback is being solicitedProvide custom instruction on the use of the app, contact information, credits, etc. in a highly configurable help windowSupported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Crowdsource Polling requires a web map with at least one feature layer. In addition, the following requirements must be met to expose full app functionality:To enable votes, this layer must have a numeric field for storing the number of votes on each featureTo collect comments, the feature layer must have a related tableTo capture the names of authenticated users, the layer must have a text field for storing this valueGet 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.Learn MoreFor release notes and more information on configuring this app, see the Crowdsource Polling documentation.

Mosaics are published as ArcGIS image serviceswhich circumvent the need to download or order data. GEO-IDS image services are different from standard web services as they provide access to the raw imagery data. This enhances user experiences by allowing for user driven dynamic area of interest image display enhancement, raw data querying through tools such as the ArcPro information tool, full geospatial analysis, and automation through scripting tools such as ArcPy. Image services are best accessed through the ArcGIS REST APIand REST endpoints (URL's). You can copy the OPS ArcGIS REST API link below into a web browser to gain access to a directory containing all OPS image services. Individual services can be added into ArcPro for display and analysis by using Add Data -> Add Data From Path and copying one of the image service ArcGIS REST endpoint below into the resultant text box. They can also be accessed by setting up an ArcGIS server connectionin ESRI software using the ArcGIS Image Server REST endpoint/URL. Services can also be accessed in open-source software. For example, in QGIS you can right click on the type of service you want to add in the browser pane (e.g., ArcGIS REST Server, WCS, WMS/WMTS) and copy and paste the appropriate URL below into the resultant popup window. All services are in Web Mercator projection. For more information on what functionality is available and how to work with the service, read the Ontario Web Raster Services User Guide. If you have questions about how to use the service, email Geospatial Ontario (GEO) at geospatial@ontario.ca Available Products: ArcGIS REST APIhttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/ Image Service ArcGIS REST endpoint / URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer https://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer https://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServerWeb Coverage Services (WCS) URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer/WCSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer/WCSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServer/WCSServer/Web Mapping Service (WMS) URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer/WMSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer/WMSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServer/WMSServer/ Metadata for all imagery products available in GEO-IDS can be accessed at the links below:South Central Ontario Orthophotography Project (SCOOP) 2023North-Western Ontario Orthophotography Project (NWOOP) 2022 Central Ontario Orthophotography Project (COOP) 2021 South-Western Ontario Orthophotography Project (SWOOP) 2020 Digital Raster Acquisition Project Eastern Ontario (DRAPE) 2019-2020 South Central Ontario Orthophotography Project (SCOOP) 2018 North-Western Ontario Orthophotography Project (NWOOP) 2017 Central Ontario Orthophotography Project (COOP) 2016 South-Western Ontario Orthophotography Project (SWOOP) 2015 Algonquin Orthophotography Project (2015) Additional Documentation: Ontario Web Raster Services User Guide (Word) Status:Completed: Production of the data has been completed Maintenance and Update Frequency:Annually: Data is updated every year Contact:Geospatial Ontario (GEO), geospatial@ontario.ca

Last Revised: February 2016

Map Information

This nowCOAST™ time-enabled map service provides maps of lightning strike density data from the NOAA/National Weather Service/NCEP's Ocean Prediction Center (OPC) which emulate (simulate) data from the future NOAA GOES-R Global Lightning Mapper (GLM). The purpose of this product is to provide mariners and others with enhanced "awareness of developing and transitory thunderstorm activity, to give users the ability to determine whether a cloud system is producing lightning and if that activity is increasing or decreasing..." Lightning Strike Density, as opposed to display of individual strikes, highlights the location of lightning cores and trends of increasing and decreasing activity. The maps depict the density of lightning strikes during a 15 minute time period at an 8 km x 8 km spatial resolution. The lightning strike density maps cover the geographic area from 25 degrees South to 80 degrees North latitude and from 110 degrees East to 0 degrees West longitude. The map units are number of strikes per square km per minute multiplied by a scaling factor of 10^3. The strike density is color coded using a color scheme which allows the data to be easily seen when overlaid on GOES imagery and to distinguish areas of low and high density values. The maps are updated on nowCOAST™ approximately every 15 minutes. The latest data depicted on the maps are approximately 12 minutes old (or older). Given the spatial resolution and latency of the data, the data should NOT be used to activite your lightning safety plans. Always follow the safety rule: when you first hear thunder or see lightning in your area, activate your emergency plan. If outdoors, immediately seek shelter in a substantial building or a fully enclosed metal vehicle such as a car, truck or van. Do not resume activities until 30 minutes after the last observed lightning or thunder. For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.

Background Information

The source for the data is OPC's gridded lightning strike density data on an 8x8 km grid. The gridded data emulate the spatial resolution of the future Global Lightning Mapper (GLM) instrument to be flown on the NOAA GOES-R series of geostationary satellites, with the first satellite scheduled for launch in late 2016.

The gridded data is based on data from Vaisala's ground based U.S. National Lightning Detection Network (NLDN) and its global lightning detection network referred to as the Global Lightning Dataset (GLD360). These networks are capable of detecting cloud-to-ground strikes, cloud-to-ground flash information and survey level cloud lightning information. According to the National Lightning Safety Institute, NLDN uses radio frequency detectors in the spectrum 1.0 kHz through 400 kHz to measure energy discharges from lightning as well as approximate distance and direction. According to Vaisala, the GLD360 network is capable of a detection efficiency greater than 70% over most of the Northern Hemisphere with a median location accuracy of 5 km or better. OPC's gridded data are coarser than the original source data from Vaisala's networks. The 15-minute gridded source data are updated at OPC every 15 minutes at 10 minutes past the valid time.

The lightning strike density product from NWS/NCEP/OPC is considered a derived product or Level 5 product ("NOAA-generated products using lightning data as input but not displaying the contractor transmitted/provided lightning data") and is appropriate for public distribution.

Time Information

This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.

In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.

This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.

This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.

When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.

Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:

  Issue a returnUpdates=true request (ArcGIS REST protocol only)
  for an individual layer or for the service itself, which will return
  the current start and end times of available data, in epoch time format
  (milliseconds since 00:00 January 1, 1970). To see an example, click on
  the "Return Updates" link at the bottom of the REST Service page under
  "Supported Operations". Refer to the
  ArcGIS REST API Map Service Documentation
  for more information.


  Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
  the proper layer corresponding with the target dataset. For raster
  data, this would be the "Image Footprints with Time Attributes" layer
  in the same group as the target "Image" layer being displayed. For
  vector (point, line, or polygon) data, the target layer can be queried
  directly. In either case, the attributes returned for the matching
  raster(s) or vector feature(s) will include the following:


      validtime: Valid timestamp.


      starttime: Display start time.


      endtime: Display end time.


      reftime: Reference time (sometimes referred to as
      issuance time, cycle time, or initialization time).


      projmins: Number of minutes from reference time to valid
      time.


      desigreftime: Designated reference time; used as a
      common reference time for all items when individual reference
      times do not match.


      desigprojmins: Number of minutes from designated
      reference time to valid time.




  Query the nowCOAST™ LayerInfo web service, which has been created to
  provide additional information about each data layer in a service,
  including a list of all available "time stops" (i.e. "valid times"),
  individual timestamps, or the valid time of a layer's latest available
  data (i.e. "Product Time"). For more information about the LayerInfo
  web service, including examples of various types of requests, refer to
  the 
  nowCOAST™ LayerInfo Help Documentation

References

Kithil, 2015: Overview of Lightning Detection Equipment, National
Lightning Safety Institute, Louisville, CO. (Available from
http://www.lightningsafety.com/nsli_ihm/detectors.html).


NASA and NOAA, 2014: Geostationary Lightning Mapper (GLM). (Available at
http://www.goes-r.gov/spacesegment/glm.html).


NWS, 2013: Lightning Strike Density Product Description Document.
NOAA/NWS/NCEP/Ocean Prediction Center, College Park, MD (Available at
http://www.opc.ncep.noaa.gov/lightning/lightning_pdd.php
and http://products.weather.gov/PDD/Experimental%20Lightning%20Strike%20Density%20Product%2020130913.pdf).


NOAA Knows Lightning. NWS, Silver Spring, MD (Available at
http://www.lightningsafety.noaa.gov/resources/lightning3_050714.pdf).


Siebers, A., 2013: Soliciting Comments until June 3, 2014 on an
Experimental Lightning Strike Density product (Offshore Waters). Public
Information Notice, NOAA/NWS Headquarters, Washington, DC (Available at
http://www.nws.noaa.gov/om/notification/pns13lightning_strike_density.htm).

This series of products from MODIS represents the only daily global composites available and is suitable for use at global and regional levels. This True Color band composition (Bands 1 4 3 | Red, Green, Blue) most accurately shows how we see the earth’s surface with our own eyes. It is a natural looking image that is useful for land surface, oceanic and atmospheric analysis. There are four True Color products in total. For each satellite (Aqua and Terra) there is a 250 meter corrected reflectance product and a 500 meter surface reflectance product. Although the resolution is coarser than other satellites, this allows for a global collection of imagery on a daily basis, which is made available in near real-time. In contrast, Landsat needs 16 days to collect a global composite. Besides the maximum resolution difference, the surface and corrected reflectance products also differ in the algorithm used for atmospheric correction.NASA Global Imagery Browse Services (GIBS)This image layer provides access to a subset of the NASA Global Imagery Browse Services (GIBS), which are a set of standard services to deliver global, full-resolution satellite imagery. The GIBS goal is to enable interactive exploration of NASA's Earth imagery for a broad range of users. The purpose of this image layer, and the other GIBS image services hosted by Esri, is to enable convenient access to this beautiful and useful satellite imagery for users of ArcGIS. The source data used by this image layer is a finished image; it is not recommended for quantitative analysis.Several full resolution, global imagery products are built and served by GIBS in near real-time (usually within 3.5 hours of observation). These products are built from NASA Earth Observing System satellites data courtesy of LANCE data providers and other sources. The MODIS instrument aboard Terra and Aqua satellites, the AIRS instrument aboard Aqua, and the OMI instrument aboard Aura are used as sources. Several of the MODIS global products are made available on this Esri hosted service.This image layer hosted by Esri provides direct access to one of the GIBS image products. The Esri servers do not store any of this data itself. Instead, for each received data request, multiple image tiles are retrieved from GIBS, which are then processed and assembled into the proper image for the response. This processing takes place on-the-fly, for each and every request. This ensures that any update to the GIBS data is immediately available in the Esri mosaic service.Note on Time: The image service supporting this map is time enabled, but time has been disabled on this image layer so that the most recent imagery displays by default. If you would like to view imagery over time, you can update the layer properties to enable time animation and configure time settings. The results can be saved in a web map to use later or share with others.

Geoform is a configurable app template for form based data editing of a Feature Service. This application allows users to enter data through a form instead of a map's pop-up while leveraging the power of the Web Map and editable Feature Services. This app geo-enables data and workflows by lowering the barrier of entry for completing simple tasks. Use CasesProvides a form-based experience for entering data through a form instead of a map pop-up. This is a good choice for users who find forms a more intuitive format than pop-ups for entering data.Useful to collect new point data from a large audience of non technical staff or members of the community.Configurable OptionsGeoform has an interactive builder used to configure the app in a step-by-step process. Use Geoform to collect new point data and configure it using the following options:Choose a web map and the editable layer(s) to be used for collection.Provide a title, logo image, and form instructions/details.Control and choose what attribute fields will be present in the form. Customize how they appear in the form, the order they appear in, and add hint text.Select from over 15 different layout themes.Choose the display field that will be used for sorting when viewing submitted entries.Enable offline support, social media sharing, default map extent, locate on load, and a basemap toggle button.Choose which locate methods are available in the form, including: current location, search, latitude and longitude, USNG coordinates, MGRS coordinates, and UTM coordinates.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. 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.

This image service is part of a collection of maps for PGA, PGV and spectral accelerations at 0.2 s (SA02), 1.0 s (SA10), and 2.0 s (SA20) to illustrate seismic hazards in California. For each ground motion parameter, maps at two different hazard levels were presented: one with a 2% probability of being exceeded in 50 years (equivalent to 2,475-year recurrence interval) and the other with 10% probability of being exceeded in 50 years (equivalent to 475-year recurrence interval). The ArcGIS Online interface allows users to select any two ground motion hazard maps to compare side by side. Ground motion parameters were calculated using the 2023 update of the U.S. Geological Survey National Seismic Hazard Model. See the “Scientific Background” on MS48 webpage for detailed information.Due to software limitations, symbology cannot be added to this service. To match the symbology used in the MS48 Ground Motion application, use the following configuration:Esri Color Ramp: MagmaMinimum: 4.41 gMaximum: 0.032 gGamma: 1

This map service is a one-stop location to view and explore Kentucky geologic map data and related-data (geologic outcrops, photos, and diagrams), Kentucky water wells and springs, Kentucky oil and gas wells. All features are provided by the Kentucky Geological Survey via ArcGIS Server services. This map service displays the 1:500,000-scale geologic map of Kentucky at scales smaller than 1:100,000, and 1:24,000-scale geological quadrangle data at larger scales. The 1:500,000-scale geologic map data were derived from the 1988 Geologic Map of Kentucky, which was compiled by Martin C. Noger (KGS) from the 1981 Geologic Map of Kentucky (Scale 1:250,000) by McDowell and others (USGS). The 1:24,000-scale geologic map data and the fault data were compiled from 707 Geological Survey 7.5-minute geologic quadrangle maps, which were digitized during the Kentucky Geological Survey Digital Mapping Program (1996-2006).The basemap data is provided via ArcGIS Server services hosted by the Kentucky Office of Geographic Information.Some tools are provided to help explore the map data:- Query tool: use this tool to search on the KGS database of lithologic descriptions. Most descriptions are derived from the 707 1:24,000 geological quadrangle maps. Once a search is completed, every unit that contains the search parameters is highlighted on the map service.- ID tools: users can identify and get detailed info on geologic units and other map features using either the point, area, or buffer identification tools.A few notes on this service:- the legend is dynamic for the viewed extent. It is provided via a database call using the current map extent.- the oil and gas and water wells are ArcGIS Server services that update dynamically from the KGS database.- the geologic map and faults are dynamic ArcGIS Server map services.- the user can link to other geologic data for the viewed extent using the links provided in the "Geologic Info" tab.- you can query the entire KGS lithologic description database and highlight the relevant geologic units based on the query.

Last Revised: February 2016

Map Information

This nowCOAST™ time-enabled map service provides maps depicting the latest global forecast guidance of water currents, water temperature, and salinity at forecast projections: 0, 12, 24, 36, 48, 60, 72, 84, and 96-hours from the NWS/NCEP Global Real-Time Ocean Forecast System (GRTOFS). The surface water currents velocity maps display the direction using white or black streaklets. The magnitude of the current is indicated by the length and width of the streaklet. The maps of the GRTOFS surface forecast guidance are updated on the nowCOAST™ map service once per day. For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.

Background Information

GRTOFS is based on the Hybrid Coordinates Ocean Model (HYCOM), an eddy resolving, hybrid coordinate numerical ocean prediction model. GRTOFS has global coverge and a horizontal resolution of 1/12 degree and 32 hybrid vertical layers. It has one forecast cycle per day (i.e. 0000 UTC) which generates forecast guidance out to 144 hours (6 days). However, nowCOAST™ only provides guidance out to 96 hours (4 days). The forecast cycle uses 3-hourly momentum and radiation fluxes along with precipitation predictions from the NCEP Global Forecast System (GFS). Each forecast cycle is preceded with a 48-hr long nowcast cycle. The nowcast cycle uses daily initial 3-D fields from the NAVOCEANO operational HYCOM-based forecast system which assimilates situ profiles of temperature and salinity from a variety of sources and remotely sensed SST, SSH and sea-ice concentrations. GRTOFS was developed by NCEP/EMC/Marine Modeling and Analysis Branch. GRTOFS is run once per day (0000 UTC forecast cycle) on the NOAA Weather and Climate Operational Supercomputer System (WCOSS) operated by NWS/NCEP Central Operations.

The maps are generated using a visualization technique developed by the Data Visualization Research Lab at The University of New Hampshire's Center for Coastal and Ocean Mapping (http://www.ccom.unh.edu/vislab/). The method combines two techniques. First, equally spaced streamlines are computed in the flow field using Jobard and Lefer's (1977) algorithm. Second, a series of "streaklets" are rendered head to tail along each streamline to show the direction of flow. Each of these varies along its length in size, color and transparency using a method developed by Fowler and Ware (1989), and later refined by Mr. Pete Mitchell and Dr. Colin Ware (Mitchell, 2007).

Time Information

This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.

In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.

This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.

This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.

When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.

Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:

  Issue a returnUpdates=true request (ArcGIS REST protocol only)
  for an individual layer or for the service itself, which will return
  the current start and end times of available data, in epoch time format
  (milliseconds since 00:00 January 1, 1970). To see an example, click on
  the "Return Updates" link at the bottom of the REST Service page under
  "Supported Operations". Refer to the
  ArcGIS REST API Map Service Documentation
  for more information.


  Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
  the proper layer corresponding with the target dataset. For raster
  data, this would be the "Image Footprints with Time Attributes" layer
  in the same group as the target "Image" layer being displayed. For
  vector (point, line, or polygon) data, the target layer can be queried
  directly. In either case, the attributes returned for the matching
  raster(s) or vector feature(s) will include the following:


      validtime: Valid timestamp.


      starttime: Display start time.


      endtime: Display end time.


      reftime: Reference time (sometimes referred to as
      issuance time, cycle time, or initialization time).


      projmins: Number of minutes from reference time to valid
      time.


      desigreftime: Designated reference time; used as a
      common reference time for all items when individual reference
      times do not match.


      desigprojmins: Number of minutes from designated
      reference time to valid time.




  Query the nowCOAST™ LayerInfo web service, which has been created to
  provide additional information about each data layer in a service,
  including a list of all available "time stops" (i.e. "valid times"),
  individual timestamps, or the valid time of a layer's latest available
  data (i.e. "Product Time"). For more information about the LayerInfo
  web service, including examples of various types of requests, refer to
  the 
  nowCOAST™ LayerInfo Help Documentation

References

Fowler, D. and C. Ware, 1989: Strokes for Representing Vector Field Maps. Proceedings: Graphics Interface '98 249-253. Jobard, B and W. Lefer,1977: Creating evenly spaced streamlines of arbitrary density. Proceedings: Eurographics workshop on Visualization in Scientific Computing. 43-55. Mitchell, P.W., 2007: The Perceptual optimization of 2D Flow Visualizations Using Human in the Loop Local Hill Climbing. University of New Hampshire Masters Thesis. Department of Computer Science. NWS, 2013: About Global RTOFS, NCEP/EMC/MMAB, College Park, MD (Available at http://polar.ncep.noaa.gov/global/about/). Chassignet, E.P., H.E. Hurlburt, E.J. Metzger, O.M. Smedstad, J. Cummings, G.R. Halliwell, R. Bleck, R. Baraille, A.J. Wallcraft, C. Lozano, H.L. Tolman, A. Srinivasan, S. Hankin, P. Cornillon, R. Weisberg, A. Barth, R. He, F. Werner, and J. Wilkin, 2009: U.S. GODAE: Global Ocean Prediction with the HYbrid Coordinate Ocean Model (HYCOM). Oceanography, 22(2), 64-75. Mehra, A, I. Rivin, H. Tolman, T. Spindler, and B. Balasubramaniyan, 2011: A Real-Time Operational Global Ocean Forecast System, Poster, GODAE OceanView –GSOP-CLIVAR Workshop in Observing System Evaluation and Intercomparisons, Santa Cruz, CA.

The MassDEP Wetlands Change layer contains polygon features identified as being a wetland change area based on one of the following MassGIS color ortho imagery (aerial photography) products: 2001-2003, 2005, 2008-2009 and 2011-2012. The attribute codes in the polygon layer describe different types of wetland environments and different types of reasons for the wetlands change.More details...Map service also available.MassDEP application

The maps and tables presented here represent potential variability of projected climate change across the conterminous United States during three 30-year periods in this century and emphasizes the importance of evaluating multiple signals of change across large spatial domains. Maps of growing degree days, plant hardiness zones, heat zones, and cumulative drought severity depict the potential for markedly shifting conditions and highlight regions where changes may be multifaceted across these metrics. In addition to the maps, the potential change in these climate variables are summarized in tables according to the seven regions of the fourth National Climate Assessment to provide additional regional context. Viewing these data collectively further emphasizes the potential for novel climatic space under future projections of climate change and signals the wide disparity in these conditions based on relatively near-term human decisions of curtailing (or not) greenhouse gas emissions. More information available at https://www.fs.usda.gov/nrs/pubs/rmap/rmap_nrs9.pdf.This record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService For complete information, please visit https://data.gov.

This map contains continuously updated U.S. tornado reports, wind storm reports and hail storm reports. Click each feature to receive information about the specific location and read a short description about the issue. Now contains ALL available Incident Report types, for a total of 15, not just Hail; Wind; and Tornados.See new layer for details or Feature Layer Item with exclusive Past 24-Hour ALL Storm Reports Layer. Each layer is updated 4 times hourly from data provided by NOAA’s National Weather Service Storm Prediction Center. A full archive of storm events can be accessed from the NOAA National Centers for Environmental Information. SourceNOAA Storm Prediction Center https://www.spc.noaa.gov/climo/reportsNOAA ALL Storm Reports layer https://www.spc.noaa.gov/exper/reports Sample DataSee Sample Layer Item for sample data during inactive periods! Update FrequencyThe service is updated every 15 minutes using the Aggregated Live Feeds Methodology Area CoveredCONUS (Contiguous United States) What can you do with this layer? This map service is suitable for data discovery and visualization.Change the symbology of each layer using single or bi-variate smart mapping. For instance, use size or color to indicate the intensity of a tornado.Click each feature to receive information about the specific location and read a short description about the issue.Query the attributes to show only specific event types or locations. RevisionsAug 10, 2021: Updated Classic Layers to use new Symbols. Corrected Layer Order Presentation. Updated Thumbnail.Aug 8, 2021: Update to layer-popups, correcting link URLs. Expanded length of 'Comment' fields to 1kb of text. New Layer added that includes ALL available Incident Types and Age in 'Hours Old'. This map 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.

Last Revised: February 2016

Map Information

This nowCOAST™ time-enabled map service provides maps depicting the NWS Multi-Radar Multi-Sensor (MRMS) quantitative precipitation estimate mosaics for 1-, 3-, 6-, 12-, 24-, 48-, and 72-hr time periods at a 1 km (0.6 miles) horizontal resolution for CONUS and southern part of Canada. The precipitation estimates are based only on radar data. The total precipitation amount is indicated by different colors at 0.01, 0.10, 0.25 inches and then at 1/4 inch intervals up to 4.0 inches (e.g. 0.50, 0.75, 1.00, 1.25, etc.), at 1-inch intervals from 4 to 10 inches and then at 2-inch intervals up to 14+ inches. The increments from 0.01 to 1.00 or 2.00 inches are similar to what are used on NCEP's Weather Prediction Center QPF products and the NWS River Forecast Center (RFC) daily precipitation analysis. The 1-hr mosaic is updated every 4 minutes with a latency on nowCOAST™ of about 6-7 minutes from valid time. The 3-, 6-, 12-, and 24-hr QPEs are updated on nowCOAST™ every hour for the period ending at the top of the hour. The 48- and 72-hr QPEs are generated daily for the period ending at 12 UTC (i.e. 7AM EST) and available on nowCOAST™ shortly afterwards. For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.

Background Information

The NWS Multi-Radar Multi-Sensor System (MRMS)/Q3 QPEs are radar-only based quantitative precipitation analyses. The 1-hr precipitation accumulation is obtained by aggregating 12 instantaneous rate fields. Missing rate fields are filled with the neighboring rate fields if the data gap is not significantly large (e.g.<=15 minutes). The instantaneous rate is computed from the hybrid scan reflectivity and the precipitation flag fields (both are 2-D derivative products from the National 3-D Reflectivity Mosaic grid which has a 1-km horizontal resolution, 31 vertical levels and a 5-minute update cycle). The instantaneous rate currently uses four Z-R relationships (i.e. tropical, convective, stratiform, or snow). The particular ZR relationship used in any grid cell depends on precipitation type which is indicated by the precipitation flag. The other accumulation products are derived by aggregating the hourly accumulations. The 1-hr QPE are generated every 4 minutes, while the 3-, 6-, 12-, and 24-hr accumulations are generated every hour at the top of the hour. The 48- and 72-hr QPEs are updated daily at approximately 12 UTC. MRMS was developed by NOAA/OAR/National Severe Storms Laboratory and migrated into NWS operations at NOAA Integrated Dissemination Program.

Time Information

This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.

In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.

This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.

This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.

When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.

Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:

  Issue a returnUpdates=true request (ArcGIS REST protocol only)
  for an individual layer or for the service itself, which will return
  the current start and end times of available data, in epoch time format
  (milliseconds since 00:00 January 1, 1970). To see an example, click on
  the "Return Updates" link at the bottom of the REST Service page under
  "Supported Operations". Refer to the
  ArcGIS REST API Map Service Documentation
  for more information.


  Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
  the proper layer corresponding with the target dataset. For raster
  data, this would be the "Image Footprints with Time Attributes" layer
  in the same group as the target "Image" layer being displayed. For
  vector (point, line, or polygon) data, the target layer can be queried
  directly. In either case, the attributes returned for the matching
  raster(s) or vector feature(s) will include the following:


      validtime: Valid timestamp.


      starttime: Display start time.


      endtime: Display end time.


      reftime: Reference time (sometimes referred to as
      issuance time, cycle time, or initialization time).


      projmins: Number of minutes from reference time to valid
      time.


      desigreftime: Designated reference time; used as a
      common reference time for all items when individual reference
      times do not match.


      desigprojmins: Number of minutes from designated
      reference time to valid time.




  Query the nowCOAST™ LayerInfo web service, which has been created to
  provide additional information about each data layer in a service,
  including a list of all available "time stops" (i.e. "valid times"),
  individual timestamps, or the valid time of a layer's latest available
  data (i.e. "Product Time"). For more information about the LayerInfo
  web service, including examples of various types of requests, refer to
  the 
  nowCOAST™ LayerInfo Help Documentation

References

For more information about the MRMS/Q3 system, please see http://nmq.ou.edu and http://www.nssl.noaa.gov/projects/mrms.