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

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 layer shows the countries of Africa. You can click on the map to get info on each country, including its name and flag, as well as links to detailed information in The World Factbook and UN Human Development Reports.The Africa Countries layer was created by joining country population data from The World Factbook to the World Countries (Generalized) layer, using ArcGIS Online analysis tools. The popup for the map uses Arcade expressions to reference other online resources based on the country code for the selected country.The Flags of countries are provided by reference to Flagpedia, which provides flags of countries of the world and the U.S. states for display and download.

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 end of January 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 dashboard defaults to a presentation of the crash points that will cluster the crash types and determine a predominant crash type. In the case two crash types have the same number of crashes for that type the predominant type will not be colored to either of the crash types. Clicking on the clusters will include a basic analysis of the cluster. These clusters are dynamic and will change as the user zooms in an out of the map. The clustering of crashes is functionality availalble in ArcGIS Online and the popups for the clusters is based on items that include elements configured with the Arcade language. Users interested in learning more about point clustering and the configuration of popups should read through some of the examples of the following ESRI Article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/) . The dashboard itself does include a map widget that does allow the user to toggle the visibility of layers and/or click on the crashes within the map. The popups for single crashes can be difficult to see unless the map is expanded (click in upper right of map widget). There is a Review Crashes tab that allows for another display of details of a crash that may be easier for users.This dashboard includes selectors in both the header and sidebar. By default the sidebar is collapsed and would need to be expanded. The crash dataset used in the presentation includes columns with a prefix of the unit. The persons information associated to each unit would be based on the Person that was considered the driver. Crash data can be filtered by clicking on items in chart widgets. All chart widgets have been configured to allow multiple selections and these selections will then filter the crash data accordingly. Allowing for data to be filtered by clicking on widgets is an alternative approach to setting up individual selectors. Selectors can take up a lot of space in the header and sidebar and clicking on the widget items can allow you to explore different scenarios which may ultimately be setup as selectors in the future. The Dashboard has many widgets that are stacked atop each other and underneath these stacked widgets are controls or tabs that allow the user to toggle between different visualizations. The downside to allowing a user to filter based on the output of a widget is the need for the end user to keep track of what has been clicked and the need to go back through and unclick.Many of the Crash Data Elements are based on lookups that have a fairly large range of values to select. This can be difficult sometimes with charts and the fact that a user may be overwhelmed by the number of items be plotted. Some of these values could potentially benefit by grouping similar values. The crash data being used in this dashboard hasn't been post processed to simplify some of the groupings of data and represent the value as it would appear in the Crash System. This dashboard was put together to continue the discussion on what data elements should be included in the GIS Crash Dataset. At the moment there is currently one primary dataset that is used to present crash data in Map Services. There is lots of potential to extend this dataset to include additional elements or it might be beneficial to create different versions of the crash data. Having an examples like this one will hopefully help with the discussion. Workable examples of what works and doesn't work. There are lots of data elements in the Crash System that could allow for an even more detailed safety analysis. Some of the unit items included in the example for Minot Ave in Auburn are the following. This information is included for the first three units associated to any crash.Most Damaged AreaExtent of DamageUnit TypeDirection of Travel (Northbound, Southbound, Eastbound, Westbound)Pre-Crash ActionsSequence of Events 1-4Most Harmful Event Some of the persons items included in the example for Minot Ave in Auburn are the following. This information is included for the first three units associated to any crash and the person would be based on the driver.Condition at Time of CrashDriver Action 1Driver Action 2Driver DistractedAgeSexPerson Type (Driver/Owner(6), Driver(1))In addition to the Units and Persons information included above each crash includes the standard crash data elements which includesDate, Time, Day of Week, Year, Month, HourInjury Level (K,A,B,C,PD)Type of CrashTownname, County, MDOT RegionWeather ConditionsLight ConditionsRoad Surface ConditionsRoad GradeSchool Bus RelatedTraffic Control DeviceType of LocationWork Zone ItemsLocation Type (NODE, ELEMENT) used for LRS# of K, # of A, # of B, # of C, # of PD InjuriesTotal # of UnitsTotal # of PersonsFactored AADT (Only currently applicable for crashes along the roadway (ELEMENT)).Location of First Harmful EventTotal Injury Count for the CrashBoolean Y/N if Pedestrian or Bicycles are InvolvedContributing EnvironmentsContributing RoadRoute Number, Milepoint, Element ID, Node ID

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.

An accident near an elementary school in your city has drawn your attention to the topic of pedestrian and bicycle safety. You want to suggest policy actions to your city's local government that will reduce the likelihood of future accidents.

In this lesson, you'll map accident data regarding pedestrians and cyclists struck by vehicles. Then, you'll determine the number of accidents that occurred within each school zone and identify the five most dangerous zones. You'll present your findings with a story map that provides narrative context and helps users understand your position. This lesson is targeted toward city or county employees or any civic-minded individual who wants to make a difference in their community.

In this lesson you will build skills in the these areas:

• Adding data from the Living Atlas- Symbolizing data with Arcade expressions- Configuring pop-ups- Summarizing data within an area- Sharing maps in a Story Map

Learn ArcGIS is a hands-on, problem-based learning website using real-world scenarios. Our mission is to encourage critical thinking, and to develop resources that support STEM education.

This dashboard shows recycling data collected from tribal nations, cities/towns, counties, and non-profits across Arizona. The original data (2013 - 2022) was cleaned and new data is now being collected via Survey123 as of the 2024 (current) reporting year.Other Information:The map in this dashboard is unique since locations are submitted as points in Survey123, but uses Arcade to spatially join with polygons and construct pop-ups that show multiple years of submissions in a table format. While non-profits are displayed as points, these too use Arcade to construct the pop-ups showing all previously submitted data via non-spatial joins. The representation of the tribal nation, city/town, and county data as polygons allows users to understand the reach of recycling programs in their community, and the inclusion of graphs lets them understand exactly what is being collected when the data is available. Since this data is collected via Survey123, users get updated data immediately without the need to wait for data to be cleaned, formatted, and mapped manually.

This view is a copy of the original COVID-19 Testing Locations in the United States - public dataset (https://giscorps.maps.arcgis.com/home/item.html?id=d7d10caf1cec43e0985cc90fbbcf91cb). The parent hosted feature service is the same. This version is symbolized by site status.This feature layer view contains information about COVID-19 screening and testing locations. It is made available to the public using the GISCorps COVID-19 Testing Site Locator app (https://giscorps.maps.arcgis.com/apps/webappviewer/index.html?id=2ec47819f57c40598a4eaf45bf9e0d16) and on findcovidtesting.com. States and counties are encouraged to include this feature service in their own testing site locator apps as well.Please submit new testing sites or updated testing site information via this form: https://arcg.is/10S1ib. Including this link on your organization's testing site finder web app will allow testing providers to add their own sites directly to the map, improving the accuracy and completeness of the dataset. GISCorps volunteers verify each submission prior to including it in this public view. You can also add your sites in bulk by completing a copy of this template and emailing it to admin@giscorps.org. This dataset is updated daily. All information is sourced from public information shared by health departments, local governments, and healthcare providers. The data are aggregated by GISCorps volunteers in collaboration with volunteers from Coders Against COVID and should not be considered complete or authoritative. Please contact testing sites or your local health department directly for official information and testing requirements.The objective of this application is to aggregate and facilitate the public communications of local governments, health departments, and healthcare providers with regard to testing site locations. GISCorps does not share any screening or testing site location information not previously made public or provided to us by one of those entities.Latest Arcade code for popups available here: https://docs.google.com/document/d/1PDOq-CxUX9fuC2v3N8muuuxN5mLMinWdf7fiwUt1lOM/edit?usp=sharing

The airphoto is flown every 4 years with very detailed imagery for urban areas and less detailed imagery for rural areas. The web map contains the 2022 airphoto at both 40cm and 10cm resolution, the 2018 airphoto at both 25cm and 10cm resolution, and the 2014 airphoto at both 40cm and 10cm resolution. This data can be downloaded at the quarter section level using this web application.Since each airphoto map layer covers different areas of the County, the tiles for each airphoto map layer are symbolised using arcade to show only the tiles that actually have airphoto data. Arcade is also used in the popups to create the links that trigger the download of the geotiff files.

This app shows evacuation routes and demographic data by census tract for Houston, Texas. The darker blue tracts have a higher percentage of households without a vehicle. This pattern helps answer the question: Where in Houston should we provide evacuation assistance during a hurricane?Use the map legend and feature pop-ups to learn more about the data shown in the map. Click individual census tracts to see pop-up information, including the percentage of households without a vehicle.The map in this app contains a Living Atlas layer of Houston evacuation routes and a layer of Houston demographic data. The demographic layer is styled using an Arcade expression that calculates the percentage of households without a vehicle. This information is also provided in pop-ups.

Hosted Feature ServiceThe heart of the Idaho Trails Experience web app is the geographic data served by the Idaho Recreation Trails collection of Hosted Feature Layers. The Hosted service can be updated more frequently and on-the-fly than the previous technology used to maintain Idaho Trails-- changes now appear on the App and through the Feature Service in real time. The newest web presentation technology under AGOL, Experience Builder, served by this dataset, will make possible several extended features to come in future updates to the App.Under the hood Linear routes, closure routes and areas, and boundary area data are ported through a Web Map from the underlying Hosted Feature Layers. In addition to view settings for attributes popups set in the Web Map, additional visibility option not managed directly in the Hosted Feature data or controllable in the Web Map will be further processed in the Experience App presentation.Underlaying Classes in the Dataset: One single linear class "Idaho Routes" contains all road and trail features (59,000+ route segment features): Routes characterized as recreational in nature include "High Clearance" (previously "Jeep" treated as a road type, now as a full-width "trail" type): High-clearance, Special Vehicle Designation (mostly OHVs >50"), OHVs 50" and under, and single-track (each width class separated by seasonal and not); E-Bike; and, non-motorized and non-mechanized.Routes where vehicles either must be highway-legal (OHVs prohibited; typically paved roads), or routes requiring Restricted plate for legal OHV travel (mostly JURISDICTION = County); combined from previously-separate Layers: Highway-legal, Automobile, Other Roads (each with subcategories for seasonal access restrictions). (Note: Different route types are no longer kept in separate layers as with the legacy Map Service dataset. Route symbology, and selectable visibility will be filtered based on the value in the SYMBOL attribute from the above linear class within the Web Map and Experience-based App. If dynamically consuming the Feature Service, provisions will need to be made to filter to select visibility by road and trail types based on the value in the SYMBOL field.)"Points of Interest" (point type data) is comprised of a layer previously titled "Trailheads" and now includes the flexibility of other types of lat/lon point-based information such as links to external maps and "attractions" information such as site seeing destinations not previously included in IDPR's map presentation. "Emergency Route Closures" contains linear route Closures (overlays any route where a Closure Order applies in web map)"Area Restrictions" is added for areas such as defined by human exclusion Orders (polygon; usually planned annual human or vehicle exclusion areas, but can be emergency closure as well)Multiple "Boundary" polygon classes contain boundary outlines and attributes information for IDPR Regions (3), Counties (44), Wildernesses (42), National Forests and Ranger Districts (39), and BLM District and Field Offices (12), and BLM land units (700+). These separate classes reduce the data footprint of the Routes data and are joined in App popups by geographic Intersection logic. Bonus Material:Added to the web app are several optional, dynamic layers via publicly-available REST services selectable for visibility:NIFC Current and Historic Fire primetersIdaho Department of Lands- Lands Available for Recreational Use (visible by-default)Idaho Department of Fish & Game Hunting Units boundaries and numbers BLM Surface Management Agency layer for all local, state, and federal agencies which manage public lands (accessible, and not) US Forest Service Motor Vehicle Use Map, National Dataset (mirrors local MVUM paper and GeoPDF maps, where data available, lags local data when changes are made)National Park Service (NPS) Parks and Monuments areas and boundariesNOHRSC Snow Depth Other REST Services to be added based on utility in researching recreational accessThis dataset is published for the use of the individuals who fund this Program. Organizations wishing to consume this Feature Service into their own application should inquire to IDPR to obtain a use agreement and schema information to aid in development.AGOL Experience App here: https://experience.arcgis.com/experience/97a42a2a73c944ba918042faf518c689 Inquire to maps@idpr.idaho.gov

Contours des 11 des Parcs nationaux de France (Vanoise, Port-Cros, Cévennes, Pyrénées, Ecrins, Mercantour, Guadeloupe, Réunion, Guyane, Calanques, Forêts). Les emprises retenues correspondent aux aires optimales d'adhésion ou périmètre d'étude de la charte (pnx_aoa) mises à disposition par les Parcs Nationaux de France sous Open Licence (v2.0). La table attributaire a été enrichie avec :les données de fréquentation (2006, 2011 et 2018) issues du rapport "Les parcs nationaux de France - Chiffres clés Edition 2021", publié en juin 2021 par le Ministère de la Transition écologique, Les parcs nationaux de France, l'OFB et la Statistique Publique ;les sites webs de chacun des parcs ; les années d'ouvertures isolées dans un champs (sans le jour ni le mois).Cette carte est publiée sur ce portail à titre de démonstration pour illustrer les capacités des webmaps dans le système ArcGIS :popups ;étiquettes ;symbologie ;Arcade ;géosignets.Crédits :Contours des 11 Parcs nationaux de France : donnée produite par les Parcs nationaux de FranceDonnées de fréquentation : rapport produit par le Ministère de la Transition Ecologique, les Parcs nationaux de France, l'OFB et la Statistique Publique