Have you ever wanted to create your own maps, or integrate and visualize spatial datasets to examine changes in trends between locations and over time? Follow along with these training tutorials on QGIS, an open source geographic information system (GIS) and learn key concepts, procedures and skills for performing common GIS tasks – such as creating maps, as well as joining, overlaying and visualizing spatial datasets. These tutorials are geared towards new GIS users. We’ll start with foundational concepts, and build towards more advanced topics throughout – demonstrating how with a few relatively easy steps you can get quite a lot out of GIS. You can then extend these skills to datasets of thematic relevance to you in addressing tasks faced in your day-to-day work.

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.

This is a link to the QGIS website where you can download open-source GIS software for viewing, analyzing and manipulating geodata like our downloadable shapefiles.

This resources contains PDF files and Python notebook files that demonstrate how to create geospatial resources in HydroShare and how to use these resources through web services provided by the built-in HydroShare GeoServer instance. Geospatial resources can be consumed directly into ArcMap, ArcGIS, Story Maps, Quantum GIS (QGIS), Leaflet, and many other mapping environments. This provides HydroShare users with the ability to store data and retrieve it via services without needing to set up new data services. All tutorials cover how to add WMS and WFS connections. WCS connections are available for QGIS and are covered in the QGIS tutorial. The tutorials and examples provided here are intended to get the novice user up-to-speed with WMS and GeoServer, though we encourage users to read further on these topic using internet searches and other resources. Also included in this resource is a tutorial designed to that walk users through the process of creating a GeoServer connected resource.

The current list of available tutorials: - Creating a Resource - ArcGIS Pro - ArcMap - ArcGIS Story Maps - QGIS - IpyLeaflet - Folium

ArcGIS tool and tutorial to convert the shapefiles into network format. The latest version of the tool is available at http://csun.uic.edu/codes/GISF2E.htmlUpdate: we now have added QGIS and python tools. To download them and learn more, visit http://csun.uic.edu/codes/GISF2E.htmlPlease cite: Karduni,A., Kermanshah, A., and Derrible, S., 2016, "A protocol to convert spatial polyline data to network formats and applications to world urban road networks", Scientific Data, 3:160046, Available at http://www.nature.com/articles/sdata201646

In this course, you will explore a variety of open-source technologies for working with geosptial data, performing spatial analysis, and undertaking general data science. The first component of the class focuses on the use of QGIS and associated technologies (GDAL, PROJ, GRASS, SAGA, and Orfeo Toolbox). The second component of the class introduces Python and associated open-source libraries and modules (NumPy, Pandas, Matplotlib, Seaborn, GeoPandas, Rasterio, WhiteboxTools, and Scikit-Learn) used by geospatial scientists and data scientists. We also provide an introduction to Structured Query Language (SQL) for performing table and spatial queries. This course is designed for individuals that have a background in GIS, such as working in the ArcGIS environment, but no prior experience using open-source software and/or coding. You will be asked to work through a series of lecture modules and videos broken into several topic areas, as outlined below. Fourteen assignments and the required data have been provided as hands-on opportunites to work with data and the discussed technologies and methods. If you have any questions or suggestions, feel free to contact us. We hope to continue to update and improve this course. This course was produced by West Virginia View (http://www.wvview.org/) with support from AmericaView (https://americaview.org/). This material is based upon work supported by the U.S. Geological Survey under Grant/Cooperative Agreement No. G18AP00077. The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the opinions or policies of the U.S. Geological Survey. Mention of trade names or commercial products does not constitute their endorsement by the U.S. Geological Survey. After completing this course you will be able to: apply QGIS to visualize, query, and analyze vector and raster spatial data. use available resources to further expand your knowledge of open-source technologies. describe and use a variety of open data formats. code in Python at an intermediate-level. read, summarize, visualize, and analyze data using open Python libraries. create spatial predictive models using Python and associated libraries. use SQL to perform table and spatial queries at an intermediate-level.

Overview:This document describes the 2021 accessibility data released by the Accessibility Observatory at the University of Minnesota. The data are included in the National Accessibility Evaluation Project for 2021, and this information can be accessed for each state in the U.S. at https://access.umn.edu/research/america. The following sections describe the format, naming, and content of the data files.Data Formats: The data files are provided in a Geopackage format. Geopackage (.gpkg) files are an open-source, geospatial filetype that can contain multiple layers of data in a single file, and can be opened with most GIS software, including both ArcGIS and QGIS.Within this zipfile, there are six geopackage files (.gpkg) structured as follows. Each of them contains the blocks shapes layer, results at the block level for all LEHD variables (jobs and workers), with a layer of results for each travel time (5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 minutes). {MPO ID}_tr_2021_0700-0859-avg.gpkg = Average Transit Access Departing Every Minute 7am-9am{MPO ID}_au_2021_08.gpkg = Average Auto Access Departing 8am{MPO ID}_bi_2021_1200_lts1.gpkg = Average Bike Access on LTS1 Network{MPO ID}_bi_2021_1200_lts2.gpkg = Average Bike Access on LTS2 Network{MPO ID}_bi_2021_1200_lts3.gpkg = Average Bike Access on LTS3 Network{MPO ID}_bi_2021_1200_lts4.gpkg = Average Bike Access on LTS4 NetworkFor mapping and geospatial analysis, the blocks shape layer within each geopackage can be joined to the blockid of the access attribute data. Opening and Using Geopackages in ArcGIS:Unzip the zip archiveUse the "Add Data" function in Arc to select the .gpkg fileSelect which layer(s) are needed — always select "main.blocks" as this layer contains the Census block shapes; select any other attribute data layers as well.There are three types of layers in the geopackage file — the "main.blocks" layer is the spatial features layer, and all other layers are either numerical attribute data tables, or the "fieldname_descriptions" metadata layer. The numerical attribute layers are named with the following format:[mode]_[threshold]_minutes[mode] is a two-character code indicating the transport mode used[threshold] is an integer indicating the travel time threshold used for this data layerTo use the data spatially, perform a join between the "main.blocks" layer and the desired numerical data layer, using either the numerical "id" fields, or 15-digit "blockid" fields as join fields.

The Digital Geologic-GIS Map of the Craters of the Moon National Monument Area, Idaho 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 (cotm_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 3.X map file (.mapx) file (cotm_geology.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 (crmo_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (crmo_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 (cotm_geology_metadata_faq.pdf). Please read the crmo_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: 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 (cotm_geology_metadata.txt or cotm_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 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).

AbstractCoastline for Antarctica created from various mapping and remote sensing sources, provided as polygons with ‘land’, ‘ice shelf’, ‘ice tongue’ or ‘rumple’ attribute. Covering all land and ice shelves south of 60°S. Suitable for topographic mapping and analysis. This dataset has been generalised from the high resolution vector polygons. Medium resolution versions of ADD data are suitable for scales smaller than 1:1,000,000, although certain regions will appear more detailed than others due to variable data availability and coastline characteristics.Changes in v7.10 include updates to the coastline of Alexander Island and surrounding islands, and the ice shelf fronts of the Wilkins and Brunt ice shelves.Data compiled, managed and distributed by the Mapping and Geographic Information Centre and the UK Polar Data Centre, British Antarctic Survey on behalf of the Scientific Committee on Antarctic Research.Further information and useful linksMap projection: WGS84 Antarctic Polar Stereographic, EPSG 3031. Note: by default, opening this layer in the Map Viewer will display the data in Web Mercator. To display this layer in its native projection use an Antarctic basemap.The currency of this dataset is November 2024 and will be reviewed every 6 months. This feature layer will always reflect the most recent version.For more information on, and access to other Antarctic Digital Database (ADD) datasets, refer to the SCAR ADD data catalogue.A related high resolution dataset is also published via Living Atlas, as well medium and high resolution line datasets.For background information on the ADD project, please see the British Antarctic Survey ADD project page.LineageDataset compiled from a variety of Antarctic map and satellite image sources. The dataset was created using ArcGIS and QGIS GIS software programmes and has been checked for basic topography and geometry checks, but does not contain strict topology. Quality varies across the dataset and certain areas where high resolution source data were available are suitable for large scale maps whereas other areas are only suitable for smaller scales. Each polygon contains a ‘surface’ attribute with either ‘land’, ‘ice shelf’, ‘ice tongue’ or ‘rumple’. Details of when and how each line was created can be found in the attributes of the high or medium resolution polyline coastline dataset. Data sources range in time from 1990s-2024 - individual lines contain exact source dates. This medium resolution version has been generalised from the high resolution version. All polygons <0.1km² not intersecting anything else were deleted and the ‘simplify’ tool was used in ArcGIS with the ‘retain critical points’ algorithm and a smoothing tolerance of 50 m.CitationGerrish, L., Ireland, L., Fretwell, P., & Cooper, P. (2024). Medium resolution vector polygons of the Antarctic coastline (Version 7.10) [Data set]. NERC EDS UK Polar Data Centre. https://doi.org/10.5285/93ac35af-9ec7-4594-9aaa-0760a2b289d5If using for a graphic or if short on space, please cite as 'data from the SCAR Antarctic Digital Database, 2024'

Notice: this is not the latest Heat Island Severity image service.This layer contains the relative heat severity for every pixel for every city in the United States, including Alaska, Hawaii, and Puerto Rico. Heat Severity is a reclassified version of Heat Anomalies raster which is also published on this site. This data is generated from 30-meter Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2023.To explore previous versions of the data, visit the links below:Heat Severity - USA 2022Heat Severity - USA 2021Heat Severity - USA 2020Heat Severity - USA 2019Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter than the average temperature for that same city as a whole. Severity is measured on a scale of 1 to 5, with 1 being a relatively mild heat area (slightly above the mean for the city), and 5 being a severe heat area (significantly above the mean for the city). The absolute heat above mean values are classified into these 5 classes using the Jenks Natural Breaks classification method, which seeks to reduce the variance within classes and maximize the variance between classes. Knowing where areas of high heat are located can help a city government plan for mitigation strategies.This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.

The Digital Geologic-GIS Map of the Rozel Quadrangle, Utah 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 (roze_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 3.X map file (.mapx) file (roze_geology.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 (gosp_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (gosp_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 (roze_geology_metadata_faq.pdf). Please read the gosp_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: 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 (roze_geology_metadata.txt or roze_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 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).

The Los Angeles County Storm Drain System is a geometric network model representing the storm drain infrastructure within Los Angeles County. The long term goal of this network is to seamlessly integrate the countywide drainage infrastructure, regardless of ownership or jurisdiction. Current uses by the Department of Public Works (DPW) include asset inventory, operational maintenance, and compliance with environmental regulations.

GIS DATA DOWNLOADS: (More information is in the table below)

File geodatabase: A limited set of feature classes comprise the majority of this geometric network. These nine feature classes are available in one file geodatabase (.gdb). ArcMap versions compatible with the .gdb are 10.1 and later. Read-only access is provided by the open-source software QGIS. Instructions on opening a .gdb file are available here, and a QGIS plugin can be downloaded here.

Acronyms and Definitions (pdf) are provided to better understand terms used.

ONLINE VIEWING: Use your PC’s browser to search for drains by street address or drain name and download engineering drawings. The Web Viewer link is: https://dpw.lacounty.gov/fcd/stormdrain/

MOBILE GIS: This storm drain system can also be viewed on mobile devices as well as your PC via ArcGIS Online. (As-built plans are not available with this mobile option.)

More About these Downloads All data added or updated by Public Works is contained in nine feature classes, with definitions listed below. The file geodatabase (.gdb) download contains these eleven feature classes without network connectivity. Feature classes include attributes with unabbreviated field names and domains.

ArcMap versions compatible with the .gdb are 10.1 and later.

Feature Class Download Description

CatchBasin In .gdb Catch basins collect urban runoff from gutters

Culvert In .gdb A relatively short conduit that conveys storm water runoff underneath a road or embankment. Typical materials include reinforced concrete pipe (RCP) and corrugated metal pipe (CMP). Typical shapes are circular, rectangular, elliptical, or arched.

ForceMain In .gdb Force mains carry stormwater uphill from pump stations into gravity mains and open channels.

GravityMain In .gdb Underground pipes and channels.

LateralLine In .gdb Laterals connect catch basins to underground gravity mains or open channels.

MaintenanceHole In .gdb The top opening to an underground gravity main used for inspection and maintenance.

NaturalDrainage In .gdb Streams and rivers that flow through natural creek beds

OpenChannel In .gdb Concrete lined stormwater channels.

PumpStation In .gdb Where terrain causes accumulation, lift stations are used to pump stormwater to where it can once again flow towards the ocean

Data Field Descriptions

Most of the feature classes in this storm drain geometric network share the same GIS table schema. Only the most critical attributes are listed here per LACFCD operations.

Attribute Description

ASBDATE The date the design plans were approved “as-built” or accepted as “final records”.

CROSS_SECTIN_SHAPE The cross-sectional shape of the pipe or channel. Examples include round, square, trapezoidal, arch, etc.

DIAMETER_HEIGHT The diameter of a round pipe or the height of an underground box or open channel.

DWGNO Drain Plan Drawing Number per LACFCD Nomenclature

EQNUM Asset No. assigned by the Department of Public Works’ (in Maximo Database).

MAINTAINED_BY Identifies, to the best of LAFCD’s knowledge, the agency responsible for maintaining the structure.

MOD_DATE Date the GIS features were last modified.

NAME Name of the individual drainage infrastructure.

OWNER Agency that owns the drainage infrastructure in question.

Q_DESIGN The peak storm water runoff used for the design of the drainage infrastructure.

SOFT_BOTTOM For open channels, indicates whether the channel invert is in its natural state (not lined).

SUBTYPE Most feature classes in this drainage geometric nature contain multiple subtypes.

UPDATED_BY The person who last updated the GIS feature.

WIDTH Width of a channel in feet.

This dataset contains both large (A0) printable maps of the Torres Strait broken into six overlapping regions, based on a clear sky, clear water composite Sentinel 2 composite imagery and the imagery used to create these maps. These maps show satellite imagery of the region, overlaid with reef and island boundaries and names. Not all features are named, just the more prominent features. This also includes a vector map of Ashmore Reef and Boot Reef in Coral Sea as these were used in the same discussions that these maps were developed for. The map of Ashmore Reef includes the atoll platform, reef boundaries and depth polygons for 5 m and 10 m.

This dataset contains all working files used in the development of these maps. This includes all a copy of all the source datasets and all derived satellite image tiles and QGIS files used to create the maps. This includes cloud free Sentinel 2 composite imagery of the Torres Strait region with alpha blended edges to allow the creation of a smooth high resolution basemap of the region.

The base imagery is similar to the older base imagery dataset: Torres Strait clear sky, clear water Landsat 5 satellite composite (NERP TE 13.1 eAtlas, AIMS, source: NASA).

Most of the imagery in the composite imagery from 2017 - 2021.

Method: The Sentinel 2 basemap was produced by processing imagery from the World_AIMS_Marine-satellite-imagery dataset (not yet published) for the Torres Strait region. The TrueColour imagery for the scenes covering the mapped area were downloaded. Both the reference 1 imagery (R1) and reference 2 imagery (R2) was copied for processing. R1 imagery contains the lowest noise, most cloud free imagery, while R2 contains the next best set of imagery. Both R1 and R2 are typically composite images from multiple dates.

The R2 images were selectively blended using manually created masks with the R1 images. This was done to get the best combination of both images and typically resulted in a reduction in some of the cloud artefacts in the R1 images. The mask creation and previewing of the blending was performed in Photoshop. The created masks were saved in 01-data/R2-R1-masks. To help with the blending of neighbouring images a feathered alpha channel was added to the imagery. The processing of the merging (using the masks) and the creation of the feathered borders on the images was performed using a Python script (src/local/03-merge-R2-R1-images.py) using the Pillow library and GDAL. The neighbouring image blending mask was created by applying a blurring of the original hard image mask. This allowed neighbouring image tiles to merge together.

The imagery and reference datasets (reef boundaries, EEZ) were loaded into QGIS for the creation of the printable maps.

To optimise the matching of the resulting map slight brightness adjustments were applied to each scene tile to match its neighbours. This was done in the setup of each image in QGIS. This adjustment was imperfect as each tile was made from a different combinations of days (to remove clouds) resulting in each scene having a different tonal gradients across the scene then its neighbours. Additionally Sentinel 2 has slight stripes (at 13 degrees off the vertical) due to the swath of each sensor having a slight sensitivity difference. This effect was uncorrected in this imagery.

Single merged composite GeoTiff: The image tiles with alpha blended edges work well in QGIS, but not in ArcGIS Pro. To allow this imagery to be used across tools that don't support the alpha blending we merged and flattened the tiles into a single large GeoTiff with no alpha channel. This was done by rendering the map created in QGIS into a single large image. This was done in multiple steps to make the process manageable.

The rendered map was cut into twenty 1 x 1 degree georeferenced PNG images using the Atlas feature of QGIS. This process baked in the alpha blending across neighbouring Sentinel 2 scenes. The PNG images were then merged back into a large GeoTiff image using GDAL (via QGIS), removing the alpha channel. The brightness of the image was adjusted so that the darkest pixels in the image were 1, saving the value 0 for nodata masking and the boundary was clipped, using a polygon boundary, to trim off the outer feathering. The image was then optimised for performance by using internal tiling and adding overviews. A full breakdown of these steps is provided in the README.md in the 'Browse and download all data files' link.

The merged final image is available in export\TS_AIMS_Torres Strait-Sentinel-2_Composite.tif.

Change Log: 2023-03-02: Eric Lawrey Created a merged version of the satellite imagery, with no alpha blending so that it can be used in ArcGIS Pro. It is now a single large GeoTiff image. The Google Earth Engine source code for the World_AIMS_Marine-satellite-imagery was included to improve the reproducibility and provenance of the dataset, along with a calculation of the distribution of image dates that went into the final composite image. A WMS service for the imagery was also setup and linked to from the metadata. A cross reference to the older Torres Strait clear sky clear water Landsat composite imagery was also added to the record.

22 Nov 2023: Eric Lawrey Added the data and maps for close up of Mer. - 01-data/TS_DNRM_Mer-aerial-imagery/ - preview/Torres-Strait-Mer-Map-Landscape-A0.jpeg - exports/Torres-Strait-Mer-Map-Landscape-A0.pdf Updated 02-Torres-Strait-regional-maps.qgz to include the layout for the new map.

Source datasets: Complete Great Barrier Reef (GBR) Island and Reef Feature boundaries including Torres Strait Version 1b (NESP TWQ 3.13, AIMS, TSRA, GBRMPA), https://eatlas.org.au/data/uuid/d2396b2c-68d4-4f4b-aab0-52f7bc4a81f5

Geoscience Australia (2014b), Seas and Submerged Lands Act 1973 - Australian Maritime Boundaries 2014a - Geodatabase [Dataset]. Canberra, Australia: Author. https://creativecommons.org/licenses/by/4.0/ [license]. Sourced on 12 July 2017, https://dx.doi.org/10.4225/25/5539DFE87D895

Basemap/AU_GA_AMB_2014a/Exclusive_Economic_Zone_AMB2014a_Limit.shp The original data was obtained from GA (Geoscience Australia, 2014a). The Geodatabase was loaded in ArcMap. The Exclusive_Economic_Zone_AMB2014a_Limit layer was loaded and exported as a shapefile. Since this file was small no clipping was applied to the data.

Geoscience Australia (2014a), Treaties - Australian Maritime Boundaries (AMB) 2014a [Dataset]. Canberra, Australia: Author. https://creativecommons.org/licenses/by/4.0/ [license]. Sourced on 12 July 2017, http://dx.doi.org/10.4225/25/5539E01878302 Basemap/AU_GA_Treaties-AMB_2014a/Papua_New_Guinea_TSPZ_AMB2014a_Limit.shp The original data was obtained from GA (Geoscience Australia, 2014b). The Geodatabase was loaded in ArcMap. The Papua_New_Guinea_TSPZ_AMB2014a_Limit layer was loaded and exported as a shapefile. Since this file was small no clipping was applied to the data.

AIMS Coral Sea Features (2022) - DRAFT This is a draft version of this dataset. The region for Ashmore and Boot reef was checked. The attributes in these datasets haven't been cleaned up. Note these files should not be considered finalised and are only suitable for maps around Ashmore Reef. Please source an updated version of this dataset for any other purpose. CS_AIMS_Coral-Sea-Features/CS_Names/Names.shp CS_AIMS_Coral-Sea-Features/CS_Platform_adj/CS_Platform.shp CS_AIMS_Coral-Sea-Features/CS_Reef_Boundaries_adj/CS_Reef_Boundaries.shp CS_AIMS_Coral-Sea-Features/CS_Depth/CS_AIMS_Coral-Sea-Features_Img_S2_R1_Depth5m_Coral-Sea.shp CS_AIMS_Coral-Sea-Features/CS_Depth/CS_AIMS_Coral-Sea-Features_Img_S2_R1_Depth10m_Coral-Sea.shp

Murray Island 20 Sept 2011 15cm SISP aerial imagery, Queensland Spatial Imagery Services Program, Department of Resources, Queensland This is the high resolution imagery used to create the map of Mer.

Marine satellite imagery (Sentinel 2 and Landsat 8) (AIMS), https://eatlas.org.au/data/uuid/5d67aa4d-a983-45d0-8cc1-187596fa9c0c - World_AIMS_Marine-satellite-imagery

Data Location: This dataset is filed in the eAtlas enduring data repository at: data\custodian\2020-2029-AIMS\TS_AIMS_Torres-Strait-Sentinel-2-regional-maps. On the eAtlas server it is stored at eAtlas GeoServer\data\2020-2029-AIMS.

This specialized location dataset delivers detailed information about marina establishments. Maritime industry professionals, coastal planners, and tourism researchers can leverage precise location insights to understand maritime infrastructure, analyze recreational boating landscapes, and develop targeted strategies.

How Do We Create Polygons? -All our polygons are manually crafted using advanced GIS tools like QGIS, ArcGIS, and similar applications. This involves leveraging aerial imagery and street-level views to ensure precision. -Beyond visual data, our expert GIS data engineers integrate venue layout/elevation plans sourced from official company websites to construct detailed indoor polygons. This meticulous process ensures higher accuracy and consistency. -We verify our polygons through multiple quality checks, focusing on accuracy, relevance, and completeness.

What's More? -Custom Polygon Creation: Our team can build polygons for any location or category based on your specific requirements. Whether it’s a new retail chain, transportation hub, or niche point of interest, we’ve got you covered. -Enhanced Customization: In addition to polygons, we capture critical details such as entry and exit points, parking areas, and adjacent pathways, adding greater context to your geospatial data. -Flexible Data Delivery Formats: We provide datasets in industry-standard formats like WKT, GeoJSON, Shapefile, and GDB, making them compatible with various systems and tools. -Regular Data Updates: Stay ahead with our customizable refresh schedules, ensuring your polygon data is always up-to-date for evolving business needs.

Unlock the Power of POI and Geospatial Data With our robust polygon datasets and point-of-interest data, you can: -Perform detailed market analyses to identify growth opportunities. -Pinpoint the ideal location for your next store or business expansion. -Decode consumer behavior patterns using geospatial insights. -Execute targeted, location-driven marketing campaigns for better ROI. -Gain an edge over competitors by leveraging geofencing and spatial intelligence.

Why Choose LocationsXYZ? LocationsXYZ is trusted by leading brands to unlock actionable business insights with our spatial data solutions. Join our growing network of successful clients who have scaled their operations with precise polygon and POI data. Request your free sample today and explore how we can help accelerate your business growth.

Notice: this is not the latest Heat Island Severity image service.This layer contains the relative heat severity for every pixel for every city in the United States, including Alaska, Hawaii, and Puerto Rico. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2022, patched with data from 2021 where necessary.Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter than the average temperature for that same city as a whole. Severity is measured on a scale of 1 to 5, with 1 being a relatively mild heat area (slightly above the mean for the city), and 5 being a severe heat area (significantly above the mean for the city). The absolute heat above mean values are classified into these 5 classes using the Jenks Natural Breaks classification method, which seeks to reduce the variance within classes and maximize the variance between classes. Knowing where areas of high heat are located can help a city government plan for mitigation strategies.This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at The Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so The Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). The Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.

This resource contains data inputs and a Jupyter Notebook that is used to introduce Hydrologic Analysis using Terrain Analysis Using Digital Elevation Models (TauDEM) and Python. TauDEM is a free and open-source set of Digital Elevation Model (DEM) tools developed at Utah State University for the extraction and analysis of hydrologic information from topography. This resource is part of a HydroLearn Physical Hydrology learning module available at https://edx.hydrolearn.org/courses/course-v1:Utah_State_University+CEE6400+2019_Fall/about

In this activity, the student learns how to (1) derive hydrologically useful information from Digital Elevation Models (DEMs); (2) describe the sequence of steps involved in mapping stream networks, catchments, and watersheds; and (3) compute an approximate water balance for a watershed-based on publicly available data.

Please note that this exercise is designed for the Logan River watershed, which drains to USGS streamflow gauge 10109000 located just east of Logan, Utah. However, this Jupyter Notebook and the analysis can readily be applied to other locations of interest. If running the terrain analysis for other study sites, you need to prepare a DEM TIF file, an outlet shapefile for the area of interest, and the average annual streamflow and precipitation data. - There are several sources to obtain DEM data. In the U.S., the DEM data (with different spatial resolutions) can be obtained from the National Elevation Dataset available from the national map (http://viewer.nationalmap.gov/viewer/). Another DEM data source is the Shuttle Radar Topography Mission (https://www2.jpl.nasa.gov/srtm/), an international research effort that obtained digital elevation models on a near-global scale (search for Digital Elevation at https://www.usgs.gov/centers/eros/science/usgs-eros-archive-products-overview?qt-science_center_objects=0#qt-science_center_objects). - If not already available, you can generate the outlet shapefile by applying basic terrain analysis steps in geospatial information system models such as ArcGIS or QGIS. - You also need to obtain average annual streamflow and precipitation data for the watershed of interest to assess the annual water balance and calculate the runoff ratio in this exercise. In the U.S., the streamflow data can be obtained from the USGS NWIS website (https://waterdata.usgs.gov/nwis) and the precipitation from PRISM (https://prism.oregonstate.edu/normals/). Note that using other datasets may require preprocessing steps to make data ready to use for this exercise.

Coastline for Antarctica created from various mapping and remote sensing sources, consisting of the following coast types: ice coastline, rock coastline, grounding line, ice shelf and front, ice rumple, and rock against ice shelf. Covering all land and ice shelves south of 60°S. Suitable for topographic mapping and analysis. High resolution versions of ADD data are suitable for scales larger than 1:1,000,000. The largest suitable scale is changeable and dependent on the region.

Major changes in v7.5 include updates to ice shelf fronts in the following regions: Seal Nunataks and Scar Inlet region, the Ronne-Filchner Ice Shelf, between the Brunt Ice Shelf and Riiser-Larsen Peninsula, the Shackleton and Conger ice shelves, and Crosson, Thwaites and Pine Island. Small areas of grounding line and ice coastlines were also updated in some of these regions as needed.

Data compiled, managed and distributed by the Mapping and Geographic Information Centre and the UK Polar Data Centre, British Antarctic Survey on behalf of the Scientific Committee on Antarctic Research.

Further information and useful links

Map projection: WGS84 Antarctic Polar Stereographic, EPSG 3031. Note: by default, opening this layer in the Map Viewer will display the data in Web Mercator. To display this layer in its native projection use an Antarctic basemap.

The currency of this dataset is May 2022 and will be reviewed every 6 months. This feature layer will always reflect the most recent version.

For more information on, and access to other Antarctic Digital Database (ADD) datasets, refer to the SCAR ADD data catalogue.

A related medium resolution dataset is also published via Living Atlas, as well medium and high resolution polygon datasets.

For background information on the ADD project, please see the British Antarctic Survey ADD project page.

Lineage

Dataset compiled from a variety of Antarctic map and satellite image sources. The dataset was created using ArcGIS and QGIS GIS software programmes and has been checked for basic topography and geometry checks, but does not contain strict topology. Quality varies across the dataset and certain areas where high resolution source data were available are suitable for large scale maps whereas other areas are only suitable for smaller scales. Each line has attributes detailing the source which can give the user further indications of its suitability for specific uses. Attributes also give information including 'surface' (e.g. grounding line, ice coastline, ice shelf front) and revision date. Compiled from sources ranging in time from 1990s-2022 - individual lines contain exact source dates.

This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.

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

This map is designed to be used as a basemap by marine GIS professionals and as a reference map by anyone interested in ocean data. The basemap includes bathymetry, marine water body names, undersea feature names, and derived depth values in meters. Land features include administrative boundaries, cities, inland waters, roads, overlaid on land cover and shaded relief imagery.

The map was compiled from a variety of best available sources from several data providers, including General Bathymetric Chart of the Oceans GEBCO_08 Grid version 20100927 and IHO-IOC GEBCO Gazetteer of Undersea Feature Names August 2010 version (https://www.gebco.net), National Oceanic and Atmospheric Administration (NOAA) and National Geographic for the oceans; and DeLorme, HERE, and Esri for topographic content. The basemap was designed and developed by Esri.

The Ocean Basemap currently provides coverage for the world down to a scale of ~1:577k; coverage down to ~1:72k in United States coastal areas and various other areas; and coverage down to ~1:9k in limited regional areas. You can contribute your bathymetric data to this service and have it served by Esri for the benefit of the Ocean GIS community. For details, see the Community Maps Program.

Tip: Here are some famous oceanic locations as they appear in this map. Each URL below launches this map at a particular location via parameters specified in the URL: Challenger Deep, Galapagos Islands, Hawaiian Islands, Maldive Islands, Mariana Trench, Tahiti, Queen Charlotte Sound, Notre Dame Bay, Labrador Trough, New York Bight, Massachusetts Bay, Mississippi Sound