MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Checklist to help Managers of large organisations to migrate to ArcGIS Pro. This document assumes the following:the organisation migrating has a Project Management Officethe IT department managers software installsArcGIS Pro is going to be used by people in multiple teams across the organisation
An ArcGIS Pro project may contain maps, scenes, layouts, data, tools, and other items. It may contain connections to folders, databases, and servers. Content can be added from online portals such as your ArcGIS organization or the ArcGIS Living Atlas of the World.In this tutorial, you'll create a new, blank ArcGIS Pro project. You'll add a map to the project and convert the map to a 3D scene.Estimated time: 10 minutesSoftware requirements: ArcGIS Pro
Attribution-NonCommercial-ShareAlike 3.0 (CC BY-NC-SA 3.0)https://creativecommons.org/licenses/by-nc-sa/3.0/
License information was derived automatically
The arrival of ArcGIS Pro has brought a challenge to ArcMap users. The new software is sufficiently different in architecture and layout that switching from the old to the new is not a simple process. In some ways, Pro is harder to learn for ArcMap users than for new GIS users, because some workflows have to be unlearned, or at least heavily modified. Current ArcMap users are pressed for time, trying to learn the new software while still completing their daily tasks, so a book that teaches Pro from the start is not an efficient method.Switching to ArcGIS Pro from ArcMap aims to quickly transition ArcMap users to ArcGIS Pro. Rather than teaching Pro from the start, as for a novice user, this book focuses on how Pro is different from ArcMap. Covering the most common and important workflows required for most GIS work, it leverages the user’s prior experience to enable a more rapid adjustment to Pro.AUDIENCEProfessional and scholarly; College/higher education; General/trade.AUTHOR BIOMaribeth H. Price, PhD, South Dakota School of Mines and Technology, has been using Esri products since 1991, teaching college GIS since 1995 and writing textbooks utilizing Esri’s software since 2001. She has extensive familiarity with both ArcMap/ArcCatalog and Pro, both as a user and in the classroom, as well as long experience writing about GIS concepts and developing software tutorials. She teaches GIS workshops, having offered more than 100 workshops to over 1,200 participants since 2000.Pub Date: Print: 2/14/2019 Digital: 1/28/2019 Format: PaperbackISBN: Print: 9781589485440 Digital: 9781589485457 Trim: 8 x 10 in.Price: Print: $49.99 USD Digital: $49.99 USD Pages: 172Table of ContentsPreface1 Contemplating the switch to ArcGIS ProBackgroundSystem requirementsLicensingCapabilities of ArcGIS ProWhen should I switch?Time to exploreObjective 1.1: Downloading the data for these exercisesObjective 1.2: Starting ArcGIS Pro, signing in, creating a project, and exploring the interfaceObjective 1.3: Accessing maps and data from ArcGIS OnlineObjective 1.4: Arranging the windows and panesObjective 1.5: Accessing the helpObjective 1.6: Importing a map document2 Unpacking the GUIBackgroundThe ribbon and tabsPanesViewsTime to exploreObjective 2.1: Getting familiar with the Contents paneObjective 2.2: Learning to work with objects and tabsObjective 2.3: Exploring the Catalog pane3 The projectBackgroundWhat is a project?Items stored in a projectPaths in projectsRenaming projectsTime to exploreObjective 3.1: Exploring different elements of a projectObjective 3.2: Accessing properties of projects, maps, and other items4 Navigating and exploring mapsBackgroundExploring maps2D and 3D navigationTime to exploreObjective 4.1: Learning to use the Map toolsObjective 4.2: Exploring 3D scenes and linking views5 Symbolizing mapsBackgroundAccessing the symbol settings for layersAccessing the labeling propertiesSymbolizing rastersTime to exploreObjective 5.1: Modifying single symbolsObjective 5.2: Creating maps from attributesObjective 5.3: Creating labelsObjective 5.4: Managing labelsObjective 5.5: Symbolizing rasters6 GeoprocessingBackgroundWhat’s differentAnalysis buttons and toolsTool licensingTime to exploreObjective 6.1: Getting familiar with the geoprocessing interfaceObjective 6.2: Performing interactive selectionsObjective 6.3: Performing selections based on attributesObjective 6.4: Performing selections based on locationObjective 6.5: Practicing geoprocessing7 TablesBackgroundGeneral table characteristicsJoining and relating tablesMaking chartsTime to exploreObjective 7.1: Managing table viewsObjective 7.2: Creating and managing properties of a chartObjective 7.3: Calculating statistics for tablesObjective 7.4: Calculating and editing in tables8 LayoutsBackgroundLayouts and map framesLayout editing proceduresImporting map documents and templatesTime to exploreObjective 8.1: Creating the maps for the layoutObjective 8.2: Setting up a layout page with map framesObjective 8.3: Setting map frame extent and scaleObjective 8.4: Formatting the map frameObjective 8.5: Creating and formatting map elementsObjective 8.6: Fine-tuning the legendObjective 8.7: Accessing and copying layouts9 Managing dataBackgroundData modelsManaging the geodatabase schemaCreating domainsManaging data from diverse sourcesProject longevityManaging shared data for work groupsTime to exploreObjective 9.1: Creating a project and exporting data to itObjective 9.2: Creating feature classesObjective 9.3: Creating and managing metadataObjective 9.4: Creating fields and domainsObjective 9.5: Modifying the table schemaObjective 9.6: Sharing data using ArcGIS Online10 EditingBackgroundBasic editing functionsCreating featuresModifying existing featuresCreating and editing annotationTime to exploreObjective 10.1: Understanding the editing tools in ArcGIS ProObjective 10.2: Creating pointsObjective 10.3: Creating linesObjective 10.4: Creating polygonsObjective 10.5: Modifying existing featuresObjective 10.6: Creating an annotation feature classObjective 10.7: Editing annotationObjective 10.8: Creating annotation features11 Moving forwardData sourcesIndex
The establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making.
BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions.
Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself.
For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise.
Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer.
This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery.
See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt
See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt
Mosaics are published as ArcGIS image serviceswhich circumvent the need to download or order data. GEO-IDS image services are different from standard web services as they provide access to the raw imagery data. This enhances user experiences by allowing for user driven dynamic area of interest image display enhancement, raw data querying through tools such as the ArcPro information tool, full geospatial analysis, and automation through scripting tools such as ArcPy.Image services are best accessed through the ArcGIS REST APIand REST endpoints (URL's). You can copy the OPS ArcGIS REST API link below into a web browser to gain access to a directory containing all OPS image services. Individual services can be added into ArcPro for display and analysis by using Add Data -> Add Data From Path and copying one of the image service ArcGIS REST endpoint below into the resultant text box. They can also be accessed by setting up an ArcGIS server connectionin ESRI software using the ArcGIS Image Server REST endpoint/URL. Services can also be accessed in open-source software. For example, in QGIS you can right click on the type of service you want to add in the browser pane (e.g., ArcGIS REST Server, WCS, WMS/WMTS) and copy and paste the appropriate URL below into the resultant popup window. All services are in Web Mercator projection.For more information on what functionality is available and how to work with the service, read the Ontario Web Raster Services User Guide. If you have questions about how to use the service, email Geospatial Ontario (GEO) at geospatial@ontario.caAvailable Products:ArcGIS REST APIhttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/Image Service ArcGIS REST endpoint / URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServerhttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer https://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServerWeb Coverage Services (WCS) URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer/WCSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer/WCSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServer/WCSServer/Web Mapping Service (WMS) URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer/WMSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer/WMSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServer/WMSServer/Metadata for all imagery products available in GEO-IDS can be accessed at the links below:South Central Ontario Orthophotography Project (SCOOP) 2023North-Western Ontario Orthophotography Project (NWOOP) 2022Central Ontario Orthophotography Project (COOP) 2021South-Western Ontario Orthophotography Project (SWOOP) 2020Digital Raster Acquisition Project Eastern Ontario (DRAPE) 2019-2020South Central Ontario Orthophotography Project (SCOOP) 2018North-Western Ontario Orthophotography Project (NWOOP) 2017Central Ontario Orthophotography Project (COOP) 2016South-Western Ontario Orthophotography Project (SWOOP) 2015Algonquin Orthophotography Project (2015)Additional Documentation:Ontario Web Raster Services User Guide (Word)Status:Completed: Production of the data has been completed Maintenance and Update Frequency:Annually: Data is updated every yearContact:Geospatial Ontario (GEO), geospatial@ontario.ca
To create this app:
Created to map completed transportation projects funded with 2008 Keep Salem Moving bond measure. This layer is intended to be used within the "Keep Salem Moving! - Updates" web experience app and associated maps to share project updates with the public.Maintained by RRegutti@cityofsalem.net for Keep Salem Moving! project updates.
Data layers that will be used in the public facing appliation and dashboards
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This map references the OpenStreetMap tile layer hosted by Esri. This tile layer presents a new vector basemap of OpenStreetMap (OSM) data created and hosted by Esri, now in beta release. Esri produced this vector tile basemap in ArcGIS Pro from a live replica of OSM data, hosted by Esri, that was rendered using OSM cartography. The vector tiles are updated every few weeks; refer to the OpenStreetMap tile layer for details on when it was last updated. When fully released, this vector basemap will be 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 downloadable ZIP file contains model documentation and contact information for the model creator. For more information, or a copy of the project report which provides greater model detail, please contact Ryan Urie - traigo12@gmail.com.This model was created from February through April 2010 as a central component of the developer's master's project in Bioregional Planning and Community Design at the University of Idaho to provide a tool for identifying appropriate locations for various land uses based on a variety of user-defined social, economic, ecological, and other criteria. It was developed using the Land-Use Conflict Identification Strategy developed by Carr and Zwick (2007). The purpose of this model is to allow users to identify suitable locations within a user-defined extent for any land use based on any number of social, economic, ecological, or other criteria the user chooses. The model as it is currently composed was designed to identify highly suitable locations for new residential, commercial, and industrial development in Kootenai County, Idaho using criteria, evaluations, and weightings chosen by the model's developer. After criteria were chosen, one or more data layers were gathered for each criterion from public sources. These layers were processed to result in a 60m-resolution raster showing the suitability of each criterion across the county. These criteria were ultimately combined with a weighting sum to result in an overall development suitability raster. The model is intended to serve only as an example of how a GIS-based land-use suitability analysis can be conceptualized and implemented using ArcGIS ModelBuilder, and under no circumstances should the model's outputs be applied to real-world decisions or activities. The model was designed to be extremely flexible so that later users may determine their own land-use suitability, suitability criteria, evaluation rationale, and criteria weights. As this was the first project of its kind completed by the model developer, no guarantees are made as to the quality of the model or the absence of errorsThis model has a hierarchical structure in which some forty individual land-use suitability criteria are combined by weighted summation into several land-use goals which are again combined by weighted summation to yield a final land-use suitability layer. As such, any inconsistencies or errors anywhere in the model tend to reveal themselves in the final output and the model is in a sense self-testing. For example, each individual criterion is presented as a raster with values from 1-9 in a defined spatial extent. Inconsistencies at any point in the model will reveal themselves in the final output in the form of an extent different from that desired, missing values, or values outside the 1-9 range.This model was created using the ArcGIS ModelBuilder function of ArcGIS 9.3. It was based heavily on the recommendations found in the text "Smart land-use analysis: the LUCIS model." The goal of the model is to determine the suitability of a chosen land-use at each point across a chosen area using the raster data format. In this case, the suitability for Development was evaluated across the area of Kootenai County, Idaho, though this is primarily for illustrative purposes. The basic process captured by the model is as follows: 1. Choose a land use suitability goal. 2. Select the goals and criteria that define this goal and get spatial data for each. 3. Use the gathered data to evaluate the quality of each criterion across the landscape, resulting in a raster with values from 1-9. 4. Apply weights to each criterion to indicate its relative contribution to the suitability goal. 5. Combine the weighted criteria to calculate and display the suitability of this land use at each point across the landscape. An individual model was first built for each of some forty individual criteria. Once these functioned successfully, individual criteria were combined with a weighted summation to yield one of three land-use goals (in this case, Residential, Commercial, or Industrial). A final model was then constructed to combined these three goals into a final suitability output. In addition, two conditional elements were placed on this final output (one to give already-developed areas a very high suitability score for development [a "9"] and a second to give permanently conserved areas and other undevelopable lands a very low suitability score for development [a "1"]). Because this model was meant to serve primarily as an illustration of how to do land-use suitability analysis, the criteria, evaluation rationales, and weightings were chosen by the modeler for expediency; however, a land-use analysis meant to guide real-world actions and decisions would need to rely far more heavily on a variety of scientific and stakeholder input.
The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. An ArcInfo(tm) (ESRI) GIS database was designed for WICA using the National Park GIS Database Design, Layout, and Procedures created by the BOR. This was created through Arc Macro Language (AML) scripts that helped automate the transfer process and ensure that all spatial and attribute data was consistent and stored properly. Actual transfer of information from the interpreted aerial photographs to a digital, geo-referenced format involved two techniques, scanning (for the vegetation classes) and on-screen digitizing (for the land-use classes). Both techniques required the use of 14 digital black-and-white orthophoto quarter quadrangles (DOQQ's) covering the study area. Transferred information was used to create vegetation polygon coverages and ancillary linear coverages in ArcInfo(tm) for each WICA DOQQ. Attribute information including vegetation map unit, location, and aerial photo number was subsequently entered for all polygons.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Household formation by scenario, local authority and year, for the 4 scenarios described in the project methodology for the years 2017-2040 https://www.esri.ie/publications/regional-demographics-and-structural-housing-demand-at-a-county-level The 4 scenarios are: Baseline/Business as usual - based on medium term projections for the economy with an underlying assumption that net inwards migration would converge to 15,000 p.a. by 2024 and remain at that level throughout the projection horizon. 50:50 City - based on a similar outlook in terms of net inwards migration but whereby population growth is distributed in line with the objectives of the National Planning Framework (See National Policy Objectives 1a and 2a of https://npf.ie/wp-content/uploads/Project-Ireland-2040-NPF.pdf) High Migration - assumes that net inwards migration stays at an elevated level throughout the projection horizon (net inwards migration of 30,000 p.a) Low Migration - assumes that net inwards migration falls to net inwards migration of 5,000 by 2022 before converging back to the business as usual levels (i.e. net inwards migration of 15,000 p.a.) by 2027 and remaining at that level thereafter.
Attribution-ShareAlike 4.0 (CC BY-SA 4.0)https://creativecommons.org/licenses/by-sa/4.0/
License information was derived automatically
The 4 scenarios are: Baseline/Business as usual – based on medium term projections for the economy with an underlying assumption that net inwards migration would converge to 15,000 p.a. by 2024 and remain at that level throughout the projection horizon. 50:50 City – based on a similar outlook in terms of net inwards migration but whereby population growth is distributed in line with the objectives of the National Planning Framework (See National Policy Objectives 1a and 2a of https://npf.ie/wp-content/uploads/Project-Ireland-2040-NPF.pdf) High Migration – assumes that net inwards migration stays at an elevated level throughout the projection horizon (net inwards migration of 30,000 p.a) Low Migration - assumes that net inwards migration falls to net inwards migration of 5,000 by 2022 before converging back to the business as usual levels (i.e. net inwards migration of 15,000 p.a.) by 2027 and remaining at that level thereafter.
Feature layer generated from running the Join Features solution
Population projection by scenario, year of age and local authority, for the 4 scenarios described in the project methodology for years 2017-2040. https://www.esri.ie/publications/regional-demographics-and-structural-housing-demand-at-a-county-level The 4 scenarios are: Baseline/Business as usual – based on medium term projections for the economy with an underlying assumption that net inwards migration would converge to 15,000 p.a. by 2024 and remain at that level throughout the projection horizon. 50:50 City – based on a similar outlook in terms of net inwards migration but whereby population growth is distributed in line with the objectives of the National Planning Framework (See National Policy Objectives 1a and 2a of https://npf.ie/wp-content/uploads/Project-Ireland-2040-NPF.pdf) High Migration – assumes that net inwards migration stays at an elevated level throughout the projection horizon (net inwards migration of 30,000 p.a) Low Migration - assumes that net inwards migration falls to net inwards migration of 5,000 by 2022 before converging back to the business as usual levels (i.e. net inwards migration of 15,000 p.a.) by 2027 and remaining at that level thereafter.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This vector webmap presents a new 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. It provides a detailed base layer for the world featuring a light neutral style with minimal colors, OpenStreetMap (Light Gray Canvas Base - WGS84) and also an overlaying reference layer, OpenStreetMap (Light Gray Canvas Reference - WGS84). The vector tiles will be updated quarterly 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.Precise Tile Registration: The tile layer uses the improved tiling scheme “WGS84 Geographic, Version 2” to ensure proper tile positioning at higher resolutions (neighborhood level and beyond). The new tiling scheme is much more precise than tiling schemes of the legacy basemaps Esri released years ago. We recommend that you start using this new basemap for any new web maps in WGS84 that you plan to author. Due to the number of differences between the old and new tiling schemes, some web clients will not be able to overlay tile layers in the old and new tiling schemes in one web map.
The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. To produce a USNVC association-level vegetation map that satisfied the standards of the USGS/NPS Vegetation Mapping Program, the alliance-level vegetation map developed by Agius was edited and refined onscreen in ArcGIS 9.1. The Agius (2003b) vegetation map was not developed following the USGS/NPS Vegetation Mapping Program standards and therefore could not be used as the final vegetation classification map. Polygons that represented vegetation were readily attributed to existing associations in the U.S. National Vegetation Classification. Polygons that represented intensive land uses were attributed with names modified from the Anderson Level II categories.. Because Saugus Iron Works National Historic Park is a small park with only 21 polygons, the mapping did not rely entirely on aerial photograph interpretation, but also incorporated lines sketched onto a hard-copy map on site. Using ArcGIS 9.1, polygon boundaries were drawn onscreen based on the plot data and additional field observations. Each polygon was attributed with the name of an USNVC association or an Anderson Level II (modified) land use/land cover map class based on plot data, field observations, aerial photography signatures, and topographic maps. The shapefile was projected in Universal Transverse Mercator Zone 19 North, North American Datum 1983, meters, in ArcGIS 9.1.
This dataset contains an ESRI Geotiff with 9 meter cell size representing the bathymetry of selected portions of seafloor around Tourmaline Bank in Puerto Rico, derived from data collected in 2008. NOAA's NOS/NCCOS/CCMA Biogeography Branch, in collaboration with NOAA vessel Nancy Foster and territory, federal, and private sector partners, acquired multibeam bathymetry data in Puerto Rico from 2/25/08 to 3/8/08. Data was acquired with a hull-mounted Kongsberg Simrad EM 1002 multibeam echosounder (95 kHz) in 2008. It was processed by a NOAA contractor using CARIS HIPS software. Data has all correctors applied (attitude, sound velocity) and has been reduced to mean lower low water (MLLW) using final approved tides and zoning from NOAA COOPS. Data is in UTM zone 19 north, datum NAD83. The processed CARIS data was used to generate a CARIS BASE surface based on swath angle. An ASCII XYZ file was exported from the BASE surface and imported to ESRI ArcMap 9.2 using the 'Convert XYZ to Raster' tool developed by CCMA for this purpose. This was used to produce the final bathymetry geotiff. The project was conducted to meet IHO Order 1 and 2 accuracy standards, dependent on the project area and depth. All users should individually evaluate the suitability of this data according to their own needs and standards.
This item relates to a research project funded by a US Geological Survey Climate Adaptation Science Center. Items found on Arcgis Online are for educational purposes only. Information on the project and the data relating to this item can be found here. Contact the project investigators for more information.
Web map illustrating the locations and details of potential USFS infrastructure projects.Created by the Utah Division of Wildlife Resources, May 2022.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Checklist to help Managers of large organisations to migrate to ArcGIS Pro. This document assumes the following:the organisation migrating has a Project Management Officethe IT department managers software installsArcGIS Pro is going to be used by people in multiple teams across the organisation