This resource was created by Esri Canada Education and Research. To browse our full collection of higher-education learning resources, please visit https://hed.esri.ca/resourcefinder/

ArcGIS Field Maps is a mobile app that allows you to view and collect field data using an Android or iOS smartphone or tablet. It is also a web app that allows you to configure web maps for use in the mobile app. The tutorials in this learning path will introduce you to the features of the Field Maps mobile app, how to create and configure web maps in Field Maps Designer that can be used in the Field Maps mobile app in online and offline mode, and how to collect data from a map and in the field with the mobile app.

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

Reporter for MRGPThe Reporter for MRGP doesn't require you to download any apps to complete an inventory; all you need is an internet connection and web browser. The Reporter includes culverts and bridges from VTCULVERTS, town highways from Vtrans and the current status of the MRGP segments and outlets on the map.MRGP Fieldworker SolutionNotes on MRGP fieldworker solution: July 12, 2021. The MRGP map now displays the current status of road segments and outlets. Fieldworkers using the MRGP solution should remove the offline map area(s) from their device, and keep their new offline map current, by syncing their map. Enabling auto-sync will get you the current segment or outlet status automatically. See FAQ section below for more information. Road Erosion Inventory forms are available and have a new look and feel this year. The drainage ditch survey is broken out into three pages for a better user experience. The first page contains survey and segment information, the second; the inventory, and the third; barriers to implementation. You will notice the questions are outlined by section so it’s easier to follow along too. The questions have remained the same. Survey123 has a new option requiring users to update surveys on their mobile device. That option has been enabled for the two MRGP Survey123 forms. Step 1: Download the free mobile appsFor fieldworkers to collect and submit data to VT DEC, two free apps are required: ArcGIS Collector or Field Maps and Survey123. ArcGIS Collector or Field Maps is used first to locate the segment or outlet for inventory, and Survey123, for completing the Road Erosion Inventory. ArcGIS Field Maps is ESRI’s new all-in-one app for field work and will replace ArcGIS Collector. You can download ArcGIS Collector or ArcGIS Fields Maps and Survey123 from the Google Play Store.You can download ArcGIS Collector or ArcGIS Field Maps and Survey123 from Apple Store.

Step 2: Sign into the mobile appYou will need appropriate credentials to access fieldworker solution, please contact your Regional Planning Commission’s Transportation Planner or Jim Ryan (MRGP Program Lead) at (802) 490-6140.Open Collector for ArcGIS, select ‘ArcGIS Online’ as shown below, and enter the user name and password. The credential is saved unless you sign out. Step 3: Open the MRGP Mobile MapIf you’re working in an area that has a reliable data connection (e.g. LTE or 4G), open the map below by selecting it.Step 4: Select a road segment or outlet for inventoryUse your location, button circled in red below, select the segment or outlet you need to inventory, and select 'Update Road Segment Status' from the pop-up to launch Survey123.

Step 5: Complete the Road Erosion Inventory and submit inventory to DECSelecting 'Update Road Segment Status' opens Survey123, downloads the relevant survey and pre-populates the REI with important information for reporting to DEC. You will have to enter the same username and password to access the REI forms. The credential is saved unless you sign out of Survey123.Complete the survey using the appropriate supplement below and submit the assessment directly to VT DEC.Paved Roads with Catch Basin SupplementPaved and Gravel Roads with Drainage Ditches Supplement

Step 6: Repeat!Go back to the ArcGIS Collector or Field Maps and select the next segment for inventory and repeat steps 1-5.

If you have question related to inventory protocol reach out to Jim Ryan, MRGP Program Lead, at jim.ryan@vermont.gov, (802) 490-6140If you have questions about implementing the mobile data collection piece please contact Ryan Knox, ADS-ANR IT, at ryan.knox@vermont.gov, (802) 793-0297

The location where I'm doing inventory does not have a data coverage (LTE or 4G). What can I do?ArcGIS Collector allows you take map areas offline when you think there will be spotty or no data coverage. I made a video to demonstrate the steps for taking map areas offline - https://youtu.be/OEsJrCVT8BISurvey123 operates offline by default but you need to download the survey. My recommendation is to test the fieldworker solution (Steps 1-5) before you go into the field but don't submit the test survey.Where can I download the Road Erosion Scoring shown on the the Atlas? You can download the scoring for both outlets and road segments through the VT Open Geodata Portal.https://geodata.vermont.gov/maps/VTANR::mrgp-scoring-open-data/aboutHow do I use my own ArcGIS Collector map for launching the official MRGP REI survey form? You can use the following custom url for launching Survey123, open the REI and prepopulate answers in the form. More information is here. TIP: add what's below directly in the HTML view of the popup not the link as described in the post I provided.

Hydrologically connected segments (lines):Update Road Segment Status

Segment ID: {SegmentID}
Segment Status: {SegmentStatus}
{RoadName}, {Municipality}
Outlets: {Outlets}
Hydrologically connected outlets (points):Update Outlet Status

Outlet ID: {OutletID}
Municipality: {Municipality}
Erosion: {ErosionValue}

How do I save my name and organization information used in subsequent surveys? Watch this short video or execute the steps below:

Open Survey123 and open a blank REI form (Collect button) Note: it's important to open a blank form so you don't save the same segment id for all your surveys Fill-in your 'Name' and 'Organization' and clear the 'Date of Assessment field' (x button). Using the favorites menu in the top-right corner you can use the current state of your survey to 'Set as favorite answers.' Close survey and 'Save this survey in Drafts.' Use Collector to launch survey from selected feature (segment or outlet). Using the favorites menu again, 'Paste answers from favorite.

What if the map doesn't have the outlet or road segment I need to inventory for the MRGP? Go Directly to Survey123 and complete the appropriate Road Erosion Inventory and submit the data to DEC. The survey includes a Geopoint (location) that we can use to determine where you completed the inventory.

Where can I view the Road Erosion Inventories completed with Survey123? Using the MRGP credentials you have access to another map that shows completed REIs.Web map - Completed Road Erosion Inventories for MRGPWhere can I download the 2020-2021 data collected with Survey123?Road Segments (lines) - https://vtanr.maps.arcgis.com/home/item.html?id=f8a11de8a5a0469596ef11429ab49465Outlets (points) - https://vtanr.maps.arcgis.com/home/item.html?id=ae13a925a662490184d5c5b1b9621672Where can I download the 2019 data collected with Survey123?

Road Segments (lines) - https://vtanr.maps.arcgis.com/home/item.html?id=f60050c6f3c04c60b053470483acb5b1 Outlets (points) - https://vtanr.maps.arcgis.com/home/item.html?id=753006f9ecf144ccac8ce37772bb2c03 Where can I download the 2018 data collected with Survey123?Outlets (points) - https://vtanr.maps.arcgis.com/home/item.html?id=124b617d142e4a1dbcfb78a00e8b9bc5Road Segments (lines) - https://vtanr.maps.arcgis.com/home/item.html?id=8abcc0fcec0441ce8ae6cd38e3812b1b Where can I download the Hydrologically Connected Road Segments and Outlets?Vermont Open Data Geoportal - https://geodata.vermont.gov/datasets/VTANR::hydrologically-connected-road-segments-1/about

This 2019 version of the MRGP Outlets is based on professional mapping completed using DEC's Stormwater Infrastructure dataset. In catch basin systems, work was completed to match outlets to road segments that drain to them. The outlets here correspond to Outlet IDs identified in the Hydrologically connected roads segments layer. For outlets that meet standard, road segments will also meet the standard for MRGP compliance.

This tutorial will teach you how to take time-series data from many field sites and create a shareable online map, where clicking on a field location brings you to a page with interactive graph(s).

The tutorial can be completed with a sample dataset (provided via a Google Drive link within the document) or with your own time-series data from multiple field sites.

Part 1 covers how to make interactive graphs in Google Data Studio and Part 2 covers how to link data pages to an interactive map with ArcGIS Online. The tutorial will take 1-2 hours to complete.

An example interactive map and data portal can be found at: https://temple.maps.arcgis.com/apps/View/index.html?appid=a259e4ec88c94ddfbf3528dc8a5d77e8

Navigator for ArcGIS is a mobile app that gets your field workforce where it needs to be, unlocking efficiency gains and improving reliability. Learn how it works offline in seamless interaction with ArcGIS field apps. Experience how to use the data provided, your own custom data, or both to search and navigate directly to your organization's assets.This seminar was developed to support ArcGIS Online and Navigator for ArcGIS.

All data displayed on this map is near real-time. There are two ways in which this happens: Web service based data and a mobile mapping application called Field Maps. Web services are updated regularly ranging from every minute to once a month. All web services in this map are refreshed automatically to ensure the latest data being provided is displayed. Data collected through the use of Field Maps is done so by firefighters on the ground. The Field Maps application is consuming, creating, and editing data that are stored in ArcGIS Online. These data are then fed directly in to this map. To learn more about these web mapping technologies, visit the links below:Web ServicesArcGIS Field MapsArcGIS OnlineWeb Services used in this map:(visit link to learn more about each service)IRWIN - A central hub that orchestrates data between various fire reporting applications. When a new incident is created and/or updated by a dispatch center or other fire reporting system, it is then displayed on the map using the Integrated Reporting of Wildland-Fire Information (IRWIN) service. Automatically refreshes every five minutes:Fires by Cause - Any incident that has occurred year to date displayed by cause.ArcGIS Online/Field Maps - Part of the Esri Geospatial Cloud, ArcGIS Online and Collector enables firefighters to use web maps created in ArcGIS Online on mobile devices using the Collector application to capture and edit data on the fireline. Data may be captured and edited in both connected and disconnected environments. When data is submitted back to the web service in ArcGIS Online, it is then checked for accuracy and approved for public viewing.Fire Perimeter - Must be set to 'Approved' and 'Public' to be displayed on the map. Automatically refreshes every five minutes.

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

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

This dataset contains files created, digitized, or georeferenced by Chris DeRolph for mapping the pre-urban renewal community within the boundaries of the Riverfront-Willow St. and Mountain View urban renewal projects in Knoxville TN. Detailed occupant information for properties within boundaries of these two urban renewal projects was extracted from the 1953 Knoxville City Directory. The year 1953 was chosen as a representative snapshot of the Black community before urban renewal projects were implemented. The first urban renewal project to be approved was the Riverfront-Willow Street project, which was approved in 1954 according to the University of Richmond Renewing Inequality project titled ‘Family Displacements through Urban Renewal, 1950-1966’ (link below in the 'Other shapefiles' section). For ArcGIS Online users, the shapefile and tiff layers are available in AGOL and can be found by clicking the ellipsis next to the layer name and selecting 'Show item details' for the layers in this webmap https://knoxatlas.maps.arcgis.com/apps/webappviewer/index.html?id=43a66c3cfcde4f5f8e7ab13af9bbcebecityDirectory1953 is a folder that contains:JPG images of 1953 City Directory for street segments within the urban renewal project boundaries; images collected at the McClung Historical CollectionTXT files of extracted text from each image that was used to join occupant information from directory to GIS address datashp is a folder that contains the following shapefiles:Residential:Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and property ownersBlack_rented_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and non-owners of the propertyNon_Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as property owners that were not listed as BlackNon_Black_rented_residential_1953.shp: residential entries in the 1953 City Directory not listed as Black or property ownersResidential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposeslastName: occupant's last namelabelShort: combines the Number and lastName fields for map labeling purposesNon-residential:Black_nonResidential_1953.shp: non-residential entries in the 1953 City Directory listed as Black-occupiedNonBlack_nonResidential_1953.shp: non-residential entries in the 1953 City Directory not listed as Black-occupiedNon-residential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationNAICS6: 2022 North American Industry Classification System (NAICS) six-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS6title: NAICS6 title/short descriptionNAICS3: 2022 North American Industry Classification System (NAICS) three-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS3title: NAICS3 title/short descriptionflag: flags whether the occupant is part of the public sector or an NGO; a flag of '0' indicates the occupant is assumed to be a privately-owned businessrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposesOther shapefiles:razedArea_1972.shp: approximate area that appears to have been razed during urban renewal based on visual overlay of usgsImage_grayscale_1956.tif and usgsImage_colorinfrared_1972.tif; digitized by Chris DeRolphroadNetwork_preUrbanRenewal.shp: road network present in urban renewal area before razing occurred; removed attribute indicates whether road was removed or remains today; historically removed roads were digitized by Chris DeRolph; remaining roads sourced from TDOT GIS roads dataTheBottom.shp: the approximate extent of the razed neighborhood known as The Bottom; digitized by Chris DeRolphUrbanRenewalProjects.shp: boundaries of the East Knoxville urban renewal projects, as mapped by the University of Richmond's Digital Scholarship Lab https://dsl.richmond.edu/panorama/renewal/#view=0/0/1&viz=cartogram&city=knoxvilleTN&loc=15/35.9700/-83.9080tiff is a folder that contains the following images:streetMap_1952.tif: relevant section of 1952 map 'Knoxville Tennessee and Surrounding Area'; copyright by J.U.G. Rich and East Tenn Auto Club; drawn by R.G. Austin; full map accessed at McClung Historical Collection, 601 S Gay St, Knoxville, TN 37902; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphnewsSentinelRdMap_1958.tif: urban renewal area map from 1958 Knox News Sentinel article; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphusgsImage_grayscale_1956.tif: May 18, 1956 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/ARA550590030582/usgsImage_colorinfrared_1972.tif: April 18, 1972 color infrared USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR6197002600096/usgsImage_grayscale_1976.tif: November 8, 1976 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR1VDUT00390010/

From presentations and reports to stories and field work, maps make everything better.GoalsExplore the suite of ArcGIS maps and apps available to your organization.Create and configure a web map using ArcGIS Online.Share your web maps with anyone, at any time, on any device.

This file presents, as of 10 June 2024, for Metropolitan France, all the crossing points belonging to the underground lines of the public electricity transmission network managed by RTE. An underground crossing point represents a ‘power junction’ (e.g.: junction between two cables). In addition to this dataset, for access to our mobility infrastructure data, you will find the open data map on our ArcGis Online system accessible on PC here or on the move by opening the map in ArcGIS Field Maps: INSPIRE TEN Network. This dataset is shared within the framework of Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE). The INSPIRE Directive applies to digital spatial data held by public authorities and requires data to be made available in accordance with harmonised technical specifications. For further information on the INSPIRE Directive, write to: rte-inspire-infos@rte-france.com. The number of crossing points has been significantly reduced thanks to an evolution of the data model. The publication of this dataset does not exonerate the user from his regulatory obligation under the anti-damage decree (DT/DICT) in case of works. * * *

This file presents, as of 10 June 2024, for Metropolitan France, all the overhead lines of the public electricity transmission network managed by RTE. You will find in the Export tab the different formats available, including ShapeFile. This dataset presents the sections as a broken line of identical characteristics.If multiple power lines share the same towers, they are listed in the attributes Line code n, Line name n, Line owner n. A complete line may require consolidation of multiple entries in the Overhead Lines and Underground Lines datasets if applicable as soon as its identifier appears in one of the Line Code fields. In this dataset, work identifiers refer to Transit Links (LIT - business object), while work names are the names of Links (which are a set of LITs, delimited by substations). Since a link is composed of one or more LITs, it is normal to find several objects with the same work name, while having a different identifier. The change from the old cutting (until June 2022) is the export of broken lines of identical characteristics instead of exporting only right-hand segments. There are therefore much fewer entities to handle, we go from around 256000 in the air to less than 14000 also decreasing the volume of files. Geographic accuracy has been improved and the position of the inflections coincides with the dataset of the pylons. This new division will be the only one maintained from December 2022. In addition to this dataset, for access to our mobility infrastructure data, you will find the open data map on our ArcGis Online system accessible on PC here or on the move by opening the map in ArcGIS Field Maps: INSPIRE TEN Network. This dataset is shared within the framework of Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE). The INSPIRE Directive applies to digital spatial data held by public authorities and requires data to be made available in accordance with harmonised technical specifications. For further information on this dataset, write to: rte-inspire-infos@rte-france.com The publication of this dataset does not exempt the user from his regulatory obligation under the anti-damage decree (DT/DICT) in the event of works or consultation of the Urban Planning Geoportal for urban planning applications (Servitudes). * * *

The Digital Geologic-GIS Map of San Miguel Island, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (smis_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (smis_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (smis_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (smis_geology_metadata_faq.pdf). Please read the chis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (smis_geology_metadata.txt or smis_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

This file presents, as of 10 June 2024, for Metropolitan France, all the underground lines of the public electricity transmission network managed by RTE. You will find in the Export tab the different formats available, including ShapeFile. This dataset presents the sections as a broken line of identical characteristics. If multiple power lines share the same towers, they are listed in the attributes Line code n, Line name n, Line owner n. A complete line may require consolidation of multiple entries in the Overhead Lines and Underground Lines datasets if applicable as soon as its identifier appears in one of the Line Code fields. In this dataset, work identifiers refer to Transit Links (LIT - business object), while work names are the names of Links (which are a set of LITs, delimited by substations). Since a link is composed of one or more LITs, it is normal to find several objects with the same work name, while having a different identifier. The change from the old cutting (until June 2022) is the export of broken lines of identical characteristics instead of exporting only right-hand segments. There are therefore much fewer entities to manipulate, from around 355000 underground to less than 4500 also reducing the volume of files. Geographic accuracy has been improved. This new division will be the only one maintained from December 2022. In addition to this dataset, for access to our mobility infrastructure data, you will find the open data map on our ArcGis Online system accessible on PC here or on the move by opening the map in ArcGIS Field Maps: INSPIRE TEN Network. This dataset is shared within the framework of Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE). The INSPIRE Directive applies to digital spatial data held by public authorities and requires data to be made available in accordance with harmonised technical specifications. For further information on this dataset, write to: rte-inspire-infos@rte-france.com. The publication of this dataset does not exempt the user from his regulatory obligation under the anti-damage decree (DT/DICT) in the event of works or consultation of the Urban Planning Geoportal for urban planning applications (Servitudes).

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

This file presents, as of 10 June 2024, for Metropolitan France, all the pylons belonging to the overhead lines of the public electricity transmission network managed by RTE. These data are supplemented by geographical coordinates expressed in decimal degrees (DD). The value of the total height of the pylon, where indicated, shall be given to the best accuracy available to RTE. In addition to this dataset, for access to our mobility infrastructure data, you will find the open data map on our ArcGis Online system accessible on PC here or on the move by opening the map in ArcGIS Field Maps: INSPIRE TEN Network. This dataset is shared within the framework of Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE). The INSPIRE Directive applies to digital spatial data held by public authorities and requires data to be made available in accordance with harmonised technical specifications. For more information on this dataset, write to: rte-inspire-infos@rte-france.com * * *

This layer shows population broken down by race and Hispanic origin. This is shown by tract, county, and state centroids. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the predominant race living within an area, and the total population in that area. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B03002Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

World Imagery provides one meter or better satellite and aerial imagery in many parts of the world and lower resolution satellite imagery worldwide. The map includes 15m TerraColor imagery at small and mid-scales (~1:591M down to ~1:72k) and 2.5m SPOT Imagery (~1:288k to ~1:72k) for the world. The map features 0.5m resolution imagery in the continental United States and parts of Western Europe from Maxar. Additional Maxar sub-meter imagery is featured in many parts of the world. In the United States, 1 meter or better resolution NAIP imagery is available in some areas. In other parts of the world, imagery at different resolutions has been contributed by the GIS User Community. In select communities, very high resolution imagery (down to 0.03m) is available down to ~1:280 scale. You can contribute your imagery to this map and have it served by Esri via the Community Maps Program. View the list of Contributors for the World Imagery Map.See World Imagery for more information on this map.Metadata: Point and click on the map to see the resolution, collection date, and source of the imagery. Values of "99999" mean that metadata is not available for that field. The metadata applies only to the best available imagery at that location. You may need to zoom in to view the best available imagery.Feedback: Have you ever seen a problem in the Esri World Imagery Map that you wanted to see fixed? You can use the Imagery Map Feedback web map to provide feedback on issues or errors that you see. The feedback will be reviewed by the ArcGIS Online team and considered for one of our updates.Need Newer Imagery?: If you need to access more recent or higher resolution imagery, you can find and order that in the Content Store for ArcGIS app.Learn MoreGet AccessOpen App

This layer shows workers' place of residence by mode of commute. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized by the percentage of workers who drove alone. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B08301 (Not all lines of this ACS table are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

Sixty-seven maps from Indian Land Cessions in the United States, compiled by Charles C. Royce and published as the second part of the two-part Eighteenth Annual Report of the Bureau of American Ethnology to the Secretary of the Smithsonian Institution, 1896-1897 have been scanned, georeferenced in JPEG2000 format, and digitized to create this feature class of cession maps. The mapped cessions and reservations included in the 67 maps correspond to entries in the Schedule of Indian Land Cessions, indicating the number and location of each cession by or reservation for the Indian tribes from the organization of the Federal Government to and including 1894, together with descriptions of the tracts so ceded or reserved, the date of the treaty, law or executive order governing the same, the name of the tribe or tribes affected thereby, and historical data and references bearing thereon, as set forth in the subtitle of the Schedule. Go to this URL for full metadata: https://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.TRIBALCEDEDLANDS.xml Each Royce map was georeferenced against one or more of the following USGS 1:2,000,000 National Atlas Feature Classes contained in \NatlAtlas_USGS.gdb: cities_2mm, hydro_ln_2mm, hydro_pl_2mm, plss_2mm, states_2mm. Cessions were digitized as a file geodatabase (GDB) polygon feature class, projected as NAD83 USA_Contiguous_Lambert_Conformal_Conic, which is the same projection used to georeference the maps. The feature class was later reprojected to WGS 1984 Web Mercator (auxiliary sphere) to optimize it for the Tribal Connections Map Viewer. Polygon boundaries were digitized as to not deviate from the drawn polygon edge to the extent that space could be seen between the digitized polygon and the mapped polygon at a viewable scale. Topology was maintained between coincident edges of adjacent polygons. The cession map number assigned by Royce was entered into the feature class as a field attribute. The Map Cession ID serves as the link referencing relationship classes and joining additional attribute information to 752 polygon features, to include the following: 1. Data transcribed from Royce's Schedule of Indian Land Cessions: a. Date(s), in the case of treaties, the date the treaty was signed, not the date of the proclamation; b. Tribe(s), the tribal name(s) used in the treaty and/or the Schedule; and c. Map Name(s), the name of the map(s) on which a cession number appears; 2. URLs for the corresponding entry in the Schedule of Indian Land Cessions (Internet Archive) for each unique combination of a Date and reference to a Map Cession ID (historical references in the Schedule are included); 3. URLs for the corresponding treaty text, including the treaties catalogued by Charles J. Kappler in Indian Affairs: Laws and Treaties (HathiTrust Digital Library), executive order or other federal statute (Library of Congress and University of Georgia) identified in each entry with a reference to a Map Cession ID or IDs; 4. URLs for the image of the Royce map(s) (Library of Congress) on which a given cession number appears; 5. The name(s) of the Indian tribe or tribes related to each mapped cession, including the name as it appeared in the Schedule or the corresponding primary text, as well as the name of the present-day Indian tribe or tribes; and 6. The present-day states and counties included wholly or partially within a Map Cession boundary. During the 2017-2018 revision of the attribute data, it was noted that 7 of the Cession Map IDs are missing spatial representation in the Feature Class. The missing data is associated with the following Cession Map IDs: 47 (Illinois 1), 65 (Tennessee and Bordering States), 128 (Georgia), 129 (Georgia), 130 (Georgia), 543 (Indian Territory 3), and 690 (Iowa 2), which will be updated in the future. This dataset revises and expands the dataset published in 2015 by the U.S. Forest Service and made available through the Tribal Connections viewer, the Forest Service Geodata Clearinghouse, and Data.gov. The 2018 dataset is a result of collaboration between the Department of Agriculture, U.S. Forest Service, Office of Tribal Relations (OTR); the Department of the Interior, National Park Service, National NAGPRA Program; the U.S. Environmental Protection Agency, Office of International and Tribal Affairs, American Indian Environmental Office; and Dr. Claudio Saunt of the University of Georgia. The Forest Service and Dr. Saunt independently digitized and georeferenced the Royce cession maps and developed online map viewers to display Native American land cessions and reservations. Dr. Saunt subsequently undertook additional research to link Schedule entries, treaty texts, federal statutes and executive orders to cession and reservation polygons, which he agreed to share with the U.S. Forest Service. OTR revised the data, linking the Schedule entries, treaty texts, federal statues and executive orders to all 1,172 entries in the attribute table. The 2018 dataset has incorporated data made available by the National NAGPRA Program, specifically the Indian tribe or tribes related to each mapped cession, including the name as it appeared in the Schedule or the corresponding primary text and the name of the present-day Indian tribe or tribes, as well as the present-day states and counties included wholly or partially within a Map Cession boundary. This data replaces in its entirety the National NAGPRA data included in the dataset published in 2015. The 2015 dataset incorporated data presented in state tables compiled from the Schedule of Indian Land Cessions by the National NAGPRA Program. In recent years the National NAGPRA Program has been working to ensure the accuracy of this data, including the reevaluation of the present-day Indian tribes and the provision of references for their determinations. Changes made by the OTR have not been reviewed or approved by the National NAGPRA Program. The Forest Service will continue to collaborate with other federal agencies and work to improve the accuracy of the data included in this dataset. Errors identified since the dataset was published in 2015 have been corrected, and we request that you notify us of any additional errors we may have missed or that have been introduced. Please contact Rebecca Hill, Policy Analyst, U.S. Forest Service, Office of Tribal Relations, at rebeccahill@fs.usda.gov with any questions or concerns with regard to the data included in this dataset.