Tile index for Alaska coastal orthoimagery and elevation data: Icy Cape to Cape Prince of Wales, 2016

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Tile index for Alaska coastal orthoimagery and elevation data: Icy Cape to Cape Prince of Wales, 2016
Abstract:
This part of the data release presents a shapefile that includes a spatial index of orthoimagery and elevation data describing the Alaskan coastline from Icy Cape to Cape Prince of Wales. The data products referenced in this index include orthoimagery, digital surface models, and elevation point clouds which were generated from aerial imagery using structure-from-motion methods. Fairbanks Fodar, a contracted mapping service, collected the aerial imagery in 2016 and created all of the data products referenced here. Due to the enormous extent of this dataset, the products are split into separate files with more manageable sizes. Each polygon in this shapefile index provides a geographic outline of a data file’s coverage, corresponding file name, and data type. Additionally, the orthoimagery and digital surface model files include a link to stream the file using any software that supports access to cloud optimized geotiffs (COGs).
Supplemental_Information:
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this Federal Geographic Data Committee-compliant metadata file is intended to document the data set in nonproprietary form, as well as in Esri format, this metadata file may include some Esri-specific terminology.
  1. How might this data set be cited?
    Nolan, Matt, Gibbs, Ann E., and Snyder, Alexander G., 20221115, Tile index for Alaska coastal orthoimagery and elevation data: Icy Cape to Cape Prince of Wales, 2016: data release DOI:10.5066/P9PGJNE9, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Online Links:

    This is part of the following larger work.

    Nolan, Matt, Gibbs, Ann E., and Snyder, Alexander G., 2022, Alaska coastal orthoimagery and elevation data: Icy Cape to Cape Prince of Wales, 2016: data release DOI:10.5066/P9PGJNE9, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Online Links:

    Other_Citation_Details:
    suggested citation: Nolan, M., Gibbs, A.E., and Snyder, A.G., 2022, Alaska coastal orthoimagery and elevation data: Icy Cape to Cape Prince of Wales, 2016: U.S. Geological Survey data release, https://doi.org/10.5066/P9PGJNE9.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -167.63080825
    East_Bounding_Coordinate: -161.00513945
    North_Bounding_Coordinate: 70.33433589
    South_Bounding_Coordinate: 65.78673484
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/636c9e13d34ed907bf6b315a?name=Tile_Index_Example.jpg&allowOpen=true (JPEG)
    Example of the Tile Index symbolized by data type and an example of an orthoimagery tile.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 29-Aug-2016
    Ending_Date: 04-Sep-2016
    Currentness_Reference:
    ground condition at time data were collected
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: polygon shapefile
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • G-polygon (474)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 3
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -165.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 0.001
      Ordinates (y-coordinates) are specified to the nearest 0.001
      Planar coordinates are specified in METERS
      The horizontal datum used is NAD83_National_Spatial_Reference_System_2011.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222101.
  7. How does the data set describe geographic features?
    Tile_Index.shp Attribute Table
    Table containing attribute information associated with the dataset. (Source: Producer defined)
    FID
    Index number unique to each record in the attribute table. (Source: Assigned by ArcMap)
    Range of values
    Minimum:0
    Maximum:473
    Shape
    Defines what type of spatial information is associated with this record (for example, polyline, polygon, point). (Source: Assigned by ArcMap 10.6)
    ValueDefinition
    PolygonAn object that stores its geographic representation—a series of x and y coordinate pairs that enclose an area—as one of its properties (or fields) in the row in the database.
    Name
    Name of the orthoimagery, digital surface model, or point cloud file that corresponds to the polygon, which represents the geographic extent of the data in the file. (Source: Producer defined.) Filenames are a unique identifier that describes certain attributes of the file, including the region, processing group, data type, grid size, and format. For example, the filename ‘shish_C_ortho_10cm-0-4x_cog’ refers to data that is somewhat close to the town of Shishmaref (‘shish’), processed with other files in group ‘C’, contains orthoimagery (‘ortho’) data, represented as a raster with cell size ‘10cm’, uniquely identified as ‘0-4’, and stored as a Cloud Optimized GeoTIFF (‘cog’).
    DataType
    Describes the type of data described by the data outline polygon and the other attributes. (Source: Producer defined.)
    ValueDefinition
    Digital_Surface_ModelRaster grid that describes the elevation of the structures and terrain of a specific area.
    Point_CloudPoint cloud that describes the elevation of the structures and terrain of a specific area.
    OrthoimageryGeoreferenced imagery represented as a 4-band raster grid with red/green/blue/alpha values.
    COG_URL
    URL that points to the file in cloud storage, allowing users to view the file by streaming it to any software that supports cloud optimized geotiffs, instead of downloading the file to a local drive. (Source: Producer defined.) Unique URL is made up of two parts: the cloud server location and the individual filename.
    Entity_and_Attribute_Overview:
    Polygons in this shapefile represent the outline of data available in other parts of this data release. Users are meant to use the index shapefile to find which files will correspond to their area of interest.
    Entity_and_Attribute_Detail_Citation: Producer defined

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Matt Nolan
    • Ann E. Gibbs
    • Alexander G. Snyder
  2. Who also contributed to the data set?
    Data collection was funded by the U.S. Geological Survey. Data acquisition and processing were conducted by Fairbanks Fodar.
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Attn: PCMSC Science Data Coordinator
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov

Why was the data set created?

The tile index enables the user to determine which files describe a specific area of interest without needing to download the entire dataset. Fairbanks Fodar was contracted by the USGS to acquire new airborne data to process into orthoimagery, digital surface models, and elevation point clouds.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 19-May-2022 (process 1 of 1)
    Outlines of the data were generated using ArcMap 10.6. Individual files were added to a Mosaic Dataset, then the data outlines were generated using the Build Footprints tool. The footprints were exported to a shapefile and the Simplify Polygon tool was used to reduce the number of vertices and therefore the file size. Person who carried out this activity:
    Alexander Snyder
    U.S. Geological Survey
    Oceanographer
    2885 Mission Street
    Santa Cruz, CA

    831-427-4450 (voice)
    agsnyder@usgs.gov
  3. What similar or related data should the user be aware of?
    Nolan, M., Larsen, C., and Sturm, M., 2015, Mapping snow depth from manned aircraft on landscape scales at centimeter resolution using structure-from-motion photogrammetry.

    Online Links:

    Other_Citation_Details:
    Nolan, M., Larsen, C., and Sturm, M., 2015, Mapping snow depth from manned aircraft on landscape scales at centimeter resolution using structure-from-motion photogrammetry: The Cryosphere, v. 9, p. 1445–1463, https://doi.org/10.5194/tc-9-1445-2015.
    Snyder, Alexander G., and Gibbs, Ann E., 2019, National assessment of shoreline change: A GIS compilation of vector shorelines and associated shoreline change data for the north coast of Alaska, Icy Cape to Cape Prince of Wales.

    Online Links:

    Other_Citation_Details:
    Snyder, A.G., and Gibbs, A.E., 2019, National assessment of shoreline change: A GIS compilation of updated vector shorelines and associated shoreline change data for the north coast of Alaska, Icy Cape to Cape Prince of Wales: U.S. Geological Survey data release, https://doi.org/10.5066/P9H1S1PV.
    Gibbs, Ann E., Snyder, Alexander G., and Richmond, Bruce M., 2019, National Assessment of Shoreline Change—Historical Shoreline Change Along the North Coast of Alaska, Icy Cape to Cape Prince of Wales.

    Online Links:

    Other_Citation_Details:
    Gibbs, A.E., Snyder, A.G., and Richmond, B.M., 2019, National assessment of shoreline change—Historical shoreline change along the north coast of Alaska, Icy Cape to Cape Prince of Wales: U.S. Geological Survey Open-File Report 2019–1146, 52 p., https://doi.org/10.3133/ofr20191146.
    Overbeck, Jacquelyn R., Buzard, Richard M., Turner, Mark M., Miller, Katie Y., and Glenn, Roberta J.T., 2020, Shoreline change at Alaska coastal communities: Alaska Division of Geological & Geophysical Surveys Report of Investigation.

    Online Links:

    Other_Citation_Details:
    Overbeck, J.R., Buzard, R.M., Turner, M.M., Miller, K.Y., and Glenn, R.J.T., 2020, Shoreline change at Alaska coastal communities: Alaska Division of Geological & Geophysical Surveys Report of Investigation 2020-10, 29 p., 47 sheets, https://doi.org/10.14509/30552.
    Quantum Spatial, Incorporated (QSI), 2019, Fairbanks Fodar Assessment.

    Other_Citation_Details:
    Additional information about this report, which describes the formal evaluation of accuracy performed on the data against vertical control points and existing lidar data, can be obtained by contacting Ann Gibbs (agibbs@usgs.gov).

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    No formal accuracy tests were conducted.
  2. How accurate are the geographic locations?
    A formal accuracy assessment of the horizontal positional information in the data set has not been conducted. The index polygons describe the approximate limits of the data in each file. Orthoimagery and digital surface models also include No Data values beyond the polygons depicted here. The polygons were also simplified to reduce the number of vertices and therefore represent an approximate outline of the data, which may exceed the polygon by up to 100 meters.
  3. How accurate are the heights or depths?
    Not applicable
  4. Where are the gaps in the data? What is missing?
    Index polygons were generated for each orthomimagery, digital surface model, and point cloud file.
  5. How consistent are the relationships among the observations, including topology?
    No formal logical accuracy tests were conducted. The boundaries were created as reference that would allow for an efficient means of navigating the data in the associated data release. Therefore, accuracy of the data boundaries was intentionally reduced to better serve the intended purpose.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints None
Use_Constraints USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. Please recognize and acknowledge the U.S. Geological Survey and Fairbanks Fodar as the originator(s) of the dataset and in products derived from these data.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - ScienceBase
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? These data are available in shapefile format contained in a single zip file.
  3. What legal disclaimers am I supposed to read?
    Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    These data can be viewed with Geographic Information Systems (GIS) software or other software capable of displaying geospatial raster data.

Who wrote the metadata?

Dates:
Last modified: 15-Nov-2022
Metadata author:
U.S. Geological Survey, Pacific Coastal and Marine Science Center
Attn: PCMSC Science Data Coordinator
2885 Mission Street
Santa Cruz, CA

831-427-4747 (voice)
pcmsc_data@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/ScienceBase/DR_P9PGJNE9/Tile_Index_metadata.faq.html>
Generated by mp version 2.9.51 on Thu Nov 17 17:43:41 2022