Instructions on the Open Data Portal process for the Open Data Team.This is a step by step instructional document detailing the following processes:PUBLISH DATA TO ARCGIS SERVER MANAGE WEB LAYERS IN PORTAL CREATE FEATURE LAYER IN ARCGIS ONLINEHOW TO ADD DOCUMENTS AND FILESSHARE STATIC FILES THROUGH THE COLLABORATIONCHANGE ITEMS OWNER TO OPEN_DATA_ADMIN

Deprecation notice: This tool is deprecated because this functionality is now available with out-of-the-box tools in ArcGIS Pro. The tool author will no longer be making further enhancements or fixing major bugs.Use Add GTFS to a Network Dataset to incorporate transit data into a network dataset so you can perform schedule-aware analyses using the Network Analyst tools in ArcMap.After creating your network dataset, you can use the ArcGIS Network Analyst tools, like Service Area and OD Cost Matrix, to perform transit/pedestrian accessibility analyses, make decisions about where to locate new facilities, find populations underserved by transit or particular types of facilities, or visualize the areas reachable from your business at different times of day. You can also publish services in ArcGIS Server that use your network dataset.The Add GTFS to a Network Dataset tool suite consists of a toolbox to pre-process the GTFS data to prepare it for use in the network dataset and a custom GTFS transit evaluator you must install that helps the network dataset read the GTFS schedules. A user's guide is included to help you set up your network dataset and run analyses.Instructions:Download the tool. It will be a zip file.Unzip the file and put it in a permanent location on your machine where you won't lose it. Do not save the unzipped tool folder on a network drive, the Desktop, or any other special reserved Windows folders (like C:\Program Files) because this could cause problems later.The unzipped file contains an installer, AddGTFStoaNetworkDataset_Installer.exe. Double-click this to run it. The installation should proceed quickly, and it should say "Completed" when finished.Read the User's Guide for instructions on creating and using your network dataset.System requirements:ArcMap 10.1 or higher with a Desktop Standard (ArcEditor) license. (You can still use it if you have a Desktop Basic license, but you will have to find an alternate method for one of the pre-processing tools.) ArcMap 10.6 or higher is recommended because you will be able to construct your network dataset much more easily using a template rather than having to do it manually step by step. This tool does not work in ArcGIS Pro. See the User's Guide for more information.Network Analyst extensionThe necessary permissions to install something on your computer.Data requirements:Street data for the area covered by your transit system, preferably data including pedestrian attributes. If you need help preparing high-quality street data for your network, please review this tutorial.A valid GTFS dataset. If your GTFS dataset has blank values for arrival_time and departure_time in stop_times.txt, you will not be able to run this tool. You can download and use the Interpolate Blank Stop Times tool to estimate blank arrival_time and departure_time values for your dataset if you still want to use it.Help forum

NOTE: An updated Introduction to ArcGIS GeoEvent Server Tutorial is available here. It is recommended you use the new tutorial for getting started with GeoEvent Server. The old Introduction Tutorial available on this page is relevant for 10.8.x and earlier and will not be updated.The Introduction to GeoEvent Server Tutorial (10.8.x and earlier) introduces you to the Real-Time Visualization and Analytic capabilities of ArcGIS GeoEvent Server. GeoEvent Server allows you to:

Incorporate real-time data feeds in your existing GIS data and IT infrastructure. Perform continuous processing and analysis on streaming data, as it is received. Produce new streams of data that can be leveraged across the ArcGIS system.

Once you have completed the exercises in this tutorial you should be able to:

Use ArcGIS GeoEvent Manager to monitor and perform administrative tasks. Create and maintain GeoEvent Service elements such as inputs, outputs, and processors. Use GeoEvent Simulator to simulate event data into GeoEvent Server. Configure GeoEvent Services to append and update features in a published feature service. Work with processors and filters to enhance and direct GeoEvents from event data.

The knowledge gained from this tutorial will prepare you for other GeoEvent Server tutorials available in the ArcGIS GeoEvent Server Gallery.

Releases

Each release contains a tutorial compatible with the version of GeoEvent Server listed. The release of the component you deploy does not have to match your version of ArcGIS GeoEvent Server, so long as the release of the component is compatible with the version of GeoEvent Server you are using. For example, if the release contains a tutorial for version 10.6; this tutorial is compatible with ArcGIS GeoEvent Server 10.6 and later. Each release contains a Release History document with a compatibility table that illustrates which versions of ArcGIS GeoEvent Server the component is compatible with.

NOTE: The release strategy for ArcGIS GeoEvent Server components delivered in the ArcGIS GeoEvent Server Gallery has been updated. Going forward, a new release will only be created when

  a component has an issue,
  is being enhanced with new capabilities,
  or is not compatible with newer versions of ArcGIS GeoEvent Server.

This strategy makes upgrades of these custom
components easier since you will not have to
upgrade them for every version of ArcGIS GeoEvent Server
unless there is a new release of
the component. The documentation for the
latest release has been
updated and includes instructions for updating
your configuration to align with this strategy.

Latest

Release 7 - March 30, 2018 - Compatible with ArcGIS GeoEvent Server 10.6 and later.

Previous

Release 6 - January 12, 2018 - Compatible with ArcGIS GeoEvent Server 10.5 thru 10.8.

Release 5 - July 30, 2016 - Compatible with ArcGIS GeoEvent Server 10.4 thru 10.8.

Release 4 - July 30, 2015 - Compatible with ArcGIS GeoEvent Server 10.3.x.

Release 3 - April 24, 2015 - Compatible with ArcGIS GeoEvent Server 10.3.x. Not available.

Release 2 - January 22, 2015 - Compatible with ArcGIS GeoEvent Server 10.3.x. Not available.

Release 1 - April 11, 2014 - Compatible with ArcGIS GeoEvent Server 10.2.x.

The Spatiotemporal Big Data Store Tutorial introduces you the the capabilities of the spatiotemporal big data store in ArcGIS Data Store, available with ArcGIS Enterprise. Observation data can be moving objects, changing attributes of stationary sensors, or both. The spatiotemporal big data store enables archival of high volume observation data, sustains high velocity write throughput, and can run across multiple machines (nodes). Adding additional machines adds capacity, enabling you to store more data, implement longer retention policies of your data, and support higher data write throughput.

After completing this tutorial you will:

Understand the concepts and best practices for working with the spatiotemporal big data store available with ArcGIS Data Store. Have configured the appropriate security settings and certificates on a enterprise server, real-time server, and a data server which are necessary for working with the spatiotemporal big data store. Have learned how to process and archive large amounts of observational data in the spatiotemporal big data store. Have learned how to visualize the observational data that is stored in the spatiotemporal big data store.

Releases

Each release contains a tutorial compatible with the version of GeoEvent Server listed. The release of the component you deploy does not have to match your version of ArcGIS GeoEvent Server, so long as the release of the component is compatible with the version of GeoEvent Server you are using. For example, if the release contains a tutorial for version 10.6; this tutorial is compatible with ArcGIS GeoEvent Server 10.6 and later. Each release contains a Release History document with a compatibility table that illustrates which versions of ArcGIS GeoEvent Server the component is compatible with.

NOTE: The release strategy for ArcGIS GeoEvent Server components delivered in the ArcGIS GeoEvent Server Gallery has been updated. Going forward, a new release will only be created when

  a component has an issue,
  is being enhanced with new capabilities,
  or is not compatible with newer versions of ArcGIS GeoEvent Server.

This strategy makes upgrades of these custom
components easier since you will not have to
upgrade them for every version of ArcGIS GeoEvent Server
unless there is a new release of
the component. The documentation for the
latest release has been
updated and includes instructions for updating
your configuration to align with this strategy.

Latest

Release 4 - February 2, 2017 - Compatible with ArcGIS GeoEvent Server 10.5 and later.

Previous

Release 3 - July 7, 2016 - Compatible with ArcGIS GeoEvent Server 10.4 thru 10.8.

Release 2 - May 17, 2016 - Compatible with ArcGIS GeoEvent Server 10.4 thru 10.8.

Release 1 - March 18, 2016 - Compatible with ArcGIS GeoEvent Server 10.4 thru 10.8.

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.

IMPORTANT information regarding proper legend rendering 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 ftp://ftp.epa.gov/wed/ecoregions/us/Eco_Level_IV_US_pg.pdf. Please read the remainder of this layer description for general information about Level IV Omernik Ecoregions. This layer represents Level IV Omernik Ecoregions. Ecoregions denote areas of general similarity in ecosystems and in the type, quality, and quantity of environmental resources. Compilation of the level IV maps, performed at 1:250,000 scale, has been a part of collaborative projects between US Environmental Protection Agency, National Health and Environmental Effects Laboratory (NHEERL)--Corvallis, OR, the US Forest Service, Natural Resources Conservation Service, and a variety of other state and federal resource agencies. The ecoregions and subregions are designed to serve as a spatial framework for environmental resource management. The most immediate needs by the states are for developing regional biological criteria and water resource standards, and for setting management goals for nonpoint-source pollution. Level IV ecoregions are intended for large geographic extents (i.e. states, multiple counties, or river basins). Use for smaller areas, such as individual counties or a 1:24,000 scale map boundary, is not recommended. Explanation of the methods used to delineate the ecoregions are given in Omernik (1995), Griffith et al. (1994), and Gallant et al. (1989). For more information about Omernik ecoregions or to download ecoregion maps and GIS data, go to: http://www.epa.gov/wed/pages/ecoregions.htm.

This web service layer group contains multiple layers at various scale dependencies which enhances the cartographic display of ecoregion data. Each layer depicts ecoregion features drawn at specific scales as detailed in the layer name. IMPORTANT information regarding proper legend rendering 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 (https://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 ftp://ftp.epa.gov/wed/ecoregions/us/Eco_Level_IV_US_pg.pdf. Please read the remainder of this layer description for general information about Level IV Omernik Ecoregions. This layer represents Level IV Omernik Ecoregions. Ecoregions denote areas of general similarity in ecosystems and in the type, quality, and quantity of environmental resources. Compilation of the level IV maps, performed at 1:250,000 scale, has been a part of collaborative projects between US Environmental Protection Agency, National Health and Environmental Effects Laboratory (NHEERL)--Corvallis, OR, the US Forest Service, Natural Resources Conservation Service, and a variety of other state and federal resource agencies. The ecoregions and subregions are designed to serve as a spatial framework for environmental resource management. The most immediate needs by the states are for developing regional biological criteria and water resource standards, and for setting management goals for nonpoint-source pollution. Level IV ecoregions are intended for large geographic extents (i.e. states, multiple counties, or river basins). Use for smaller areas, such as individual counties or a 1:24,000 scale map boundary, is not recommended. Explanation of the methods used to delineate the ecoregions are given in Omernik (1995), Griffith et al. (1994), and Gallant et al. (1989). For more information about Omernik ecoregions or to download ecoregion maps and GIS data, go to: https://www.epa.gov/wed/pages/ecoregions.htm.

This document explains Virginia Geographic Information Network (VGIN) map and feature services and how to work with them in ArcGIS Desktop and ArcGIS Pro. Instructions cover connecting to the server, adding services to a map, and extracting data from feature services. Particular focus is on the provisioning and PSAP boundary polygons used in NG9-1-1 deployment. The steps listed also apply to other VGIN feature services and publicly-facing or shared feature services from other sources.Feature services are supported in ArcGIS Pro. ArcMap support started in version 10.1. If you are working with a version of ArcGIS Desktop 10.0 or older, please contact us at NG911GIS@vdem.virginia.gov for support.Document updated October 2022 to reflect changes to https://vgin.vdem.virginia.gov/Additional resources and recommendations on GIS related topics are available on the VGIN 9-1-1 & GIS page.

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://dmap-prod-oms-edc.s3.us-east-1.amazonaws.com/index.html#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://dmap-prod-oms-edc.s3.us-east-1.amazonaws.com/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

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.

Map Information

The nowCOAST time-enabled map service provides maps depicting the geographic coverage of the latest NOAA/National Weather Service (NWS) WARNINGS for short-duration hazards for inland, coastal, and maritime areas which are in progress, imminent, or has a very high probability of occurring. These hazards include severe thunderstorms (damaging winds, large hail), tornadoes, waterspouts, flash floods, and extreme winds associated with major land-falling hurricanes.
Specifically, the layer includes the following warnings: Special Marine Warnings (winds of 34 knots, 3/4 inch diameter hail, waterspouts), Severe Thunderstorm Warnings (winds of 58 MPH or greater, large hail of 1 inch or greater in diameter), Tornado Warnings, Flash Flood Warnings, and Extreme Wind Warnings (sustained surface winds of 115 MPH or greater during major [Category 3 or higher]land-falling hurricane within one hour). The colors used to identify the different warnings are the same colors used by the NWS on their map at weather.gov.
The map is updated in the nowCOAST map service every minute. For more detailed information about the update schedule, please see: http://new.nowcoast.noaa.gov/help/#section=updateschedule

Background Information

The NWS threat-based polygon or storm-based warnings are issued by NWS Weather Forecast Offices to depict the type of short-duration weather or hydrological hazard which is in progress, imminent or has a very high probability of occurring for a specified geographic area. For Severe Thunderstorm, Tornado, Flash Flood and Extreme Wind Warnings, the warnings are not restricted to geopolitical boundaries. However, Special Marine Warnings are issued for marine areas such as bays, harbors, sounds and coastal waters along the U.S. coastline out to the NWS Offshore marine forecast zone. For Guam and Pago Pago, American Samoa, the coastal waters extend out to the the NWS High Seas marine forecast zone.

Time Information

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

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.

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

Due to software limitations, the time extent of the service and map layers displayed below does not provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time information about the service:

Issue a returnUpdates=true request 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
this 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 reffered 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 help documentation at:
  http://new.nowcoast.noaa.gov/help/#section=layerinfo

References

NWS, 2003: NWS Product Description Document for Special Marine Warning, NWS, Silver Spring, MD. NWS, 2005: NWS Instructions 10-511, WFO Severe Weather Products Specification, NWS, Silver Spring, MD. NWS, 2007: NWS Instructions 10-922, Weather Forecast Office Hydrologic Products Specifications, NWS, Silver Spring, MD. NWS, 2014: Extreme Wind Warning Product (http://www.nws.noaa.gov/os/hurricane/eww.shtml).

NWS Instructions and other directives are available at http://www.nws.noaa.gov/directives/.

Sentinel-2, 10, 20, and 60m Multispectral, Multitemporal, 13-band imagery is rendered on-the-fly and available for visualization. This imagery layer pulls directly from the Sentinel-2 on AWS collection and is updated daily with new imagery.This imagery layer can be applied across a number of industries, scientific disciplines, and management practices. Some applications include, but are not limited to, land cover and environmental monitoring, climate change, deforestation, disaster and emergency management, national security, plant health and precision agriculture, forest monitoring, watershed analysis and runoff predictions, land-use planning, tracking urban expansion, highlighting burned areas and estimating fire severity.Geographic CoverageGlobalContinental land masses from 65.4° South to 72.1° North, with these special guidelines:All coastal waters up to 20 km from the shoreAll islands greater than 100 km2All EU islandsAll closed seas (e.g. Caspian Sea)The Mediterranean SeaTemporal CoverageThe revisit time for each point on Earth is every 5 days.This layer is updated daily with new imagery.This imagery layer includes a rolling collection of imagery acquired within the past 14 months.The number of images available will vary depending on location.Product LevelThis service provides Level-1C Top of Atmosphere imagery.Alternatively, Sentinel-2 Level-2A is also available.Image Selection/FilteringThe most recent and cloud free images are displayed by default.Any image available within the past 14 months can be displayed via custom filtering.Filtering can be done based on attributes such as Acquisition Date, Estimated Cloud Cover, and Tile ID.Tile_ID is computed as [year][month][day]T[hours][minutes][seconds]_[UTMcode][latitudeband][square]_[sequence]. More…Visual RenderingDefault rendering is Natural Color (bands 4,3,2) with Dynamic Range Adjustment (DRA).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 created.Available renderings include: Agriculture with DRA, Bathymetric with DRA, Color-Infrared with DRA, Natural Color with DRA, Short-wave Infrared with DRA, Geology with DRA, NDMI Colorized, Normalized Difference Built-Up Index (NDBI), NDWI Raw, NDWI - with VRE Raw, NDVI – with VRE Raw (NDRE), NDVI - VRE only Raw, NDVI Raw, Normalized Burn Ratio, NDVI Colormap.Multispectral BandsBandDescriptionWavelength (µm)Resolution (m)1Coastal aerosol0.433 - 0.453602Blue0.458 - 0.523103Green0.543 - 0.578104Red0.650 - 0.680105Vegetation Red Edge0.698 - 0.713206Vegetation Red Edge0.733 - 0.748207Vegetation Red Edge0.773 - 0.793208NIR0.785 - 0.900108ANarrow NIR0.855 - 0.875209Water vapour0.935 - 0.9556010SWIR – Cirrus1.365 - 1.3856011SWIR-11.565 - 1.6552012SWIR-22.100 - 2.28020Additional NotesOverviews exist with a spatial resolution of 150m and are updated every quarter based on the best and latest imagery available at that time.To work with source images at all scales, the ‘Lock Raster’ functionality is available.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.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.Images can be exported up to a maximum of 4,000 columns x 4,000 rows per request.Data SourceSentinel-2 imagery is the result of close collaboration between the (European Space Agency) ESA, the European Commission and USGS. Data is hosted by the Amazon Web Services as part of their Registry of Open Data. Users can access the imagery from Sentinel-2 on AWS , or alternatively access EarthExplorer or the Copernicus Data Space Ecosystem to download the scenes.For information on Sentinel-2 imagery, see Sentinel-2.

The establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making.

   BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions.


   Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself.


   For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise.


   Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer. 


   This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery.


   See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt


   See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt

Map Information

This nowCOAST time-enabled map service provides maps depicting the geographic coverage of the latest NOAA/National Weather Service (NWS) WATCHES for the following short-duration hazardous weather and hydrological events which may affect inland and coastal areas: severe thunderstorms (surface winds of 58 MPH (93 KM/H, 50 knots) or greater, large hail of 1 inch (2.5 cm) or greater in diameter, tornadoes, and flash floods. A watch indicates that the risk of hazardous weather or hydrologic event has increased significantly, but its occurrence, location, and/or timing is still uncertain. The geographic areas covered by Severe Thunderstorm, Tornado, and Flash Flood Watches are usually indicated by county or subdivided-county boundaries. The colors used to identify the different watches are the same colors used by the NWS on their map at weather.gov. The NWS watches are updated in the nowCOAST map service approximately every 10 minutes. For more detailed information about the update schedule, please see: http://new.nowcoast.noaa.gov/help/#section=updateschedule

Background Information

The NWS watches depict the geographic areas where the risk of hazardous weather or hydrologic events has increased significantly, but their occurrence, location, and/or timing is still uncertain. The watch is intended to give enough lead time so people can set their plans into motion. NWS Severe Thunderstorm and Tornado Watches are issued by the NWS/NCEP Storm Prediction Center in Oklahoma. Flash Flood Watches are issued by the NWS regional Weather Forecast Offices (WFO). All watches are cancelled by WFOs.

Time Information

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

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.

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

Due to software limitations, the time extent of the service and map layers displayed below does not provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time information about the service:

Issue a returnUpdates=true request 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
this 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 reffered 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 help documentation at:
  http://new.nowcoast.noaa.gov/help/#section=layerinfo

References

NWS, 2006: NWS Instructions 10-313, WFO Severe Weather Products Specification, NWS, Silver Spring, MD. NWS, 2007: NWS Instructions 10-922, Weather Forecast Office Hydrologic Products Specification, NWS, Silver Spring, MD. NWS, 2010: NWS Instructions 10-512, National Severe Weather Products Specification, NWS, Silver Spring, MD.

NWS Instructions and other directives are available at http://www.nws.noaa.gov/directives/.

Swimming pools are important for property tax assessment because they impact the value of the property. Tax assessors at local government agencies often rely on expensive and infrequent surveys, leading to assessment inaccuracies. Finding pools that are not on the assessment roll (such as those recently constructed) is valuable to assessors and will ultimately mean additional revenue for the community.This deep learning model helps automate the task of finding pools from high resolution satellite imagery. This model can also benefit swimming pool maintenance companies and help redirect their marketing efforts. Public health and mosquito control agencies can also use this model to detect pools and drive field activity and mitigation efforts.Licensing requirementsArcGIS Desktop – ArcGIS Image Analyst extension for ArcGIS ProArcGIS Enterprise – ArcGIS Image Server with raster analytics configuredArcGIS Online – ArcGIS Image for ArcGIS OnlineUsing the modelFollow the guide to use the model. Before using this model, ensure that the supported deep learning libraries are installed. For more details, check Deep Learning Libraries Installer for ArcGIS.Note: Deep learning is computationally intensive, and a powerful GPU is recommended to process large datasets.Input8-bit, 3-band high resolution (5-7.5 centimeters) imageryOutputFeature class containing bounding boxes depicting pool locations with class BuiltinPool | PopupPoolApplicable geographiesThe model is expected to work well in the New Zealand.Model architectureThe model uses the MMDetection model architecture implemented using ArcGIS Pro Arcpy.Accuracy metricsThe model has an average precision score of 0.95.1 BuiltInPool2PopupPoolSample resultsHere are a few results from the model.(Post processing are recommended to filter out False Positive Object. If the confidence are below certain threshold e.g 5%)To learn how to use this model, see this story

Sentinel-2, 10 and 20m Multispectral 13-band imagery, rendered on-the-fly. Available for visualization and analytics, this Imagery Layer pulls directly from the Sentinel-2 on AWS collection and is updated daily with new imagery.This imagery layer can be used for multiple purposes including but not limited to vegetation, land cover and environmental monitoring.Geographic CoverageGlobalContinental land masses from 65.4° South to 72.1° North, with these special guidelines:All coastal waters up to 20 km from the shoreAll islands greater than 100 km2All EU islandsAll closed seas (e.g. Caspian Sea)The Mediterranean SeaNote: Areas of interest going beyond the Mission baseline (as laid out in the Mission Requirements Document) will be assessed, and may be added to the baseline if sufficient resources are identified.Temporal CoverageThe revisit time for each point on Earth is every 5 days.This layer is updated daily with new imagery.This imagery layer is designed to include imagery collected within the past 14 months. Custom Image Services can be created for access to images older than 14 months.The number of images available will vary depending on location.Image Selection/FilteringThe most recent and cloud free image, for any location, is displayed by default.Any image available, within the past 14 months, can be displayed via custom filtering.Filtering can be done based on Acquisition Date, Estimated Cloud Cover, and Tile ID.Tile_ID is computed as [year][month][day]T[hours][minutes][seconds]_[UTMcode][latitudeband][square]_[sequence]. More…NOTE: Not using filters, and loading the entire archive, may affect performance.Analysis ReadyThis imagery layer is analysis ready with TOA correction applied.Visual RenderingDefault rendering is NDMI Colorized (Normalized Difference Moisture Index with colormap) computed as NIR(B8)-SWIR1(B11)/NIR(B8)+SWIR1(B11)Wetlands and moist areas appear blue whereas dry areas are represented by deep yellow and brown color.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 created.Available renderings include: Agriculture with DRA, Bathymetric with DRA, Color-Infrared with DRA, Natural Color with DRA, Short-wave Infrared with DRA, Geology with DRA, Normalized Difference Built-Up Index (NDBI), NDWI Raw, NDWI - with VRE Raw, NDVI – with VRE Raw (NDRE), NDVI - VRE only Raw, NDVI Raw, Normalized Burn Ratio, NDVI Colormap.Multispectral BandsBandDescriptionWavelength (µm)Resolution (m)1Coastal aerosol0.433 - 0.453602Blue0.458 - 0.523103Green0.543 - 0.578104Red0.650 - 0.680105Vegetation Red Edge0.698 - 0.713206Vegetation Red Edge0.733 - 0.748207Vegetation Red Edge0.773 - 0.793208NIR0.785 - 0.900108ANarrow NIR0.855 - 0.875209Water vapour0.935 - 0.9556010SWIR – Cirrus1.365 - 1.3856011SWIR-11.565 - 1.6552012SWIR-22.100 - 2.28020Additional NotesOverviews exist with a spatial resolution of 150m and are updated every quarter based on the best and latest imagery available at that time.To work with source images at all scales, the ‘Lock Raster’ functionality is available.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.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.Images can be exported up to a maximum of 4,000 columns x 4,000 rows per request.Data SourceSentinel-2 imagery is the result of close collaboration between the (European Space Agency) ESA, the European Commission and USGS. Data is hosted by the Amazon Web Services as part of their Registry of Open Data. Users can access the imagery from Sentinel-2 on AWS , or alternatively access Sentinel2Look Viewer, EarthExplorer or the Copernicus Open Access Hub to download the scenes.For information on Sentinel-2 imagery, see Sentinel-2.

This data table shows COVID-19 vaccination rates by race and ethnicity in Maricopa County zip codes.Data Source: Maricopa County GIS Open Data weekly count of COVID-19 vaccinations. The data were reformatted from the source data to accommodate dashboard configuration. Dates: Updated data shows publishing dates which represents values from the previous calendar week (Sunday through Saturday). For more details on data reporting, please see the Maricopa County COVID-19 data reporting notes at https://www.maricopa.gov/5460/Coronavirus-Disease-2019.The Maricopa County Department of Public Health (MCDPH) releases the COVID-19 vaccination rate per 100,000 of the vaccine eligible population and COVID-19 vaccination rate per 100,000 of the total population for each zip code and city in Maricopa County at ~12:00 PM weekly on Wednesdays via the Maricopa County GIS Open Data website (https://data-maricopa.opendata.arcgis.com/). More information about the data is available on the Maricopa County COVID-19 Vaccine Data page (https://www.maricopa.gov/5671/Public-Vaccine-Data#dashboard).Additional InformationSource: Maricopa County Department of Public Health (MCDPH) through Maricopa County GIS Open Data weekly count of COVID-19 vaccinationsContact (author): n/aContact E-Mail (author): n/aContact (maintainer): City of Tempe Open Data TeamContact E-Mail (maintainer): data@tempe.govData Source Type: TablePreparation Method: Data are exposed via ArcGIS Server and its REST API.Publish Frequency: WeeklyPublish Method: Data are downloaded each week once Maricopa County GIS Open Data updates its public API. Data are transformed and appended to a table in Tempe’s Enterprise GIS.Data Dictionary

The Provincial Digital Elevation Model (PDEM) is a general purpose dataset designed to represent true ground elevation where possible and is based on best-available data across the province. This dataset has not been conditioned for any specific application. Please see the User Guide below for more information.Zoom in on the map and click your area of interest to determine which package(s) you require for download.Now also available through a web service which exposes the data forvisualization and geoprocessing.The service is best accessed through the ArcGIS REST API, either directly or by setting up an ArcGIS server connection using the REST endpoint URL. The service draws using the 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 Land Information Ontario (LIO) at lio@ontario.ca.Service Endpointshttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/Elevation/Ontario_Provincial_Digital_Elevation_Model/ImageServerhttps://intra.ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/Elevation/Ontario_Provincial_Digital_Elevation_Model/ImageServer (Government of Ontario Internal Users)Additional DocumentationProvincial Digital Elevation Model - User Guide (Word)Provincial Digital Elevation Model - Methods and Processes (Word)Updating Provincial Elevation Data Using Least Cost Path Analysis (Word)Provincial Digital Elevation Model - Boundary in shape file format (Shapefile)OBM Photo Block Index (Zip file)PDEM Spatial Metadata Index (Elevation Source) - October 3rd, 2023 (Zip file)Product PackagesProvincial Digital Elevation Model -North (CGVD28)Provincial Digital Elevation Model - South (CGVD28)Provincial Digital Elevation Model - North (CGVD2013)Provincial Digital Elevation Model - South (CGVD2013)StatusOn going: Data is continually being updatedMaintenance and Update FrequencyAs needed: Data is updated as deemed necessaryRSS FeedFollow our feed to get the latest announcements and developments concerning our PDEM product. Visit our feed at the bottom of our ArcGIS Online PDEM page.ContactOntario Ministry of Natural Resources - Geospatial Ontario, geospatial@ontario.ca

Sentinel-2 Level-1C imagery with on-the-fly renderings for visualization. This imagery layer pulls directly from theSentinel-2 on AWScollection and is updated daily with new imagery.Sentinel-2 imagery can be applied across a number of industries, scientific disciplines, and management practices. Some applications include, but are not limited to, land cover and environmental monitoring, climate change, deforestation, disaster and emergency management, national security, plant health and precision agriculture, forest monitoring, watershed analysis and runoff predictions, land-use planning, tracking urban expansion, highlighting burned areas and estimating fire severity. Geographic Coverage GlobalContinental land masses from65.4° South to 72.1° North, with these special guidelines:All coastal waters up to 20 km from the shoreAll islands greater than 100 km2All EU islandsAll closed seas (e.g. Caspian Sea)The Mediterranean Sea Temporal Coverage This layer includes a rolling collection of Sentinel-2 imagery acquired within the past 14 months. This layer is updated daily with new imagery. The revisit time for each point on Earth is every 5 days. The number of images available will vary depending on location. Product Level This service provides Level-1C Top of Atmosphere imagery.Alternatively,Sentinel-2 Level-2A is also available. Image Selection/Filtering The most recent and cloud free images are displayed by default. Any image available within the past 14 months can be displayed via custom filtering. Filtering can be done based on attributes such as Acquisition Date, Estimated Cloud Cover, and Tile ID. Tile_ID is computed as [year][month][day]T[hours][minutes][seconds]_[UTMcode][latitudeband][square]_[sequence].More… Visual Rendering Default rendering is Natural Color (bands 4,3,2) with Dynamic Range Adjustment (DRA). 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 created. Available renderings include: Agriculture with DRA,Bathymetric with DRA,Color-Infrared with DRA,Natural Color with DRA,Short-wave Infrared with DRA,Geology with DRA,NDMI Colorized,Normalized Difference Built-Up Index (NDBI),NDWI Raw,NDWI - with VRE Raw,NDVI – with VRE Raw (NDRE),NDVI - VRE only Raw,NDVI Raw,Normalized Burn Ratio,NDVI Colormap. Multispectral Bands BandDescriptionWavelength (µm)Resolution (m)1Coastal aerosol0.433 - 0.453602Blue0.458 - 0.523103Green0.543 - 0.578104Red0.650 - 0.680105Vegetation Red Edge0.698 - 0.713206Vegetation Red Edge0.733 - 0.748207Vegetation Red Edge0.773 - 0.793208NIR0.785 - 0.900108ANarrow NIR0.855 - 0.875209Water vapour0.935 - 0.9556010SWIR – Cirrus1.365 - 1.3856011SWIR-11.565 - 1.6552012SWIR-22.100 - 2.28020Additional Notes Overviews exist with a spatial resolution of 150m and are updated every quarter based on the best and latest imagery available at that time.To work with source images at all scales, the ‘Lock Raster’ functionality is available. 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.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.Images can be exported up to a maximum of 4,000 columns x 4,000 rows per request.Data SourceSentinel-2 imagery is the result of close collaboration between the (European Space Agency) ESA, the European Commission and USGS. Data is hosted by the Amazon Web Services as part of theirRegistry of Open Data. Users can access the imagery fromSentinel-2 on AWS, or alternatively accessEarthExploreror theCopernicus Data Space Ecosystemto download the scenes.For information on Sentinel-2 imagery, seeSentinel-2.