U.S. Coast Guard Marine Safety Office (MSO) Zones Encompassing Louisiana, Geographic NAD83, LOSCO (2000) [zongeog3dbmso]

Metadata also available as - [Outline]

Frequently-anticipated questions:


What does this data set describe?

    Title:
    U.S. Coast Guard Marine Safety Office (MSO) Zones Encompassing Louisiana, Geographic NAD83, LOSCO (2000) [zongeog3dbmso]
    Abstract:
    This is a polygon dataset delineating the boundaries of the three U.S. Coast Guard Marine Safety Office (MSO) zones that encompass the state of Louisiana. The MSO zones are: New Orleans, Morgan City, and Port Arthur.
    Supplemental_Information:
    These metadata describe the Arc/Info coverage of name 'zongeog3dbmso' and the shapefile of the same name derived from it.

    The metadata for this data set are encapsulated into several documents and graphics files. The metadata are not complete if you did not receive the following files along with the data set:

    zongeog3dbmso.mtd - this metadata in mp (metadata parser) compatible ASCII text form
    zongeog3dbmso.html - this metadata in HTML form
    zongeog3dbmso_faq.html - this metadata presented as Questions and Answers
    zongeog3dbmso.sgml - this metadata in SGML form
    zongeog3dbmso1.gif - thumbnail graphic of data set
    zongeog3dbmso2.gif - larger view of the data set illustrating the source of the bounding arcs
    
    The attribute and/or geometric component(s) of the data are provided as Arc export (.e00) file(s) and the corresponding three part (.shp, .shx, .dbf) shapefile(s) or standalone .dbf file(s) in the case an export file is a standalone INFO file. You should have received the following as part of the dataset:
    zongeog3dbmso.e00
    zongeog3dbmso.shp
    zongeog3dbmso.shx
    zongeog3dbmso.dbf
    zongeog3dbmso.prj - coordinate system specification file for shape
    

  1. How should this data set be cited?

    Louisiana Oil Spill Coordinator's Office (LOSCO), 20000205, U.S. Coast Guard Marine Safety Office (MSO) Zones Encompassing Louisiana, Geographic NAD83, LOSCO (2000) [zongeog3dbmso].

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -97.000
    East_Bounding_Coordinate: -88.000
    North_Bounding_Coordinate: 33.960
    South_Bounding_Coordinate: 25.617

  3. What does it look like?

    <URL:zongeog3dbmso1.gif> (GIF)
    thumbnail graphic of data set
    <URL:zongeog3dbmso2.gif> (GIF)
    larger view of the data set illustrating the source of the bounding arcs

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

    Calendar_Date: 01-Jul-1997
    Currentness_Reference:
    Date of edition of Code of Federal Regulations describing the MSO zone boundaries.

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

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

      • GT-polygon composed of chains (3)

    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.01. Longitudes are given to the nearest 0.01. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257.

  7. How does the data set describe geographic features?

    zongeog3dbmso.pat or zongeog3dbmso.dbf
    attributes of MSO zone polygons (Source: 3001, Inc.)

    mso_zone
    name of MSO zone (Source: 3001, Inc.)

    Free text MSO zone name

    zongeog3dbmso.aat (not present in shapefile)
    attributes of MSO zone bounding arcs (Source: 3001, Inc.)

    source
    source for arc (Source: 3001, Inc.)

    ValueDefinition
    CFRthe arc was constructed by coordinate geometry using the CFR description
    constructedthe arc was added to bridge a gap in the other data
    countyp020the source of the arc was COUNTYP20
    EEZthe source of the arc was EEZ
    hydrogl020the source of the arc was HYDROGL020
    hydrogp020the source of the arc was HYDROGP020


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?

    LOSCO gratefully acknowledges the Minerals Management Service for providing the Exclusive Economic Zone component of this data set and the USGS for providing the county boundary and hydrography data necessary to delineate other parts of the MSO zone boundaries.

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

    Louisiana Oil Spill Coordinator's Office
    c/o David Gisclair
    Technical Assistance Program (TAP) Director
    Louisiana Oil Spill Coordinator's Office
    Baton Rouge, LA 70804

    (225) 219-5800 (voice)
    (225) 219-5802 (FAX)
    <URL:mailto:tapgis@linknet.idt.net>


Why was the data set created?

Delineates the jurisdictional boundaries of MSO zones. For the purposes of responding to an oil spill emergency (a LOSCO concern) it identifies the MSO office to be contacted for assistance that is dependent on the area of Louisiana in which the spill occurs. This data set is appropriate to identify MSO zones pertinent to Louisiana. It is not appropriate to identify the MSO zones pertinent to other states.


How was the data set created?

  1. From what previous works were the data drawn?

    CFR (source 1 of 4)
    US Government Printing Office, 1997, 33 CFR Ch1 (7-1-97) section 3.40-15, section 3.40-17, section 3.40-30.

    Type_of_Source_Media: paper copy
    Source_Contribution: description of MSO boundaries

    EEZ (source 2 of 4)
    Service, Minerals Management , unpublished, 'Exclusive Economic Zone Line in the Gulf of Mexico'.

    Type_of_Source_Media: computer file
    Source_Contribution:
    delineation of most oceanward limit of this data set, the Exclusive Economic Zone, at a nominal 200 nautical miles from the shoreline.

    COUNTYP20 (source 3 of 4)
    U.S. Geological Survey, 199911, County Boundaries of the United States.

    Online Links:

    Type_of_Source_Media: computer file
    Source_Contribution:
    Provided delineation of state shoreline (sea/land boundary) for Texas and Mississippi. The sea/land boundary, in combination with lines of fixed longitude, provide several inflection points for the MSO zone boundaries. The shoreline was used as a buffer object to build a boundary portion at 10.3 nautical miles from the coast. Provided delineation of county boundaries when the MSO zone boundary followed them.

    HYDROGL020, HYDROGP020 (source 4 of 4)
    U.S. Geological Survey, 199911, Hydrography Features of the United States.

    Online Links:

    Type_of_Source_Media: computer file
    Source_Contribution:
    Provided line (HYDROGL020) and polygon (HYDROGP020) water features defining portions of the MSO zone boundaries, namely the Trinity River (TX) and Lake Livingston (TX).

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

    Date: 30-Jan-2000 (process 1 of 1)
    The CFR description was used as a guide to produce those portions of the zone boundaries defined by lines of longitude and points of latitude and longitude. The CFR description was used to select those counties whose boundaries comprised a portion of an MSO boundary from the COUNTYP20 dataset. The COUNTYP20 data set was used as a buffer source to produce a portion of MSO zone boundary defined as 10.3 nautical miles from the coast, and the means to define turning points in the boundary at lines of fixed longitude. The Trinity River was selected from the HYDROGL020 data set and Lake Livingston was selected from the HYDROP020 data set. The arcs comprising those features selected (or built) as described above and the EEZ data set were attributed to encapsulate the source name.

    The arcs described above were placed into a common data set and edited to remove all arc segments extraneous to the MSO zone delineation. Short arcs were constructed as necessary to bridge gaps between the component data. A long arc was constructed at 30.5 degrees north latitude to close the New Orleans MSO zone to the north. This was necessary to resolve incomplete description of that boundary in the CFR source and does not impact the delineation of MSO zones across the state of Louisiana.

    The arcs were built into polygons and densified with intermediate vertices at 1 minute (0.01667 degree) intervals.

    Person who carried out this activity:

    3001, Inc.
    c/o Hugh Phillips
    GIS Analyst
    3655 SW 2nd Ave., Suite 3C
    Gainesville, FL 32607

    (352) 379-3001 (voice)
    <URL:mailto:hphillips@gnv.3001data.com>


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

  1. How well have the observations been checked?

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

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

    Includes the MSO zones which cover Louisiana except for a sliver of the Mobile MSO covering a small piece of southeast Louisiana offshore territory. The northern boundary of the New Orleans MSO was constructed somewhat arbitrarily because the description in the Code of Federal Regulations was not clear.

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

    Topological and labeling tests, and attribute statistics were obtained with a quality assurance AML (qa_report.aml). This report is used to expose inconsistencies and problems in the data and its attributes, and to verify correction of those errors when corrections are possible. No errors were detected in labeling or topology.

    These data represent what the data processor (3001, Inc.) believes was intended by the boundary description from the Code of Federal Regulations, even though that description is, in cases, logically inconsistent, discontinuous, or ambiguous.


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:
These unaltered data may not be redistributed without all of the elements of the metadata listed in the Supplemental_Information section of this metadata document. It is recommended that third parties wishing to use these data obtain them from the Distributor listed in this metadata document.

If these data are altered or incorporated into another dataset, they are not to be redistributed without also: altering the name of the dataset, including a Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998) compliant metadata file that describes the dataset and reflects the alteration steps that makes the new dataset different from this one, and citing this dataset in the metadata as a source for the altered dataset using the source citation specified below.

If these digital data are used in the production of a report or in the compilation of a standalone printed map, then this dataset is to be cited in the report or on the map using the source citation specified below.

The following source citation is to be used when citing this dataset: LOSCO Environmental Baseline Inventory Dataset 'U.S. Coast Guard Marine Safety Office (MSO) Zones Encompassing Louisiana, Geographic NAD83, LOSCO (2000) [zongeog3dbmso]'

Users hereby agree to abide by the use and reproduction conditions specified above. By using the data described in these metadata, the user acknowledges that the terms and conditions of use have been read and that the user is bound by these criteria.

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

    Louisiana Oil Spill Coordinator's Office
    c/o David Gisclair
    Technical Assistance Program (TAP) Director
    Louisiana Oil Spill Coordinator's Office
    Baton Rouge, LA 70804

    (225) 219-5800 (voice)
    (225) 219-5802 (FAX)
    <URL:mailto:tapgis@linknet.idt.net>

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

    zongeog3dbmso This is the explanation for the obtuse name: <URL:http://www.3001data.com/metadata/systematic_name.html>

  3. What legal disclaimers am I supposed to read?

    The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the Louisiana Oil Spill Coordinator's Office (LOSCO) be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The LOSCO does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form.

    These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.

    Although these data have been processed successfully on computers at the LOSCO, no guarantee, expressed or implied, is made by LOSCO regarding the use of these data on any other system, nor does the act of distribution constitute or imply any such warranty. Distribution of these data is intended for information purposes and should not be considered authoritative for navigational, engineering, legal and other site-specific uses.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 05-Feb-2000

Metadata author:
3001, Inc.
c/o Hugh Phillips
GIS Analyst
3655 SW 2nd Ave., Suite 3C
Gainesville, FL 32607

(352) 379-3001 (voice)
(352) 377-4234 (FAX)
<URL:mailto:hphillips@gnv.3001data.com>

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


Generated by mp version 2.7.3 on Fri Dec 29 23:37:10 2000