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.

Use the Attachment Viewer template to provide an app for users to explore a layer's features and review attachments with the option to update attribute data. Present your images, videos, and PDF files collected using ArcGIS Field Maps or ArcGIS Survey123 workflows. Choose an attachment-focused layout to display individual images beside your map or a map-focused layout to highlight your map next to a gallery of images. Examples: Review photos collected during emergency response damage inspections. Display the results of field data collection and support downloading images for inclusion in a report. Present a map of land parcel along with associated documents stored as attachments. Data requirements The Attachment Viewer template requires a feature layer with attachments. It includes the capability to view attachments of a hosted feature service or an ArcGIS Server feature service (10.8 or later). Currently, the app can display JPEG, JPG, PNG, GIF, MP4, QuickTime (.mov), and PDF files in the viewer window. All other attachment types are displayed as a link. Key app capabilities App layout - Choose between an attachment-focused layout, which displays one attachment at a time in the main panel of the app with the map on the side, or a map-focused layout, which displays the map in the main panel of the app with a gallery of attachments. Feature selection - Allows users to select features in the map and view associated attachments. Review data - Enable tools to review and update existing records. Zoom, pan, download images - Allow users to interact with and download attachments. Language switcher - Provide translations for custom text and create a multilingual app. Home, Zoom controls, Legend, Layer List, Search Supportability This web app is designed responsively to be used in browsers on desktops, mobile phones, and tablets. We are committed to ongoing efforts towards making our apps as accessible as possible. Please feel free to leave a comment on how we can improve the accessibility of our apps for those who use assistive technologies.

Pistekenttäpalvelua tarjotaan julkisena palveluna Tšekin pistekenttien nykyisen tietokannan kautta. Tiedot toimitetaan karttapalvelun, WMS:n ja WFS:n muodossa.

Information Lookup is a configurable web application template that can be used to provide the general public, internal staff and other interested parties with information about a location. If no features are found at that location, a general message is displayed. Optionally, the location entered can be stored in a point layer.Configurable OptionsThe template can be configured using the following options:Lookup Layers: One or more polygon layers queried by the location specified. The pop-up defined in these layers combined into a single pop-up and displayed to the user. The layers can either be a feature service layer or a layer that is part of a dynamic map service. Use a vertical bar or pipe (|) to separate this list of layers. It is recommended that these layers visibility is turned off.Pop-up Title: The title of the pop-up when results are returned from one or more of the Lookup Layers.Pop-up Width: The width of the pop-up. pop-up Max Height: The maximum height title of the pop-up.Unavailable pop-up Title: The title of the pop-up when no results are returned from the Lookup Layers.Unavailable pop-up Message: The message to display in the pop-up when no results are returned from the Lookup Layers.Zoom Level for Location: The scale to set the map at when a location is specified.Store Location: Option to store the location specified in a point layer, if checked on, fill out the remaining parameters.Application Title: Enter a custom title for the application.Storage Layer Name: Name of the point feature service layer in the map to store the location. Editing must be enabled on this layer.Storage Layer Field: Field in the Storage Layer to store a value if a result was returned from the Lookup Layers.Yes Value: The value to store in the Storage Layer Field specified above when a result is returned from the Lookup Layers.No Value: The value to store in the Storage Layer Field specified above when no results are returned from the Lookup Layers.Display Splash Screen on Startup: Option to show a splash screen when the app loads.Splash Screen message: The message to display in the splash screen.Splash Screen Theme: The color scheme for the splash screen.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.

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

This map contains a number of world-wide dynamic image services providing access to various Landsat scenes covering the landmass of the World for visual interpretation. Landsat 8 collects new scenes for each location on Earth every 16 days, assuming limited cloud coverage. Newest and near cloud-free scenes are displayed by default on top. Most scenes collected since 1st January 2015 are included. The service also includes scenes from the Global Land Survey* (circa 2010, 2005, 2000, 1990, 1975).The service contains a range of different predefined renderers for Multispectral, Panchromatic as well as Pansharpened scenes. The layers in the service can be time-enabled so that the applications can restrict the displayed scenes to a specific date range. This ArcGIS Server dynamic service can be used in Web Maps and ArcGIS Desktop, Web and Mobile applications using the REST based image services API. Users can also export images, but the exported area is limited to maximum of 2,000 columns x 2,000 rows per request.Data Source: The imagery in these services is sourced from the U.S. Geological Survey (USGS) and the National Aeronautics and Space Administration (NASA). The data for these services reside on the Landsat Public Datasets hosted on the Amazon Web Service cloud. Users can access full scenes from https://github.com/landsat-pds/landsat_ingestor/wiki/Accessing-Landsat-on-AWS, or alternatively access http://landsatlook.usgs.gov to review and download full scenes from the complete USGS archive.For more information on Landsat 8 images, see http://landsat.usgs.gov/landsat8.php.*The Global Land Survey includes images from Landsat 1 through Landsat 7. Band numbers and band combinations differ from those of Landsat 8, but have been mapped to the most appropriate band as in the above table. For more information about the Global Land Survey, visit http://landsat.usgs.gov/science_GLS.php.For more information on each of the individual layers, see http://www.arcgis.com/home/item.html?id=d9b466d6a9e647ce8d1dd5fe12eb434b ; http://www.arcgis.com/home/item.html?id=6b003010cbe64d5d8fd3ce00332593bf ; http://www.arcgis.com/home/item.html?id=a7412d0c33be4de698ad981c8ba471e6

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.

ArcGIS Server Service displays the Radiometric field map of the Czech Republic 1:500 000 (M. Manová, M. Matolín, 1995). This map was published by the Czech Geological Survey in the Atlas of map of Czech Republic (GEOCR500) in 1998. Data on the gamma dose rate of rocks are based on regional and detailed airborne measurement of terrestrial radiation. The data of the map illustrate the regional distribution of natural radionuclides in rocks and an above-average rock radioactivity in the Czech Republic.

ArcGIS Server Service displaying the Magnetic Map of the Czech Republic at a scale of 1 : 500,000 (K. Šalanský, 1995).

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.

This layer features tropical storm (hurricanes, typhoons, cyclones) tracks, positions, and observed wind swaths from the past hurricane season for the Atlantic, Pacific, and Indian Basins. These are products from the National Hurricane Center (NHC) and Joint Typhoon Warning Center (JTWC). They are part of an archive of tropical storm data maintained in the International Best Track Archive for Climate Stewardship (IBTrACS) database by the NOAA National Centers for Environmental Information.Data SourceNOAA National Hurricane Center tropical cyclone best track archive.Update FrequencyWe automatically check these products for updates every 15 minutes from the NHC GIS Data page.The NHC shapefiles are parsed using the Aggregated Live Feeds methodology to take the returned information and serve the data through ArcGIS Server as a map service.Area CoveredWorldWhat can you do with this layer?Customize the display of each attribute by using the ‘Change Style’ option for any layer.Run a filter to query the layer and display only specific types of storms or areas.Add to your map with other weather data layers to provide insight on hazardous weather events.Use ArcGIS Online analysis tools like ‘Enrich Data’ on the Observed Wind Swath layer to determine the impact of cyclone events on populations.Visualize data in ArcGIS Insights or Operations Dashboards.This map is provided for informational purposes and is not monitored 24/7 for accuracy and currency. Always refer to NOAA or JTWC sources for official guidance.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

This map contains a number of world-wide dynamic image services providing access to various Landsat scenes covering the landmass of the World for visual interpretation. Landsat 8 collects new scenes for each location on Earth every 16 days, assuming limited cloud coverage. Newest and near cloud-free scenes are displayed by default on top. Most scenes collected since 1st January 2015 are included. The service also includes scenes from the Global Land Survey* (circa 2010, 2005, 2000, 1990, 1975).The service contains a range of different predefined renderers for Multispectral, Panchromatic as well as Pansharpened scenes. The layers in the service can be time-enabled so that the applications can restrict the displayed scenes to a specific date range. This ArcGIS Server dynamic service can be used in Web Maps and ArcGIS Desktop, Web and Mobile applications using the REST based image services API. Users can also export images, but the exported area is limited to maximum of 2,000 columns x 2,000 rows per request.Data Source: The imagery in these services is sourced from the U.S. Geological Survey (USGS) and the National Aeronautics and Space Administration (NASA). The data for these services reside on the Landsat Public Datasets hosted on the Amazon Web Service cloud. Users can access full scenes from https://github.com/landsat-pds/landsat_ingestor/wiki/Accessing-Landsat-on-AWS, or alternatively access http://landsatlook.usgs.gov to review and download full scenes from the complete USGS archive.For more information on Landsat 8 images, see http://landsat.usgs.gov/landsat8.php.*The Global Land Survey includes images from Landsat 1 through Landsat 7. Band numbers and band combinations differ from those of Landsat 8, but have been mapped to the most appropriate band as in the above table. For more information about the Global Land Survey, visit http://landsat.usgs.gov/science_GLS.php.For more information on each of the individual layers, see http://www.arcgis.com/home/item.html?id=d9b466d6a9e647ce8d1dd5fe12eb434b ; http://www.arcgis.com/home/item.html?id=6b003010cbe64d5d8fd3ce00332593bf ; http://www.arcgis.com/home/item.html?id=a7412d0c33be4de698ad981c8ba471e6

This map service displays Level III and Level IV Ecoregions of the United States and was created from ecoregion data obtained from the U.S. Environmental Protection Agency Office of Research and Development's Western Ecology Division. The original ecoregion data was projected from Albers to Web Mercator for this map service. To download shapefiles of ecoregion data (in Albers), please go to: https://gaftp.epa.gov/EPADataCommons/ORD/Ecoregions/. IMPORTANT NOTE ABOUT LEVEL IV POLYGON LEGEND DISPLAY IN ARCMAP: Due to the limitations of Graphical Device Interface (GDI) resources per application on Windows, ArcMap does not display the legend in the Table of Contents for the ArcGIS Server service layer if the legend has more than 100 items. As of December 2011, there are 968 unique legend items in the Level IV Ecoregion Polygon legend. Follow this link (http://support.esri.com/en/knowledgebase/techarticles/detail/33741) for instructions about how to increase the maximum number of ArcGIS Server service layer legend items allowed for display in ArcMap. Note the instructions at this link provide a slightly incorrect path to "Maximum Legend Count". The correct path is HKEY_CURRENT_USER > Software > ESRI > ArcMap > Server > MapServerLayer > Maximum Legend Count. When editing the "Maximum Legend Count", update the field, "Value data" to 1000. To download a PDF version of the Level IV ecoregion map and legend, go to https://gaftp.epa.gov/EPADataCommons/ORD/Ecoregions/us/Eco_Level_IV_US_pg.pdf. Ecoregions denote areas of general similarity in ecosystems and in the type, quality, and quantity of environmental resources. They are designed to serve as a spatial framework for the research, assessment, management, and monitoring of ecosystems and ecosystem components. These general purpose regions are critical for structuring and implementing ecosystem management strategies across federal agencies, state agencies, and nongovernment organizations that are responsible for different types of resources within the same geographical areas. The approach used to compile this map is based on the premise that ecological regions can be identified through the analysis of patterns of biotic and abiotic phenomena, including geology, physiography, vegetation, climate, soils, land use, wildlife, and hydrology. The relative importance of each characteristic varies from one ecological region to another. A Roman numeral hierarchical scheme has been adopted for different levels for ecological regions. Level I is the coarsest level, dividing North America into 15 ecological regions. Level II divides the continent into 52 regions (Commission for Environmental Cooperation Working Group, 1997). At Level III, the continental United States contains 104 regions whereas the conterminous United States has 85 (U.S. Environmental Protection Agency, 2005). Level IV ecoregions (n = 968) are further subdivisions of Level III ecoregions. Methods used to define the ecoregions are explained in Omernik (1995, 2004), Omernik and others (2000), and Gallant and others (1989). Literature cited: Commission for Environmental Cooperation Working Group, 1997, Ecological regions of North America- toward a common perspective: Montreal, Commission for Environmental Cooperation, 71 p. Gallant, A.L., Whittier, T.R., Larsen, D.P., Omernik, J.M., and Hughes, R.M., 1989, Regionalization as a tool for managing environmental resources: Corvallis, Oregon, U.S. Environmental Protection Agency, EPA/600/3-89/060, 152p. Omernik, J.M., 1995, Ecoregions - a framework for environmental management, in Davis, W.S. and Simon, T.P., eds., Biological assessment and criteria-tools for water resource planning and decision making: Boca Raton, Florida, Lewis Publishers, p.49-62. Omernik, J.M., Chapman, S.S., Lillie, R.A., and Dumke, R.T., 2000, Ecoregions of Wisconsin: Transactions of the Wisconsin Academy of Science, Arts, and Letters, v. 88, p. 77-103. Omernik, J.M., 2004, Perspectives on the nature and definitions of ecological regions: Environmental Management, v. 34, Supplement 1, p. s27-s38. Comments and questions regarding ecoregion development should be addressed to Glenn Griffith, Dynamac Corporation, c/o US EPA., 200 SW 35th Street, Corvallis, OR 97333, 541-754-4465, email:griffith.glenn@epa.gov Alternate: James Omernik, USGS, c/o US EPA, 200 SW 35th Street, Corvallis, OR 97333, 541-754-4458, email:omernik.james@epa.gov

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.

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 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.

This map displays the wind forecast over the next 72 hours across the contiguous United States, in 3 hour increments, including wind direction, wind gust, and sustained wind speed.

Zoom in on the Map to refine the detail for a desired area. The Wind Gust is the maximum 3-second wind speed (in mph) forecast to occur within a 2-minute interval within a 3 hour period at a height of 10 meters Above Ground Level (AGL). The Wind Speed is the expected sustained wind speed (in mph) for the indicated 3 hour period at a height of 10 meters AGL. Data are updated hourly from the National Digital Forecast Database produced by the National Weather Service.

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 gridded forecasts 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).

Wind Speed Source: https://tgftp.nws.noaa.gov/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/AR.conus/VP.001-003/ds.wspd.bin

Wind Gust Source: https://tgftp.nws.noaa.gov/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/AR.conus/VP.001-003/ds.wgust.bin

Wind Direction Source: https://tgftp.nws.noaa.gov/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/AR.conus/VP.001-003/ds.wdir.bin

Where 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.

Alternate Symbology Feature Layer item that uses Vector Marker Symbols to render point arrows, easily altered by user. The color palette uses the Beaufort Scale for Wind Speed. https://www.arcgis.com/home/item.html?id=45cd2d4f5b9a4f299182c518ffa15977 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.

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

The ArcGIS Server map service displays hydrogeological documentation of maps that were processed during the solution of various types of projects in the CGS. Data on the chemical composition of groundwater and hydraulic properties of rocks are presented for selected archival wells. Descriptions, results of field measurements and photo documentation are available for individual hydrogeological objects documented in the field (eg springs).

This layer includes Landsat GLS multispectral imagery for use in visualization and analysis. This layer is time enabled and includes a number band combinations and indices rendered on demand. The layer includes Landsat 7 ETM+, Landsat 5 TM, and Landsat 4 imagery at 30m, and includes Landsat MSS imagery at 60m.Geographic CoverageWorld-wide imagery coverage.Temporal CoverageThis imagery layer includes data from epochs 2010, 2005, 2000, 1990 and 1975. Analysis ReadyThis imagery layer is analysis ready with Top of Atmosphere (TOA) correction applied.The TOA reflectance values (ranging 0 – 1 by default) are scaled using a range of 0 – 10,000.The scale is equivalent to other TOA reflectance products, including those provided by the USGS.Image Selection/FilteringNewer images are displayed by default on top.The entire archive is accessible via custom filtering.A number of fields are available for filtering, including Acquisition Date, Estimated Cloud Cover, and Product ID.By setting the filter to Best is lesser than QQQQ one can control to see the best N scenes, where QQQQ=N*1million.NOTE: Turning off all filters, and loading the entire archive, may affect performance.Visual RenderingDefault layer is Agriculture (bands 5,4,1) with Dynamic Range Adjustment (DRA). Brighter green indicates more vigorous vegetation.The DRA version of each layer enables visualization of the full dynamic range of the images.Rendering (or display) of band combinations and calculated indices is done on-the-fly from the source images via Raster Functions.Various pre-defined Raster Functions can be selected or custom functions can be created.Similar Imagery Layers are also available: Panchromatic and Pansharpened.Multispectral Bands

Band

Wavelength (µm)

Landsat 7 ETM+

Landsat 4-5 TM

Landsat MSS

1

0.45 – 0.52

0.45 – 0.52

N/A

2

0.52 – 0.60

0.52 – 0.60

0.5 – 0.6

3

0.63 – 0.69

0.63 – 0.69

0.6 – 0.7

4

0.77 – 0.90

0.76 – 0.90

0.7 – 0.8

5

1.55 – 1.75

1.55 – 1.75

0.8 – 1.1

6

2.09 – 2.35

2.08 – 2.35

N/A

Other Layer Usage Notes...Overviews exist with a spatial resolution of 300m and are updated weekly based on the best and latest imagery available at that time.To work with individual source images at all scales, either use the ‘Lock Raster’ functionality or add a query filter to restrict the display to a specified image or group of images.NOTE: ‘Lock Raster’ should only be used on the layer for short periods of time, as the imagery and associated record Object IDs may change daily.Images can be exported up to a maximum of 2,000 columns x 2,000 rows per request.This ArcGIS Server dynamic Imagery Layer can be used in Web Maps and ArcGIS Desktop as well as Web and Mobile applications using the REST based Image Services API.WCS and WMS compatibility means this imagery can be consumed as WCS or WMS services.Landsat Web App via Unlock Earth's Secrets.Data SourceLandsat imagery is sourced from the U.S. Geological Survey (USGS) and the National Aeronautics and Space Administration (NASA). Data is hosted by the Amazon Web Services as part of their Public Data Sets program. Users can access full scenes from Landsat on AWS, or alternatively access LandsatLook to review and download full scenes from the complete USGS archive.The Global Land Survey includes images from Landsat 1 through Landsat 7. Band numbers and band combinations differ from those of Landsat 8, but have been mapped to the most appropriate band as in the above table. For more information about the Global Land Survey, visit GLS.