This dataset is a compilation of address point data for the City of Tempe. The dataset contains a point location, the official address (as defined by The Building Safety Division of Community Development) for all occupiable units and any other official addresses in the City. There are several additional attributes that may be populated for an address, but they may not be populated for every address. Contact: Lynn Flaaen-Hanna, Development Services Specialist Contact E-mail Link: Map that Lets You Explore and Export Address Data Data Source: The initial dataset was created by combining several datasets and then reviewing the information to remove duplicates and identify errors. This published dataset is the system of record for Tempe addresses going forward, with the address information being created and maintained by The Building Safety Division of Community Development.Data Source Type: ESRI ArcGIS Enterprise GeodatabasePreparation Method: N/APublish Frequency: WeeklyPublish Method: AutomaticData Dictionary

In this course, you will learn about some common types of data used for GIS mapping and analysis, and practice adding data to a file geodatabase to support a planned project.Goals Create a file geodatabase. Add data to a file geodatabase. Create an empty geodatabase feature class.

You have been assigned a new project, which you have researched, and you have identified the data that you need.The next step is to gather, organize, and potentially create the data that you need for your project analysis.In this course, you will learn how to gather and organize data using ArcGIS Pro. You will also create a file geodatabase where you will store the data that you import and create.After completing this course, you will be able to perform the following tasks:Create a geodatabase in ArcGIS Pro.Create feature classes in ArcGIS Pro by exporting and importing data.Create a new, empty feature class in ArcGIS Pro.

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.

This page contains the help documentation for the GIS Open Data Portal. Refer to https://gisdata-csj.opendata.arcgis.com/pages/help.

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

A listing of web services published from the authoritative East Baton Rouge Parish Geographic Information System (EBRGIS) data repository. Services are offered in Esri REST, and the Open Geospatial Consortium (OGC) Web Mapping Service (WMS) or Web Feature Service (WFS) formats.

Expands the use of internal data for creating Geographic Information System (GIS) maps. SSA's Database Systems division developed a map users guide for GIS data object publishing and was made available in an internal Sharepoint site for access throughout the agency. The guide acts as the reference for publishers of GIS objects across the life-cycle in our single, central geodatabase implementation.

Focus on Geodatabases in ArcGIS Pro introduces readers to the geodatabase, the comprehensive information model for representing and managing geographic information across the ArcGIS platform.Sharing best practices for creating and maintaining data integrity, chapter topics include the careful design of a geodatabase schema, building geodatabases that include data integrity rules, populating geodatabases with existing data, working with topologies, editing data using various techniques, building 3D views, and sharing data on the web. Each chapter includes important concepts with hands-on, step-by-step tutorials, sample projects and datasets, 'Your turn' segments with less instruction, study questions for classroom use, and an independent project. Instructor resources are available by request.AUDIENCEProfessional and scholarly.AUTHOR BIODavid W. Allen has been working in the GIS field for over 35 years, the last 30 with the City of Euless, Texas, and has seen many versions of ArcInfo and ArcGIS come along since he started with version 5. He spent 18 years as an adjunct professor at Tarrant County College in Fort Worth, Texas, and now serves as the State Director of Operations for a volunteer emergency response group developing databases and templates. Mr. Allen is the author of GIS Tutorial 2: Spatial Analysis Workbook (Esri Press, 2016).Pub Date: Print: 6/17/2019 Digital: 4/29/2019 Format: PaperbackISBN: Print: 9781589484450 Digital: 9781589484467 Trim: 7.5 x 9.25 in.Price: Print: $59.99 USD Digital: $59.99 USD Pages: 260

The Digital Geomorphic-GIS Map of the Avon Area (1:24,000 scale 2007 mapping), North Carolina 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 (avon_geomorphology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (avon_geomorphology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (avon_geomorphology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). 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.) A GIS readme file (caha_fora_wrbr_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (caha_fora_wrbr_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 (avon_geomorphology_metadata_faq.pdf). Please read the caha_fora_wrbr_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. 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: North Carolina Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (avon_geomorphology_metadata.txt or avon_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: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 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).

The Digital Geologic-GIS Map of Everglades National Park and Vicinity, Florida 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 (ever_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 (ever_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 (ever_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.) A GIS readme file (ever_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (ever_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 (ever_geology_metadata_faq.pdf). Please read the ever_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: Florida Geological Survey and U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (ever_geology_metadata.txt or ever_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:675,000 and United States National Map Accuracy Standards features are within (horizontally) 342.9 meters or 1125 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).

TransportationThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau, displays primary roads, secondary roads, local roads and railroads in the United States. According to the USCB, "This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways."Interstates 20 and 635Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (TIGERweb/Transportation) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 155 (Series Information for All Roads County-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Transportation - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Census Feature Class Codes (CFCC)For feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

This map presents transportation data, including highways, roads, railroads, and airports for the world.

The map was developed by Esri using Esri highway data; Garmin basemap layers; HERE street data for North America, Europe, Australia, New Zealand, South America and Central America, India, most of the Middle East and Asia, and select countries in Africa. Data for Pacific Island nations and the remaining countries of Africa was sourced from OpenStreetMap contributors. Specific country list and documentation of Esri's process for including OSM data is available to view.

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

Our self-hosted GIS data cover administrative and postal divisions with up to 6 precision levels: a zip code layer and up to 5 administrative levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.

The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

Use cases for the Global Boundaries Database (GIS data, Geospatial data)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

• Reporting and Business Intelligence (BI)

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Fast-loading polygons for reporting and BI

• Multi-language support

For additional insights, you can combine the GIS data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our geospatial data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All GIS data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

This layer features special areas of interest (AOIs) that have been contributed to Esri Community Maps using the new Community Maps Editor app. The data that is accepted by Esri will be included in selected Esri basemaps, including our suite of Esri Vector Basemaps, and made available through this layer to export and use offline. Export DataThe contributed data is also available for contributors and other users to export (or extract) and re-use for their own purposes. Users can export the full layer from the ArcGIS Online item details page by clicking the Export Data button and selecting one of the supported formats (e.g. shapefile, or file geodatabase (FGDB)). User can extract selected layers for an area of interest by opening in Map Viewer, clicking the Analysis button, viewing the Manage Data tools, and using the Extract Data tool. To display this data with proper symbology and metadata in ArcGIS Pro, you can download and use this layer file.Data UsageThe data contributed through the Community Maps Editor app is primarily intended for use in the Esri Basemaps. Esri staff will periodically (e.g. weekly) review the contents of the contributed data and either accept or reject the data for use in the basemaps. Accepted features will be added to the Esri basemaps in a subsequent update and will remain in the app for the contributor or others to edit over time. Rejected features will be removed from the app.Esri Community Maps Contributors and other ArcGIS Online users can download accepted features from this layer for their internal use or map publishing, subject to the terms of use below.

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

This data set contains small-scale base GIS data layers compiled by the National Park Service Servicewide Inventory and Monitoring Program and Water Resources Division for use in a Baseline Water Quality Data Inventory and Analysis Report that was prepared for the park. The report presents the results of surface water quality data retrievals for the park from six of the United States Environmental Protection Agency's (EPA) national databases: (1) Storage and Retrieval (STORET) water quality database management system; (2) River Reach File (RF3) Hydrography; (3) Industrial Facilities Discharges; (4) Drinking Water Supplies; (5) Water Gages; and (6) Water Impoundments. The small-scale GIS data layers were used to prepare the maps included in the report that depict the locations of water quality monitoring stations, industrial discharges, drinking intakes, water gages, and water impoundments. The data layers included in the maps (and this dataset) vary depending on availability, but generally include roads, hydrography, political boundaries, USGS 7.5' minute quadrangle outlines, hydrologic units, trails, and others as appropriate. The scales of each layer vary depending on data source but are generally 1:100,000.

Crowther_Nature_Files.zip This description pertains to the original download. Details on revised (newer) versions of the datasets are listed below. When more than one version of a file exists in Figshare, the original DOI will take users to the latest version, though each version technically has its own DOI. -- Two global maps (raster files) of tree density. These maps highlight how the number of trees varies across the world. One map was generated using biome-level models of tree density, and applied at the biome scale. The other map was generated using ecoregion-level models of tree density, and applied at the ecoregion scale. For this reason, transitions between biomes or between ecoregions may be unrealistically harsh, but large-scale estimates are robust (see Crowther et al 2015 and Glick et al 2016). At the outset, this study was intended to generate reliable estimates at broad spatial scales, which inherently comes at the cost of fine-scale precision. For this reason, country-scale (or larger) estimates are generally more robust than individual pixel-level estimates. Additionally, due to data limitations, estimates for Mangroves and Tropical coniferous forest (as identified by WWF and TNC) were generated using models constructed from Topical moist broadleaf forest data and Temperate coniferous forest data, respectively. Because we used ecological analogy, the estimates for these two biomes should be considered less reliable than those of other biomes . These two maps initially appeared in Crowther et al (2015), with the biome map being featured more prominently. Explicit publication of the data is associated with Glick et al (2016). As they are produced, updated versions of these datasets, as well as alternative formats, will be made available under Additional Versions (see below).

Methods: We collected over 420,000 ground-sources estimates of tree density from around the world. We then constructed linear regression models using vegetative, climatic, topographic, and anthropogenic variables to produce forest tree density estimates for all locations globally. All modeling was done in R. Mapping was done using R and ArcGIS 10.1.

Viewing Instructions: Load the files into an appropriate geographic information system (GIS). For the original download (ArcGIS geodatabase files), load the files into ArcGIS to view or export the data to other formats. Because these datasets are large and have a unique coordinate system that is not read by many GIS, we suggest loading them into an ArcGIS dataframe whose coordinate system matches that of the data (see File Format). For GeoTiff files (see Additional Versions), load them into any compatible GIS or image management program.

Comments: The original download provides a zipped folder that contains (1) an ArcGIS File Geodatabase (.gdb) containing one raster file for each of the two global models of tree density – one based on biomes and one based on ecoregions; (2) a layer file (.lyr) for each of the global models with the symbology used for each respective model in Crowther et al (2015); and an ArcGIS Map Document (.mxd) that contains the layers and symbology for each map in the paper. The data is delivered in the Goode homolosine interrupted projected coordinate system that was used to compute biome, ecoregion, and global estimates of the number and density of trees presented in Crowther et al (2015). To obtain maps like those presented in the official publication, raster files will need to be reprojected to the Eckert III projected coordinate system. Details on subsequent revisions and alternative file formats are list below under Additional Versions.----------

Additional Versions: Crowther_Nature_Files_Revision_01.zip contains tree density predictions for small islands that are not included in the data available in the original dataset. These predictions were not taken into consideration in production of maps and figures presented in Crowther et al (2015), with the exception of the values presented in Supplemental Table 2. The file structure follows that of the original data and includes both biome- and ecoregion-level models.

Crowther_Nature_Files_Revision_01_WGS84_GeoTiff.zip contains Revision_01 of the biome-level model, but stored in WGS84 and GeoTiff format. This file was produced by reprojecting the original Goode homolosine files to WGS84 using nearest neighbor resampling in ArcMap. All areal computations presented in the manuscript were computed using the Goode homolosine projection. This means that comparable computations made with projected versions of this WGS84 data are likely to differ (substantially at greater latitudes) as a product of the resampling. Included in this .zip file are the primary .tif and its visualization support files.

References:

Crowther, T. W., Glick, H. B., Covey, K. R., Bettigole, C., Maynard, D. S., Thomas, S. M., Smith, J. R., Hintler, G., Duguid, M. C., Amatulli, G., Tuanmu, M. N., Jetz, W., Salas, C., Stam, C., Piotto, D., Tavani, R., Green, S., Bruce, G., Williams, S. J., Wiser, S. K., Huber, M. O., Hengeveld, G. M., Nabuurs, G. J., Tikhonova, E., Borchardt, P., Li, C. F., Powrie, L. W., Fischer, M., Hemp, A., Homeier, J., Cho, P., Vibrans, A. C., Umunay, P. M., Piao, S. L., Rowe, C. W., Ashton, M. S., Crane, P. R., and Bradford, M. A. 2015. Mapping tree density at a global scale. Nature, 525(7568): 201-205. DOI: http://doi.org/10.1038/nature14967Glick, H. B., Bettigole, C. B., Maynard, D. S., Covey, K. R., Smith, J. R., and Crowther, T. W. 2016. Spatially explicit models of global tree density. Scientific Data, 3(160069), doi:10.1038/sdata.2016.69.

This layer represents streams, rivers, and similar linear features that have been defined by the ADEC via qualitative and quantitative data. These features are noted in the 2014/2016 Integrated Report and currently being actively monitored or have institutional controls (TMDLs) in place, and are classified as Category 4a, 4b, or Category 5 under Section 303(d) of the Clean Water Act (1987). These 2014/2016 Impaired Waters should be used for regulatory purposes.

The Digital Geologic-GIS Map of Sagamore Hill National Historic Site and Vicinity, New York 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 (sahi_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 (sahi_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 (sahi_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.) A GIS readme file (sahi_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (sahi_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 (sahi_geology_metadata_faq.pdf). Please read the sahi_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: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sahi_geology_metadata.txt or sahi_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:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 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).