USGS: science for a changing world - www.usgs.gov
Coastal and Marine Geology Program home - marine.usgs.gov
  U.S. Geological Survey Open-File Report 02-002

81_2NAVT: Navigation lines for R/V ASTERIAS 81-2

Metadata also available as: HTML - TEXT

Frequently-anticipated questions:


What does this data set describe?

    Title: 81_2NAVT: Navigation lines for R/V ASTERIAS 81-2 (AST81-2)
    Abstract:
    This GIS layer contains the shiptrack navigation collected aboard the R/V ASTERIAS during a 1981 geophysical curise to Block Island Sound and easternmost Long Island Sound.

  1. How should this data set be cited?

    Poppe, Larry, and Paskevich, Valerie, 20020630, 81_2NAVT: Navigation lines for R/V ASTERIAS 81-2 (AST81-2): U.S. Geological Survey Open-File Report 02-002, U.S. Geological Survey, Woods Hole Field Center.

    Online Links:

    This is part of the following larger work.

    Poppe, Larry, and Paskevich, Valerie, 2002, Geological Framework Data from Long Island Sound, 1981-1990: A Digital Data Release: U.S. Geological Survey Open-File Report 02-002, U. S. Geological Survey, Coastal and Marine Geology Program, Woods Hole, MA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -72.193500
    East_Bounding_Coordinate: -71.493170
    North_Bounding_Coordinate: 41.348500
    South_Bounding_Coordinate: 41.067000

  3. What does it look like?

    ../../../../htmldocs/images/browse/81_2navt.gif (GIF)
    R/V ASTERIAS cruise 81-2 extent of navigation lines shapefile shown in it's spatial reference to Long Island Sound.

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: 11-Sep-1981
    Ending_Date: 18-Sep-1981
    Currentness_Reference: ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

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

      • String (42)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.00001. Longitudes are given to the nearest 0.00001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1927.
      The ellipsoid used is Clarke 1866.
      The semi-major axis of the ellipsoid used is 6378206.400000.
      The flattening of the ellipsoid used is 1/294.978698.

  7. How does the data set describe geographic features?

    81_2navt
    shapefile attribute table (Source: ESRI)

    FID
    Internal feature number. (Source: ESRI)

    Frequency of measurement: None planned

    Range of values

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    ID
    Sequential number assigned to polyline segment.

    Frequency of measurement: As needed

    Range of values
    Minimum:0
    Maximum:41
    Units:integer
    Resolution:1

    LENGTH
    length of line segment in native units

    Range of values
    Minimum:.013
    Maximum:.293
    Resolution:.001

    Range of values
    Units:Time in hours and minutes in military time
    Resolution:Hours and minutes

    CRUISEID
    USGS assigned cruise identifier (Source: Recorded by Loran-C navigation system and noted in cruise log book.)

    ValueDefinition
    AST81-2Assigned identifier for cruise R/V ASTERIAS 81-2

    Range of values
    Units:Time in hours and minutes in military time
    Resolution:Hours and minutes

    DATE
    Date which the navigation data was collected. Values are recorded as an ASCII string. (Source: Chief Scientist)

    Character string

    LINE
    Number assigned to the seismic line for which the navigation was collected (Source: Chief Scientist)

    Frequency of measurement: As needed

    Range of values
    Minimum:1
    Maximum:31
    Units:integer
    Resolution:1

    SOL
    Start of Line (SOL):Time that recording of seismic line began. (Source: Recorded by Loran-C navigation system and noted in cruise log book.)

    Frequency of measurement: As needed

    ValueDefinition
    Hour:minuteHour and minutes

    EOL
    End of Line (EOL): Time that recording of seismic line was completed. (Source: Recorded by Loran-C navigation system and noted in cruise log book.)

    Frequency of measurement: As needed

    ValueDefinition
    HH:MMHour and minute

    IMAGE
    Name of associated GIF image containing browse version of seismic record for line. (Source: assigned file name)

    GIF file name

    Entity_and_Attribute_Overview:
    This data layer (navigation collected onboard the R/V ASTERIAS cruise 81-2 to BIS and easternmost LIS) provides information location of seismic data used to interpret the geologic framework.
    Entity_and_Attribute_Detail_Citation:
    Geological framework data from Long Island Sound and vicinity, 1981-1990: a digital release


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    Sally Needell and Ralph Lewis, the chief scientists aboard the cruise; and Valerie Paskevich for completing the Arc processing and creation of the GIS data layer.

  3. To whom should users address questions about the data?

    U. S. Geological Survey
    c/o Larry Poppe
    384 Woods Hole Road
    Woods Hole, MA 02543-1598
    USA

    (508) 548-8700 x2314 (voice)
    (508) 457-2310 (FAX)
    lpoppe@usgs.gov

    Hours_of_Service: 0800-1600


Why was the data set created?

The purpose is to disseminate a digital version of a regional map showing the distribution of sub-bottom seismic profiles (boomer) collected in Block Island Sound and easternmost Long Island Sound. The seismic data collected along these ship tracks can be used to provide useful information about the framework geology in this region.


How was the data set created?

  1. From what previous works were the data drawn?

    R/V ASTERIAS 81-2 LORAN-C printouts (source 1 of 1)
    Needel, Sally W. , and Lewis, Ralph S. , 19840000, Geology of Block Island Sound, R.I. and N.Y.: U.S. Geological Survey Miscellaneous Field Studies Map MF-1621, U.S. Geological Survey, Woods Hole, MA.

    Type_of_Source_Media:
    High-resolution seismic-reflection boomer lines navigated with Loran C
    Source_Contribution:
    During field work conducted in Block Island Sound during September 1981 high-resolution seismic-reflection data were collected. This data set is the 5-min. navigation from that cruise.

  2. How were the data generated, processed, and modified?

    Date: 24-Mar-2002 (process 1 of 3)
    An ArcView shapefile containing the five-minute navigation for cruise AST81-2 was edited to create separate shapefiles for each of the individual line segments.

    Person who carried out this activity:

    U.S. Geological Survey
    c/o Valerie Paskevich
    Computer Specialist
    384 Woods Hole road
    Woods Hole, MA 02543-1598
    USA

    (508) 548-8700 x2281 (voice)
    (508) 457-2310 (FAX)
    vpaskevich@usgs.gov

    Data sources used in this process:
    • 81_2navp.dbf, 81_2navp.shp, 81_2navp.shx

    Data sources produced in this process:

    • line01p.dbf, line01p.shp, line01p.shx
    • line02p.dbf, line02p.shp, line02p.shx
    • line03p.dbf, line03p.shp, line03p.shx
    • line04p.dbf, line04p.shp, line04p.shx
    • line05p.dbf, line05p.shp, line05p.shx
    • line06p.dbf, line06p.shp, line06p.shx
    • line07p.dbf, line07p.shp, line07p.shx
    • line08p.dbf, line08p.shp, line08p.shx
    • line09p.dbf, line09p.shp, line09p.shx
    • line10p.dbf, line10p.shp, line10p.shx
    • line11p.dbf, line11p.shp, line11p.shx
    • line12ap.dbf, line12ap.shp, line12ap.shx
    • line12bp.dbf, line12bp.shp, line12bp.shx
    • line13p.dbf, line13p.shp, line13p.shx
    • line14p.dbf, line14p.shp, line14p.shx
    • line15ap.dbf, line15ap.shp, line15ap.shx
    • line15bp.dbf, line15bp.shp, line15bp.shx
    • line16ap.dbf, line16ap.shp, line16ap.shx
    • line16bp.dbf, line16bp.shp, line16bp.shx
    • line16bc.dbf, line16bc.shp, line16bc.shx
    • line17ap.dbf, line17ap.shp, line17ap.shx
    • line17bp.dbf, line17bp.shp, line17bp.shx
    • line18p.dbf, line18p.shp, line18p.shx
    • line19p.dbf, line19p.shp, line19p.shx
    • line20p.dbf, line20p.shp, line20p.shx
    • line21ap.dbf, line21ap.shp, line21ap.shx
    • line21bp.dbf, line21bp.shp, line21bp.shx
    • line22p.dbf, line22p.shp, line22p.shx
    • line23p.dbf, line23p.shp, line23p.shx
    • line24p.dbf, line24p.shp, line24p.shx
    • line25p.dbf, line25p.shp, line25p.shx
    • line26p.dbf, line26p.shp, line26p.shx
    • line27ap.dbf, line27ap.shp, line27ap.shx
    • line27bp.dbf, line27bp.shp, line27bp.shx
    • line28ap.dbf, line28ap.shp, line28ap.shx
    • line28bp.dbf, line28bp.shp, line28bp.shx
    • line28bc.dbf, line28bc.shp, line28bc.shx
    • line28bd.dbf, line28bd.shp, line28bd.shx
    • line29ap.dbf, line29ap.shp, line29ap.shx
    • line29bp.dbf, line29bp.shp, line29bp.shx
    • line30p.dbf, line30p.shp, line30p.shx
    • line31p.dbf, line31p.shp, line31p.shx

    Date: 24-Mar-2002 (process 2 of 3)
    The shapefiles containing the 5 minute navigational fixes for the individual cruise lines were each converted to separate polyline shapefiles.

    Person who carried out this activity:

    U.S. Geological Survey
    c/o Valerie Paskevich
    384 Woods Hole road
    Woods Hole, MA 02543-1598
    USA

    (508) 548-8700 x2281 (voice)
    (508) 457-2310 (FAX)
    vpaskevich@usgs.gov

    Data sources used in this process:
    • line01p.dbf, line01p.shp, line01p.shx
    • line02p.dbf, line02p.shp, line02p.shx
    • line03p.dbf, line03p.shp, line03p.shx
    • line04p.dbf, line04p.shp, line04p.shx
    • line05p.dbf, line05p.shp, line05p.shx
    • line06p.dbf, line06p.shp, line06p.shx
    • line07p.dbf, line07p.shp, line07p.shx
    • line08p.dbf, line08p.shp, line08p.shx
    • line09p.dbf, line09p.shp, line09p.shx
    • line10p.dbf, line10p.shp, line10p.shx
    • line11p.dbf, line11p.shp, line11p.shx
    • line12ap.dbf, line12ap.shp, line12ap.shx
    • line12bp.dbf, line12bp.shp, line12bp.shx
    • line13p.dbf, line13p.shp, line13p.shx
    • line14p.dbf, line14p.shp, line14p.shx
    • line15ap.dbf, line15ap.shp, line15ap.shx
    • line15bp.dbf, line15bp.shp, line15bp.shx
    • line16ap.dbf, line16ap.shp, line16ap.shx
    • line16bp.dbf, line16bp.shp, line16bp.shx
    • line16cp.dbf, line16cp.shp, line16cp.shx
    • line17ap.dbf, line17ap.shp, line17ap.shx
    • line17bp.dbf, line17bp.shp, line17bp.shx
    • line18p.dbf, line18p.shp, line18p.shx
    • line19p.dbf, line19p.shp, line19p.shx
    • line20p.dbf, line20p.shp, line20p.shx
    • line21ap.dbf, line21ap.shp, line21ap.shx
    • line21bp.dbf, line21bp.shp, line21bp.shx
    • line22p.dbf, line22p.shp, line22p.shx
    • line23p.dbf, line23p.shp, line23p.shx
    • line24p.dbf, line24p.shp, line24p.shx
    • line25p.dbf, line25p.shp, line25p.shx
    • line26p.dbf, line26p.shp, line26p.shx
    • line27ap.dbf, line27ap.shp, line27ap.shx
    • line27bp.dbf, line27bp.shp, line27bp.shx
    • line28ap.dbf, line28ap.shp, line28ap.shx
    • line28bp.dbf, line28bp.shp, line28bp.shx
    • line28cp.dbf, line28cp.shp, line28cp.shx
    • line28dp.dbf, line28dp.shp, line28dp.shx
    • line29ap.dbf, line29ap.shp, line29ap.shx
    • line29bp.dbf, line29bp.shp, line29bp.shx
    • line30p.dbf, line30p.shp, line30p.shx
    • line31p.dbf, line31p.shp, line31p.shx

    Data sources produced in this process:

    • line01t.dbf, line01t.shp, line01t.shx
    • line02t.dbf, line02t.shp, line02t.shx
    • line03t.dbf, line03t.shp, line03t.shx
    • line04t.dbf, line04t.shp, line04t.shx
    • line05t.dbf, line05t.shp, line05t.shx
    • line06t.dbf, line06t.shp, line06t.shx
    • line07t.dbf, line07t.shp, line07t.shx
    • line08t.dbf, line08t.shp, line08t.shx
    • line09t.dbf, line09t.shp, line09t.shx
    • line10t.dbf, line10t.shp, line10t.shx
    • line11t.dbf, line11t.shp, line11t.shx
    • line12at.dbf, line12at.shp, line12at.shx
    • line12bt.dbf, line12bt.shp, line12bt.shx
    • line13t.dbf, line13t.shp, line13t.shx
    • line14t.dbf, line14t.shp, line14t.shx
    • line15at.dbf, line15at.shp, line15at.shx
    • line15bt.dbf, line15bt.shp, line15bt.shx
    • line16at.dbf, line16at.shp, line16at.shx
    • line16bt.dbf, line16bt.shp, line16bt.shx
    • line16ct.dbf, line16ct.shp, line16ct.shx
    • line17at.dbf, line17at.shp, line17at.shx
    • line17bt.dbf, line17bt.shp, line17bt.shx
    • line18t.dbf, line18t.shp, line18t.shx
    • line19t.dbf, line19t.shp, line19t.shx
    • line20t.dbf, line20t.shp, line20t.shx
    • line21at.dbf, line21at.shp, line21at.shx
    • line21bt.dbf, line21bt.shp, line21bt.shx
    • line22t.dbf, line22t.shp, line22t.shx
    • line23t.dbf, line23t.shp, line23t.shx
    • line24t.dbf, line24t.shp, line24t.shx
    • line25t.dbf, line25t.shp, line25t.shx
    • line26t.dbf, line26t.shp, line26t.shx
    • line27at.dbf, line27at.shp, line27at.shx
    • line27bt.dbf, line27bt.shp, line27bt.shx
    • line28at.dbf, line28at.shp, line28at.shx
    • line28bt.dbf, line28bt.shp, line28bt.shx
    • line28ct.dbf, line28ct.shp, line28ct.shx
    • line28dt.dbf, line28dt.shp, line28dt.shx
    • line29at.dbf, line29at.shp, line29at.shx
    • line29bt.dbf, line29bt.shp, line29bt.shx
    • line30t.dbf, line30t.shp, line30t.shx
    • line31t.dbf, line31t.shp, line31t.shx

    Date: 24-Mar-2002 (process 3 of 3)
    The individual line segments were combined to create a single shapefile. The file was then edited to add the individual line attribute information and links to the seismic record browse image.

    Person who carried out this activity:

    Valerie Paskevich
    U.S. Geological Survey
    Computer Specialist
    384 Woods Hole Road
    Woods Hole, MA 02543-1598
    USA

    (508) 548-8700 x2281 (voice)
    (508) 457-2310 (FAX)
    vpaskevich@usgs.gov

    Data sources used in this process:
    • line01t.dbf, line01t.shp, line01t.shx
    • line02t.dbf, line02t.shp, line02t.shx
    • line03t.dbf, line03t.shp, line03t.shx
    • line04t.dbf, line04t.shp, line04t.shx
    • line05t.dbf, line05t.shp, line05t.shx
    • line06t.dbf, line06t.shp, line06t.shx
    • line07t.dbf, line07t.shp, line07t.shx
    • line08t.dbf, line08t.shp, line08t.shx
    • line09t.dbf, line09t.shp, line09t.shx
    • line10t.dbf, line10t.shp, line10t.shx
    • line11t.dbf, line11t.shp, line11t.shx
    • line12at.dbf, line12at.shp, line12at.shx
    • line12bt.dbf, line12bt.shp, line12bt.shx
    • line13t.dbf, line13t.shp, line13t.shx
    • line14t.dbf, line14t.shp, line14t.shx
    • line15at.dbf, line15at.shp, line15at.shx
    • line15bt.dbf, line15bt.shp, line15bt.shx
    • line16at.dbf, line16at.shp, line16at.shx
    • line16bt.dbf, line16bt.shp, line16bt.shx
    • line16ct.dbf, line16ct.shp, line16ct.shx
    • line17at.dbf, line17at.shp, line17at.shx
    • line17bt.dbf, line17bt.shp, line17bt.shx
    • line18t.dbf, line18t.shp, line18t.shx
    • line19t.dbf, line19t.shp, line19t.shx
    • line20t.dbf, line20t.shp, line20t.shx
    • line21at.dbf, line21at.shp, line21at.shx
    • line21bt.dbf, line21bt.shp, line21bt.shx
    • line22t.dbf, line22t.shp, line22t.shx
    • line23t.dbf, line23t.shp, line23t.shx
    • line24t.dbf, line24t.shp, line24t.shx
    • line25t.dbf, line25t.shp, line25t.shx
    • line26t.dbf, line26t.shp, line26t.shx
    • line27at.dbf, line27at.shp, line27at.shx
    • line27bt.dbf, line27bt.shp, line27bt.shx
    • line28at.dbf, line28at.shp, line28at.shx
    • line28bt.dbf, line28bt.shp, line28bt.shx
    • line28ct.dbf, line28ct.shp, line28ct.shx
    • line28dt.dbf, line28dt.shp, line28dt.shx
    • line29at.dbf, line29at.shp, line29at.shx
    • line29bt.dbf, line29bt.shp, line29bt.shx
    • line30t.dbf, line30t.shp, line30t.shx
    • line31t.dbf, line31t.shp, line31t.shx

    Data sources produced in this process:

    • 81_2navt.dbf, 81_2navt.shp, 81_2nav.shx


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

  1. How well have the observations been checked?

    All attribute data were recorded by the chief scientist and entered and checked by the compilers in a consistent manner.

  2. How accurate are the geographic locations?

    A navigation was done by Loran C. Typical Loran accuracy for LIS is about 100 m.

  3. How accurate are the heights or depths?

    Tides are less than 2 m

  4. Where are the gaps in the data? What is missing?

    Complete information is provided for all navigation lines in the data set. Navigation points are spaced at 5 minute intervals (approx) and at course changes or line events (start/end). Continous navigation is not available.

  5. How consistent are the relationships among the observations, including topology?

    No additional checks for topological consistency were performed on this data set.


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:
The U.S. Geological Survey must be referenced as the originator of the dataset in any future products or research derived from these data.

Although this derived data set and it's lineage dataset have been used by the USGS, no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and/or related materials. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials.

  1. Who distributes the data set? (Distributor 1 of 1)

    U. S. Geological Survey
    c/o Larry Poppe
    Geologist
    384 Woods Hole Road
    Woods Hole, MA 02543-1598
    USA

    (508) 548-8700 x2314 (voice)
    (508) 457-2310 (FAX)
    lpoppe@usgs.gov

  2. What's the catalog number I need to order this data set?

    Long Island Sound: 81_2navt.shp

  3. What legal disclaimers am I supposed to read?

    Although this derived data set and it's lineage dataset have been used by the USGS, no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and/or related materials. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials.

  4. How can I download or order the data?

  5. Is there some other way to get the data?

    None

  6. What hardware or software do I need in order to use the data set?

    The 81_2 navigation overlay is available in an ArcView shapefile format. The user must have ESRI's ArcView 3.0 or greater software to read and process the data file. In lieu of Arcview, the user may utilize another GIS application package capable of importing the data.


Who wrote the metadata?

Dates:
Last modified: 17-Apr-2002

Metadata author:
Valerie Paskevich
U. S. Geological Survey
computer specialist
384 Woods Hole Road
Woods Hole, MA 02543-1598
USA

(508) 548-8700 x2281 (voice)
(508) 457-2310 (FAX)
vpaskevich@usgs.gov

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)


Generated by mp version 2.7.3 on Wed Apr 17 07:22:46 2002