Geocode addresses for the Portland metropolitan region. The locator is based on RLIS data including the Master Address File and streets and supports finding an address in a single-line format. It is available both as a geocode service and as a downloadable locator package. This is the original geocode service, the original ArcMap-compatible downloadable locator package is available under the name "RLIS Address Locator - Download." The new ArcGIS Pro version of the geocode service with autosuggest functionality enabled is available under the name "RLIS Address Locator (Pro)." Date of last data update: 2025-04-21 This is official RLIS data. Contact Person: Alicia Wood alicia.wood@oregonmetro.gov 503-813-7561 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2751 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

Geocode addresses for the Portland metropolitan region. This locator is an ArcGIS Pro version of the RLIS Address Locator, with autosuggestion capabilities enabled. It is based on RLIS data including the Master Address File and Streets and supports finding an address in a single-line format. It is available both as a geocode service and as a downloadable locator package. This is the new ArcGIS Pro based geocode service with autosuggest functionality enabled, the ArcMap-compatible version is available under the name "RLIS Address Locator." The new ArcGIS Pro version of the downloadable locator package is available under the name "RLIS Address Locator (Pro) - Download." Date of last data update: 2025-04-21 This is official RLIS data. Contact Person: Alicia Wood alicia.wood@oregonmetro.gov 503-813-7561 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3736 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

Arizona composite geocoding service using NextGen 9-1-1 address points and road centerlines datasets. The source data used in creating this web service provides updated information from Arizona local governments based on quarterly, biannual, or annual submission scheduling. ArcGIS desktop or applications can use the geocoding service depending on the intent of use. By default, the input data sources reside in the NAD83 UTM Zone 12N projection but can be translated upon output by desktop software or application settings. Each locator element uses a result hierarchy from the most granular result provided as an output first (Address Points) to the least granular last (Road Centerline). Data is limited to Arizona and cannot guarantee results in other states. For more information about the Arizona geocoder, please visit https://azgeo-data-hub-agic.hub.arcgis.com/If you are using the AZGeo Address Locator in ArcGIS Desktop or ArcGIS Pro you can connect to the AZGeo server via: https://azgeo.az.gov/arcgis/rest/services/ and then look in the 'geocoders' folder and use AZGeo_Address_Locator.

This locator file provides the ability to perform tabular geocoding, reverse geocoding, and identifying results for locations that contain sub-addresses using ArcGIS Pro or ArcGIS Desktop in an offline/disconnected environment. This service and the supporting data are provided by the AddressNC program.A geocoding web service is also available.

This geocoding service provides the ability to perform tabular geocoding, reverse geocoding, and identifying results for locations that contain sub-addresses. This service and the supporting data are provided by the AddressNC program.A geocoding locator file is also available for users of ArcGIS Pro or ArcGIS Desktop in an offline/disconnected environment.

The VGIN Composite Geocoding service is a cascading locator consisting of Virginia Address Points, Virginia RCL (Road Centerlines), Virginia Community Anchor Institutions (CAI), and several other data layers that supply the end user with returned XY coordinates based on input address number or address name. The source data used in creating this REST service provides updated information from Virginia local governments based on quarterly, biannual, or annual submission scheduling. ESRI applications can use the geocoding service depending on intent of use. By default, the input data sources reside in the Virginia Lambert Conformal Conic projection but can be translated upon output by desktop software or application settings. Each locator element uses a result hierarchy from the most granular result provided as an output first (Address Points) to the least granular last (Jurisdictions). Data is limited to the Commonwealth of Virginia and cannot guarantee results in other states. Underlying locator files within the service for Address Points and RCL are updated quarterly.General use within ArcGIS Desktop and ArcGIS Pro:https://vgin.vdem.virginia.gov/documents/VGIN::about-the-vgin-composite-geocoding-service/exploreDevelopers:https://developers.arcgis.com/rest/geocode/api-reference/geocoding-geocode-addresses.htmFrequently asked question about applications that need Spatial Reference adjustment on output. Search (control+f) web page using outSR. VGIN Base Map REST services utilize WGS Web Mercator (ID 102100) while the VGIN Composite Locator is WGS standard (ID 4269).Individual Address Locator Downloads (ArcGIS Pro 3.3):Address PointsRoad Centerlines

The new Oregon Address Geocoder is used to find the location coordinates for street addresses in the State of Oregon. This service is:

• Free
  
• Public
• Updated regularly
• Outputs location coordinates in Oregon Lambert, feet (SRID 2992)
• Uses over 2 million address points and 288,000 streets for reference

It is an ArcGIS multirole locator with two roles:

1. Point Address - Generally more accurate results from rooftop location points. Includes a Subaddress if a unit number is located.
   
2. Street Address - Less accurate results from an estimated distance along a street centerline address range if a Point Address was not found.

Instructions for using the Geocoder via ArcGIS Pro, ArcGIS Online, and REST Services are below:

ArcGIS Pro
Web Services
ArcGIS Online

This web map features a vector basemap of OpenStreetMap (OSM) data created and hosted by Esri. Esri produced this vector tile basemap in ArcGIS Pro from a live replica of OSM data, hosted by Esri, and rendered using a creative cartographic style emulating a blueprint technical drawing. The vector tiles are updated every few weeks with the latest OSM data. This vector basemap is freely available for any user or developer to build into their web map or web mapping apps.OpenStreetMap (OSM) is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site: www.OpenStreetMap.org. Esri is a supporter of the OSM project and is excited to make this new vector basemap available available to the OSM, GIS, and Developer communities.

The way to access Layers Quickly.

Quick Layers is an Add-In for ArcGIS Pro 3 that allows rapid access to the DNR's Geospatial Data Resource Site (GDRS). The GDRS is a data structure that serves core geospatial dataset and applications for not only DNR, but many state agencies, and supports the Minnesota Geospatial Commons. Data added from Quick Layers is pre-symbolized, helping to standardize visualization and map production. Current version: 3.11

To use Quick Layers with the GDRS, there's no need to download QuickLayers from this location. Instead, download a full copy or a custom subset of the public GDRS (including Quick Layers for ArcGIS Pro 3) using GDRS Manager.

Quick Layers also allows users to save and share their own pre-symbolized layers, thus increasing efficiency and consistency across the enterprise.

Installation:

After using GDRS Manager to create a GDRS, including Quick Layers, add the path to the Quick Layers addin to the list of shared folders:
1. Open ArcGIS Pro
2. Project -> Add-In Manager -> Options
3. Click add folder, and enter the location of the Quick Layers Pro app. For example, if your GDRS is mapped to the V drive, the path would be V:\gdrs\apps\pub\us_mn_state_dnr\quick_layers_pro3
4. After you do this, the Quick Layers ribbon will be available. To also add Quick Layers to the Quick Access Toolbar at the top, right click Quick Layers, and select Add to Quick Access Toolbar

The link below is only for those who are using Quick Layers without a GDRS. To get the most functionality out of Quick Layers, don't install it separately, but instead download it as part of a GDRS build using GDRS Manager.

The Residential Schools Locations Dataset in Geodatabase format (IRS_Locations.gbd) contains a feature layer "IRS_Locations" that contains the locations (latitude and longitude) of Residential Schools and student hostels operated by the federal government in Canada. All the residential schools and hostels that are listed in the Residential Schools Settlement Agreement are included in this dataset, as well as several Industrial schools and residential schools that were not part of the IRRSA. This version of the dataset doesn’t include the five schools under the Newfoundland and Labrador Residential Schools Settlement Agreement. The original school location data was created by the Truth and Reconciliation Commission, and was provided to the researcher (Rosa Orlandini) by the National Centre for Truth and Reconciliation in April 2017. The dataset was created by Rosa Orlandini, and builds upon and enhances the previous work of the Truth and Reconcilation Commission, Morgan Hite (creator of the Atlas of Indian Residential Schools in Canada that was produced for the Tk'emlups First Nation and Justice for Day Scholar's Initiative, and Stephanie Pyne (project lead for the Residential Schools Interactive Map). Each individual school location in this dataset is attributed either to RSIM, Morgan Hite, NCTR or Rosa Orlandini. Many schools/hostels had several locations throughout the history of the institution. If the school/hostel moved from its’ original location to another property, then the school is considered to have two unique locations in this dataset,the original location and the new location. For example, Lejac Indian Residential School had two locations while it was operating, Stuart Lake and Fraser Lake. If a new school building was constructed on the same property as the original school building, it isn't considered to be a new location, as is the case of Girouard Indian Residential School.When the precise location is known, the coordinates of the main building are provided, and when the precise location of the building isn’t known, an approximate location is provided. For each residential school institution location, the following information is provided: official names, alternative name, dates of operation, religious affiliation, latitude and longitude coordinates, community location, Indigenous community name, contributor (of the location coordinates), school/institution photo (when available), location point precision, type of school (hostel or residential school) and list of references used to determine the location of the main buildings or sites. Access Instructions: there are 47 files in this data package. Please download the entire data package by selecting all the 47 files and click on download. Two files will be downloaded, IRS_Locations.gbd.zip and IRS_LocFields.csv. Uncompress the IRS_Locations.gbd.zip. Use QGIS, ArcGIS Pro, and ArcMap to open the feature layer IRS_Locations that is contained within the IRS_Locations.gbd data package. The feature layer is in WGS 1984 coordinate system. There is also detailed file level metadata included in this feature layer file. The IRS_locations.csv provides the full description of the fields and codes used in this dataset.

Laatste update: 07 december 2023Een locator kan helpen om een specifieke locatie op de kaart te vinden, of om een tabel met adressen of plaatsen om te zetten naar punten op de kaart. Het kan gebruikt worden in meerdere onderdelen van het ArcGIS-platform. Een locator bevat de referentiedata die gebruikt wordt om te geocoderen, en daarnaast ook indices, regels, configuratie en regionale kennis over de weergave van adressen. Daarom kan een locator een beter zoekresultaat geven dan een eenvoudige database query.Een locator kan worden gemaakt binnen ArcGIS Pro (zie Create a locator—ArcGIS Pro | Documentation) en lokaal worden gebruikt. Het voordeel van het ArcGIS-platform is dat een locator ook op eenvoudige wijze kan worden gedeeld binnen de organisatie of met het publiek. Een locator kan gedeeld worden als een service in ArcGIS Enterprise. De locator kan up to date gehouden worden, zonder dat de eindgebruiker hinder ondervindt van eventuele updates.

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

This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

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

Pacific lamprey (Entosphenus tridentata) are native fish to the Columbia River Basin. Over the past 60 years, anthropogenic disturbances have contributed to a 95% decline of historical population numbers. Member-tribes of the Columbia River Inter-Tribal Fish Commission have acknowledged the importance of Pacific lamprey to the Columbia River ecosystem and expressed concern about the loss of an essential tribal cultural resource. As a result, the Columbia River Inter-Tribal Fish Commission created the Tribal Pacific Lamprey Restoration Plan to halt their decline, re-establish the species, and restore the population to sustainable, harvestable levels throughout their historical range. Limited knowledge about the movement and preferred habitat of larval Pacific lamprey, such as optimal habitat conditions, demographic information, and species resilience, results in challenges to monitor and protect the species. Pacific lamprey is known to use the mainstem Columbia River to migrate between their spawning grounds and the Pacific Ocean. However, dams, levees, and culverts within the Columbia River Estuary and adjacent tributaries have restricted the lamprey's access to spawning grounds and other upstream habitats. These restrictions have prompted conservation and restoration efforts to better understand how Pacific lamprey utilizes the Columbia River Estuary. Here, we address these knowledge gaps in an effort to aid restoration initiatives by completing a Habitat Suitability Analysis to determine where optimal larval Pacific lamprey habitat may exist in the Columbia River Estuary. The project identified the spatial and temporal distribution of suitable habitat for larval Pacific lamprey and generated recommendations to address habitat-related knowledge gaps and further evaluate anthropogenic threats to their recovery. The results of the Habitat Suitability Analysis suggest that habitat conditions in the Columbia River itself are unable to support larval lamprey year-round, but may provide suitable habitat on a seasonal basis due to spatial and temporal limitations. However, we stress that our analyses were necessarily limited to aquatic conditions and that the temperature of the water column used in our analyses may differ from the temperature within fine sediments, where larval lamprey burrow. Our results imply that suitable lamprey habitat is present at times throughout the year in the Columbia River Estuary, and these locations can be used to support habitat restoration and conservation strategies for improving the species' recovery. Anthropogenic threats to the Columbia River continue to alter habitat conditions, including average water temperature, salinity, and sedimentation. Laboratory experiments have provided insight into the potential impacts of changing temperature and salinity on larval Pacific lamprey, where elevated water temperatures can affect their development and elevated salinity levels can result in larval mortality. In addition, anthropogenic disturbances such as dams, levees, and culverts have cut off the Columbia River Estuary's floodplain habitats from the mainstem Columbia River, decreased sedimentation rates, and separated adult lamprey from the floodplains and tributaries that they use to spawn. The presence of these barriers in the region can inhibit the distribution of fine sediments in the river, limiting where larval lamprey burrow and develop. The burrowing behavior of larval lamprey has yet to fully be investigated in the Columbia River Estuary. Limited research may be due to the lack of resources for studying Pacific lamprey's life cycle, habitat, and population dynamics since they are not federally designated as an endangered species, like resident salmonid species. This has further added to the challenge of understanding the species and restoring its population to sustainable numbers. To the best of our knowledge, this project is the first to explore spatial and temporal trends of suitable larval Pacific lamprey habitat conditions in the Columbia River Estuary. The Habitat Suitability Analysis provides technical information about the presence and distribution of suitable conditions to address habitat-related uncertainties. The member-tribes of the Columbia River Inter-Tribal Fish Commission and their collaborators can incorporate the information into current and future Pacific lamprey restoration, conservation, and education programs to enhance general understanding of lamprey populations throughout the Columbia River Basin. Key recommendations are provided to address additional knowledge gaps and prioritize future restoration projects in the Columbia River Basin including the refinement of the Habitat Suitability Analysis, evaluation of barrier effects on Pacific lamprey passage, and assessment of climate change scenarios on larval lamprey habitat. The Habitat Suitability Analysis uses salinity, temperature, and geomorphology data to identify suitable larval Pacific lamprey ...

The Habitat Suitability Analysis was built using ArcGIS Pro's ModelBuilder tool. This program does not have an option to save the model's inputs as a relative file path. As a result, the model may not run because it's searching for each layer's original file path. If this happens, we have included a file titled Habitat_Suitability_Analysis_Script that outlines the processes we used to build the model. This submission contains three folders and three supplemental files. The folder titled "Data" includes all of the raw data and data input in the Habitat Suitability Analysis. The folder titled "Scripts" describes the steps to build the Habitat Suitability Analysis model in ArcGIS Pro. The Results folder contains the Habitat Suitability Analysis model and the data that was input into the model. The supplemental files are a file titled "Dryad_Folder_Contents" which describes the contents of every folder in this submission, and a file titled "Habitat_Suitability_Analysis_README" which contain...

This template is used to compute urban growth between two land cover datasets, that are classified into 20 classes based on the Anderson Level II classification system. This raster function template is used to generate a visual representation indicating urbanization across two different time periods. Typical datasets used for this template is the National Land Cover Database. A more detailed blog on the datasets can be found on ArcGIS Blogs. This template works in ArcGIS Pro Version 2.6 and higher. It's designed to work on Enterprise 10.8.1 and higher.References:Raster functionsWhen to use this raster function templateThe template is useful to generate an intuitive visualization of urbanization across two images.Sample Images to test this againstNLCD2006 and NLCD2011How to use this raster function templateIn ArcGIS Pro, search ArcGIS Living Atlas for raster function templates to apply them to your imagery layer. You can also download the raster function template, attach it to a mosaic dataset, and publish it as an image service. The output is a visual representation of urban sprawl across two images. Applicable geographiesThe template is designed to work globally.

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

This model was originally developed in 2016-17 by Henk Pieter Sterk (www.rfase.org), with minor updates in 2021 in ArcGIS Pro 10.7.1 by Stacy Shinneman and Henk Pieter Sterk. Model used to generate publication results: Hierarchical geomorphological mapping in mountainous areas Matheus G.G. De Jong, Henk Pieter Sterk, Stacy Shinneman & Arie C. Seijmonsbergen. Submitted to Journal of Maps 2020, revisions made in 2021.

The Digital Geomorphic-GIS Map of Cape Lookout National Seashore, North Carolina (1:10,000 scale 2008 mapping) is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (calo_geomorphology.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 3.X map file (.mapx) file (calo_geomorphology.mapx) and individual Pro 3.X layer (.lyrx) 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 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.) a readme file (calo_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (calo_geomorphology.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 (calo_geomorphology_metadata_faq.pdf). Please read the calo_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: 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: East Carolina University. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (calo_geomorphology_metadata.txt or calo_geomorphology_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:10,000 and United States National Map Accuracy Standards features are within (horizontally) 8.5 meters or 27.8 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 Pro, 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).