GoalsSymbolize dense point features.Add and label reference data.Configure a layout for print maps.

Contents: This is an ArcGIS Pro zip file that you can download and use for creating map books based on United States National Grid (USNG). It contains a geodatabase, layouts, and tasks designed to teach you how to create a basic map book.Version 1.0.0 Uploaded on May 24th and created with ArcGIS Pro 2.1.3 - Please see the README below before getting started!Updated to 1.1.0 on August 20thUpdated to 1.2.0 on September 7thUpdated to 2.0.0 on October 12thUpdate to 2.1.0 on December 29thBack to 1.2.0 due to breaking changes in the templateBack to 1.0.0 due to breaking changes in the template as of June 11th 2019Updated to 2.1.1 on October 8th 2019Audience: GIS Professionals and new users of ArcGIS Pro who support Public Safety agencies with map books. If you are looking for apps that can be used by any public safety professional, see the USNG Lookup Viewer.Purpose: To teach you how to make a map book with critical infrastructure and a basemap, based on USNG. You NEED to follow the steps in the task and not try to take shortcuts the first time you use this task in order to receive the full benefits. Background: This ArcGIS Pro template is meant to be a starting point for your map book projects and is based on best practices by the USNG National Implementation Center (TUNIC) at Delta State University and is hosted by the NAPSG Foundation. This does not replace previous templates created in ArcMap, but is a new experimental approach to making map books. We will continue to refine this template and work with other organizations to make improvements over time. So please send us your feedback admin@publicsafetygis.org and comments below. Instructions: Download the zip file by clicking on the thumbnail or the Download button.Unzip the file to an appropriate location on your computer (C:\Users\YourUsername\Documents\ArcGIS\Projects is a common location for ArcGIS Pro Projects).Open the USNG Map book Project File (APRX).If the Task is not already open by default, navigate to Catalog > Tasks > and open 'Create a US National Grid Map Book' Follow the instructions! This task will have some automated processes and models that run in the background but you should pay close attention to the instructions so you also learn all of the steps. This will allow you to innovate and customize the template for your own use.FAQsWhat is US National Grid? The US National Grid (USNG) is a point and area reference system that provides for actionable location information in a uniform format. Its use helps achieve consistent situational awareness across all levels of government, disciplines, and threats & hazards – regardless of your role in an incident.One of the key resources NAPSG makes available to support emergency responders is a basic USNG situational awareness application. See the NAPSG Foundation and USNG Center websites for more information.What is an ArcGIS Pro Task? A task is a set of preconfigured steps that guide you and others through a workflow or business process. A task can be used to implement a best-practice workflow, improve the efficiency of a workflow, or create a series of interactive tutorial steps. See "What is a Task?" for more information.Do I need to be proficient in ArcGIS Pro to use this template? We feel that this is a good starting point if you have already taken the ArcGIS Pro QuickStart Tutorials. While the task will automate many steps, you will want to get comfortable with the map layouts and other new features in ArcGIS Pro.Is this template free? This resources is provided at no-cost, but also with no guarantees of quality assurance or support at this time. Can't I just use ArcMap? Ok - here you go. USNG 1:24K Map Template for ArcMapKnown Limitations and BugsZoom To: It appears there may be a bug or limitation with automatically zooming the map to the proper extent, so get comfortable with navigation or zoom to feature via the attribute table.FGDC Compliance: We are seeking feedback from experts in the field to make sure that this meets minimum requirements. At this point in time we do not claim to have any official endorsement of standardization. File Size: Highly detailed basemaps can really add up and contribute to your overall file size, especially over a large area / many pages. Consider making a simple "Basemap" of street centerlines and building footprints.We will do the best we can to address limitations and are very open to feedback!

This resource contains the test data for the GeoServer OGC Web Services tutorials for various GIS applications including ArcGIS Pro, ArcMap, ArcGIS Story Maps, and QGIS. The contents of the data include a polygon shapefile, a polyline shapefile, a point shapefile, and a raster dataset; all of which pertain to the state of Utah, USA. The polygon shapefile is of every county in the state of Utah. The polyline is of every trail in the state of Utah. The point shapefile is the current list of GNIS place names in the state of Utah. The raster dataset covers a region in the center of the state of Utah. All datasets are projected to NAD 1983 Zone 12N.

Please note, the updated version of this toolbox is now available for download on this page. The COVID-19-Modeling-v1.zip file contains version 5 of the toolbox with updated documentation. Version 5 of the toolbox updates the CHIME Model v1.1.5 tool. The COVID-19Surge (CDC) model is unchanged in this version.More information about the toolbox can be found in the toolbox document. More information about the CHIME Model v1.1.5 tool, including the change log, can be found in the tool documentation and this video.More information about the COVID-19Surge (CDC) tool is included in the tool documentation and this video. CHIME Model v1.1.5 ToolVersion 4 - Updated 11 MAY 2020An implementation of Penn Medicine’s COVID-19 Hospital Impact Model for Epidemics (CHIME) for use in ArcGIS Pro 2.3 or later. This tool leverages SIR (Susceptible, Infected, Recovered) modeling to assist hospitals, cities, and regions with capacity planning around COVID-19 by providing estimates of daily new admissions and current inpatient hospitalizations (census), ICU admissions, and patients requiring ventilation. Version 4 of this tool is based on CHIME v1.1.5 (2020-05-07). Learn more about how CHIME works.Version 4 contains the following updates:Updated the CHIME tool from CHIME v1.1.2 to CHIME v1.1.5.Added a new parameter called Date of Social Distancing Measures Effect to specify the date when social distancing measures started showing their effects.Added a new parameter called Recovery to specify the number of recovered cases at the start of the model.COVID-19Surge (CDC) ToolVersion 1 - Released 04 MAY 2020An implementation of Centers for Disease Control and Prevention’s (CDC) COVID-19Surge for use in ArcGIS Pro 2.3 or later. This tool leverages SIICR (Susceptible, Infected, Infectious, Convalescing, Recovered) modeling to assist hospitals, cities, and regions with capacity planning around COVID-19 by providing estimates of daily new admissions and current inpatient hospitalizations (census), ICU admissions, and patients requiring ventilation based on the extent to which mitigation strategies such as social distancing or shelter-in-place recommendations are implemented. This tool is based on COVID-19Surge. Learn more about how COVID-19Surge works.Potential ApplicationsThe illustration above depicts the outputs of the COVID-19Surge (CDC) tool of the COVID-19 Modeling toolbox.A hospital systems administrator needs a simple model to project the number of patients the hospitals in the network will need to accommodate in the next 90 days due to COVID-19. You know the population served by each hospital, the date and level of current social distancing, the number of people who have recovered, and the number of patients that are currently hospitalized with COVID-19 in each facility. Using your hospital point layer, you run the CHIME Model v1.1.5 tool.An aid agency wants to estimate where and when resources will be required in the counties you serve. You know the population and number of COVID-19 cases today and 14 days ago in each county. You run the COVID-19Surge (CDC) tool using your county polygon data, introducing an Intervention Policy and New Infections Per Case (R0) driven by fields to account for differences in anticipated social distancing policies and effectiveness between counties.A county wants to understand how the lessening or removal of interventions may impact hospital bed availability within the county. You run the CHIME Model v1.1.5 and COVID-19Surge (CDC) tool, checking Add Additional Web App Fields in Summary in both tools. You display the published results from each tool in the Capacity Analysis configurable app so estimates can be compared between models.This toolbox requires any license of ArcGIS Pro 2.3 or higher in order to run. Steps for upgrading ArcGIS Pro can be found here.For questions, comments and support, please visit our COVID-19 GeoNet community.

This layer includes Landsat GLS, Landsat 8, and Landsat 9 imagery for use in visualization and analysis. This layer is time enabled and includes a number band combinations and indices rendered on demand. The Landsat 8 and 9 imagery includes nine multispectral bands from the Operational Land Imager (OLI) and two bands from the Thermal Infrared Sensor (TIRS). It is updated daily with new imagery directly sourced from the USGS Landsat collection on AWS.Geographic CoverageGlobal Land Surface.Polar regions are available in polar-projected Imagery Layers: Landsat Arctic Views and Landsat Antarctic Views.Temporal CoverageThis layer is updated daily with new imagery.Together, Landsat 8 and 9 revisit each point on Earth's land surface every 8 days.Most images collected from January 2015 to present are included.Approximately 5 images for each path/row from 2013 and 2014 are also included.This layer also includes imagery from the Global Land Survey* (circa 2010, 2005, 2000, 1990, 1975).Product LevelThe Landsat 8 and 9 imagery in this layer is comprised of Collection 2 Level-1 data.The imagery has Top of Atmosphere (TOA) correction applied.TOA is applied using the radiometric rescaling coefficients provided the USGS.The TOA reflectance values (ranging 0 – 1 by default) are scaled using a range of 0 – 10,000.Image Selection/FilteringA number of fields are available for filtering, including Acquisition Date, Estimated Cloud Cover, and Product ID.To isolate and work with specific images, either use the ‘Image Filter’ to create custom layers or add a ‘Layer Filter’ to restrict the default layer display to a specified image or group of images.To isolate a specific mission, use the Layer Filter and the dataset_id or SensorName fields.Visual RenderingThe default rendering in this layer is Agriculture (bands 6,5,2) 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.Pre-defined functions: Natural Color with DRA, Agriculture with DRA, Geology with DRA, Color Infrared with DRA, Bathymetric with DRA, Short-wave Infrared with DRA, Normalized Difference Moisture Index Colorized, NDVI Raw, NDVI Colorized, NBR Raw15 meter Landsat Imagery Layers are also available: Panchromatic and Pansharpened.Multispectral Bands BandDescriptionWavelength (µm)Spatial Resolution (m)1Coastal aerosol0.43 - 0.45302Blue0.45 - 0.51303Green0.53 - 0.59304Red0.64 - 0.67305Near Infrared (NIR)0.85 - 0.88306SWIR 11.57 - 1.65307SWIR 22.11 - 2.29308Cirrus (in OLI this is band 9)1.36 - 1.38309QA Band (available with Collection 1)*NA30 *More about the Quality Assessment BandTIRS BandsBandDescriptionWavelength (µm)Spatial Resolution (m)10TIRS110.60 - 11.19100 * (30)11TIRS211.50 - 12.51100 * (30)*TIRS bands are acquired at 100 meter resolution, but are resampled to 30 meter in delivered data product.Additional Usage NotesImage exports are limited to 4,000 columns x 4,000 rows per request.This dynamic imagery layer can be used in Web Maps and ArcGIS Pro as well as web and mobile applications using the ArcGIS REST APIs.WCS and WMS compatibility means this imagery layer can be consumed as WCS or WMS services.The Landsat Explorer App is another way to access and explore the imagery.Data SourceLandsat imagery is sourced from the U.S. Geological Survey (USGS) and the National Aeronautics and Space Administration (NASA). Data is hosted in Amazon Web Services as part of their Public Data Sets program.For information, see Landsat 8 and Landsat 9.*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.

Excel files include the raw database and the processed data that led to the quadrat analyses. The "Matrix_raw data" file includes the raw data as downloaded from the server. This data was cleaned and organized for its posterior use. "Quadrat analyzes "file includes all the quadrat analyses resulting in each research question in the paper except question four. Question 4 can be seen in the file "Water analysis_Blaarmeersen." All excel files come with a "CODE" tab that describes each of the codes used, their meaning, and ways that were calculated where necessary. Two zip files include all the GIS files. The first one includes the GIS files from which "Matrix_raw data" was built from. The second folder includes the resulting maps from the quadrat analyses. In order to visualize them as in the paper, configure the symbology tab at the GIS software in quantile and the categories number, as shown in the paper. The production of the files in the "GIS_Processed data" folder was done via a repetitive line of commands in ArcGIS pro. The same process was followed for each one of the quadrat analysis described in the paper. Refer to "Reproduction commands and parameters.pdf" for further information.

VT E911 Composite geocoder - uses ESITE, RDSNAME, and RDSRANGE. REFRESHED WEEKLY. VCGI, in collaboration with the VT E911 Board, has created a suite of geocoding services that can be used to batch geocode addresses using ArcGIS Desktop 10.x. This service can also be integrated into ESRI ArcGIS web-based mapping applications.Input Address Requirements Must use valid E911 addresses (street style addressing...no P.O. box addresses!) and E911 town names. Limitations Don't attempt to geocode more than 50000 records or so. You must have an Internet connection to use the services. A DSL, cable, or other high bandwidth connection is the best option. Addresses other than E911 addresses are not supported. ArcGIS Pro - How To:Startup ArcGIS ProUnder the "Insert" ribbon select Connections --> New ArcGIS Server. Server URL = https://maps.vcgi.vermont.gov/arcgis/servicesBrowse to the ./EGC_services folder and select GEOCODE_COMPOSITE (or GEOCODE_ESITE).Add the table you want to geocode to project, then right-click and select "Geocode Table". Choose the “Go to Tool” option at the bottom of the dialogue box.Make selections and run geocoder.ArcGIS Desktop (ArcMap) - How To: Startup ArcMap 10+ Add a table containing VT addresses to geocode. ?Click the "Add Data" button.Navigate to your table, choose to add your tableRight-click on the table in the table of contentsSelect "Geocode Addresses...".Select "Add" in the dialog box.Browse to the "GIS Servers" icon in your catalog, then double click "Add ArcGIS Server".Select "Use GIS Services", then Next.ServerURL = https://maps.vcgi.vermont.gov/arcgis/services then click finish.Browse to "arcgis on maps.vcgi.org (user)". Browse to .\EGC_services folder.Select GECODE_ESITE (or GEOCODE_COMPOSITE). Click OK.Select whatever options you want in the geocode dialog box, including output, then click ok.The output will be automatically added to your ArcMap session.

This crash dataset does include crashes from 2023 up until near the middle of July that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

The dataset presented here, a historical coregonine spawning database, or CORHIST for short, is the result of several years of coordinated research in archives, libraries, and field stations, to track down evidence of spawning locations for the Coregoninae sub-family of ciscoes and whitefishes in the Great Lakes of North America and their tributaries. Our objective was to accurately identify _location information to coordinates and add all associated data and metadata to a database built specifically for these types of records (a database capable of storing historical, geospatial, and biological data). Data for a total of 11 accepted species of coregonines are included in this dataset. Spawning or nursery habitat designations were assigned based on a wide-range of evidence from original sources, including descriptions of physiology, ontogeny, and behaviors, interviews, first-hand and Indigenous Ecological Knowledge, and by our own examination of museum specimens. Georeferencing was completed using evidence from original records, including navigational information such as dead reckonings, landmarks like islands, lighthouses, reefs, and river mouths, and by using depth and substrate descriptions. Occasionally, supplemental sources including various historical maps and/or published bathymetry and substrate layers were used to assist in georeferencing points. Data points were summarized and quality-checked using ArcMap 10.8 and ArcGIS Pro (datum: WGS84). Reference tables are also included with this dataset.

The amount of water in soil is based on rainfall amount, what proportion of rain infiltrates into the soil, and the soil"s storage capacity. Available water storage is the maximum amount of plant available water a soil can provide. It is an indicator of a soil’s ability to retain water and make it sufficiently available for plant use. Available Water Storage is a capacity estimate for the top 150 centimeters of soil. It is calculated from the difference between soil water content at field capacity and the permanent wilting point adjusted for salinity and fragments. Available water storage is used to develop water budgets, predict droughtiness, design and operate irrigation systems, design drainage systems, protect water resources, and predict yields. Available water storage is an important input into hydrologic models including the Soil and Water Assessment Tool (SWAT) - a water quality model that is designed to assess non-point and point source pollution at the river basin scale. Available water storagecan also be used as an indication of a soil"s drought susceptibility, for water recharge modeling, to assess a soil"s ability to support crops, and for many other purposes. Dataset SummaryPhenomenon Mapped: Amount of water a soil can hold that is available to plantsGeographic Extent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands, Republic of Palau, Republic of the Marshall Islands, Federated States of Micronesia, and American Samoa.Projection: Web Mercator Auxiliary SphereData Coordinate System: WKID 5070 USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WKID 3338 WGS 1984 Albers (Alaska), WKID 4326 WGS 1984 Decimal Degrees (Guam, Republic of the Marshall Islands, Northern Mariana Islands, Republic of Palau, Federated States of Micronesia, American Samoa, and Hawaii).Units: MillimetersCell Size: 30 metersSource Type: DiscretePixel Type: Unsigned integerSource:Natural Resources Conservation ServiceUpdate Frequency: AnnualPublication Date: December 2024 Data from the gNATSGO database was used to create the layer. This layer is derived from the 30m rasters produced by the Natural Resources Conservation Service (NRCS). The value for available water storage is derived from the gSSURGO map unit aggregated attribute table field: Available Water Storage 0-150cm Weighted Average (aws0150wta). What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application. Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "available water storage" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "available water storage" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro. Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions. The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one. Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

This layer presents the locations of major cities within the United States with populations of approximately 10,000 or greater, state capitals, and the national capital. Major Cities are locations containing population totals from the 2020 Census.The points represent U.S. Census Places polygons sourced from U.S. Census Bureau 2020 TIGER FGDB (National Sub-State). Attribute fields include 2020 total population from the U.S. Census Public Law 94 data that symbolize the city points using these six classifications: Class Population Range 5 2,500 – 9,999 6 10,000 – 49,999 7 50,000 – 99,999 8 100,000 – 249,999 9 250,000 – 499,999 10 500,000 and overThis ready-to-use layer can be used in ArcGIS Pro and in ArcGIS Online and its configurable apps, dashboards, StoryMaps, custom apps, and mobile apps. The data can also be exported for offline workflows. Cite the 'U.S. Census Bureau' when using this data.

This crash dataset does include crashes from 2023 up until near the middle of July that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

The new Oregon Address Geocoder is used to find the location coordinates for street addresses in the State of Oregon. This service is:FreePublicUpdated regularlyOutputs location coordinates in Oregon Lambert, feet (SRID 2992)Uses over 2 million address points and 288,000 streets for referenceIt is an ArcGIS multirole locator with two roles:Point Address - Generally more accurate results from rooftop location points. Includes a Subaddress if a unit number is located.Street Address - Less accurate results from an estimated distance along a street centerline address range if a Point Address was not found.Instructions for using the Geocoder via ArcGIS Pro, ArcGIS Online, and REST Services are below:ArcGIS ProWeb ServicesArcGIS Online

This crash dataset does include crashes from 2023 up until near the middle of July that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

This crash dataset does include crashes from 2023 up until near the middle of July that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

This crash dataset was generated in June 2023 and includes those crashes along State Route 4 up until that point. The dataset was uploaded to ArcGIS Online to allow for further review of potential changes to the GIS Crash Dataset(s). The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

This dataset represents crashes on the full extent of Minot Ave between 2012 and May 2023. The Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggreagation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

This crash dataset does include crashes from 2023 up until near the middle of July that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

This crash dataset does include crashes from 2023 up until near the middle of July that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.

This crash dataset does include crashes from 2023 up until the end of May that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that could be toggled on or off if the user were to add this layer to a new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some more advanced options should see the following ESRI article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).Popups have been configured for both the clusters and the individual crashes. The individual crashes themselves do include multiple tables within a single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that do include more than 3 units and information for these additional units is not currently included in the dataset at the moment. The crash data items available in this Feature Layer representation includes many of the same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information may not be visible in those situations where there are four or more units involved in a crash.