U.S. Geological Survey

---------------------------------------------------------------------------

Metadata for SHORE

 Table of Contents

Identification_Information
     Abstract
     Purpose
     Supplemental Information
Data_Quality_Information
Spatial_Data_Organization_Information
Entity_and_Attribute_Information
     Detailed Description
     Overview
Distribution_Information
Metadata_Reference_Section

---------------------------------------------------------------------------

Identification_Information

Citation_Information
    Originator: Strategic Environmental Assessments Div, OORCA, NOS, NOAA, Alhadeff, S. Jack, ed
    Publication_Date: 1994, 1996
    Title: NOAA Medium Resolution Digital Vector Shoreline of Georgia
    Edition: 1.0
             1.1 Datum change from 1927 to 1983 (North American Datum of 1983)
                 Data Re-projected using North American Datum (NAD83) - September 2000

    Geospatial_Data_Presentation_Format: map and CD-ROM
    Series_Information
        Series_Name: Digital Data Series
    Online_Linkage: ftp://seaserver.nos.noaa.gov/datasets/shoreline/data
    Scale_Denominator: 70000

Description
    Abstract

    INTRODUCTORY INFORMATION

    Official Product Name:  NOAA Medium Resolution Digital Vector Shoreline.

    Introduction/Brief Overview:

    NOAA Medium Resolution Digital Vector Shoreline for Georgia

    Data for the State of Georgia Medium Resolution Digital Vector Shoreline
    was derived from the NOAA Medium Resolution Digital Vector Shoreline for
    the United States.

    The NOAA Medium Resolution, 1:70,000, Digital Vector Shoreline is a high
    quality, GIS-Ready digital document containing the coastline of the
    contiguous United States of America.  The shoreline was created from data
    captured (digitized from scanned images of the master separates of the NOS
    Charts) from over 270 National Ocean Service Navigation Charts and spans
    some 80,000 nautical miles at an average map scale of 1:70,000.  The data
    set is designed for a broad target audience ranging from governmental
    agencies, universities and other research institutions, to the private
    sector, and students, as well as any other concern requiring a general
    purpose digital shoreline layer for GIS and cartographic projects.

    Currency of Product:
    Data sourced during compilation was the most up to date available at the
    time.  Revision edition dates range from 1988 through 1992, depending on
    the revision cycle of the individual chart.  Revision dates for the sources
    charts used in compilation are supplied as a part of the descriptive
    attribute data listings associated with each coastline section.

    Quality Assessment:
    Spatial data was derived directly from National Ocean Service Navigation
    Charts.  The NOS Chart Products meet or exceed National Map Accuracy
    standards (hard copy)-- the digital data supplied in this compilation
    should, when plotted at scale, meet or exceed these same cartographic
    standards.

    Keywords:
    Shoreline, Navigation, Coastline, NOAA, NOS, GIS, Vector


    Purpose

    The product is designed to meet the demanding needs of a broad target
    audience. Potential subscribers include government agencies, universities
    and other research institutions, the private sector, and students, as
    well as any other concern requiring a general purpose digital shoreline
    layer for GIS and cartographic projects.


Supplemental_Information
    Procedures_Used
    Arc/Info was used to extract the portion of the NOAA Shoreline file in
    the State of Georgia.  The US Geological Survey 1:100,000 digital county
    boundary data processed in Arc/Info was used as a CLIP cover to the US
    compilation of the NOAA data. The resulting Georgia Shoreline has been
    projected to the Albers Projection outlined in the documentation.

    This following narrative from NOAA describes all of the various procedures
    which went into constructing the shoreline data contained on this CD.
    This information provided here is taken unabridged from the original

    Introduction:
    The construction of a data set such as this shoreline involves many steps,
    some brief and simple, but most lengthy and of a complex nature.  In
    attempting to document these various processes it was soon realized that,
    because of the complexity of the efforts, lengthy and highly detailed
    treatises  were called for, if one hoped to supply instruction and guidance
    suitable for understanding, and, more importantly, for successful execution
    of the project.  As a result, some seven documents, schematic in format, were
    generated to chronicle the procedures used, constituting over 60 typed pages
    of text.

    The inclusion of these procedural documents into this archive required
    structuring them into topical process groups.  The following is a listing of
    the various topical groupings.

    Scanning the master manuscript
    Vector/raster registration (ArcEdit capture only)
    Data Capture
    Data Capture Guidelines
    Vector layer construction
    Section assembly
    Data verification
    Final archive

    The information provided outline, step-by-step, as applicable, the 
    processing required to carry out each of the various stages of the 
    production effort.  Where a step-by-step approach is not feasible, or is 
    inappropriate, a series of rules or guidelines are provided for completing 
    the process.  Data set encoding and quality control measures are also 
    outlined here as well.

    Informational Overview of Processing Stages and Procedures

    Generation of the NOS/SEAD High Resolution Digital Shoreline Product was
    accomplished in five stages: data capture, chart cover construction, segment
    assembly, verification, and final formatting/archive.  Stage 1, data capture
    involves the initial conversion of analog source data, NOS Coastal Series
    Navigational Charts, into a digital vector image.  During stage 2, the raw
    vector image is converted into an Arc/Info GIS Coverage.  In addition,
    during this phase of the work, the data is corrected (gross error removal),
    topologies are constructed, descriptive information is added, and an
    intermediate archive is created.  The third stage is segment assembly.  
    Here, the chart cover data is partitioned into regionally contiguous 
    groupings, (referred to as sections), adjacent boundaries are matched, and 
    the individual charts are joined together to produce continuous shoreline 
    segments.

    Following assembly, stage 4, data verification, is initiated. Portions of 
    the sectional data are chosen at random to be plotted coincident with chart
    master sheets (mylars) and compared.  Discrepancies are noted, corrective
    action, if required, is taken, and the data re-verified.  The fifth and 
    final stage is formatting and final archive.  The shoreline data is 
    converted into the two ASCII formats for distribution.

    Process Synopsis
    1.   Obtain Black Line Separate of Chart from Coast and Geodetic Survey,
    Nautical Charting Division.
    2.   Scan separate and archive image.
    3.   Capture (digitize) shoreline from scanned raster layer using CAD Heads
    Up or Arc/Info Editing. Carefully check vector image against raster for
    errors and/or omissions.
    4.   Archive captured vector data(Point, Line, and Drawing).  Export data
    (Point and Line) from native CAD into a format readable via ArcInfo's
    GENERATE.
    5.   Generate vector coverage in ArcInfo using exported CAD point and line
    files.
    6.   Create topologies -linear(arc) and polygonal.
    7.   Visually scan covers in search of errors, etc.
    8.   Transform cover into geo-referenced coordinate system.  Check and
    record RMS error.
    9.   Add descriptive attributes, including the arc left and right side
    identifiers (land or water),  to Arc Attribute Table.
    10.  Recheck visually for errors.
    11.  Archive cover.
    12.  If selected, generate proof plot for comparison with chart separate
    master.
    13.  Project cover into national projection (Lambert Conformal Conic) for
    assembly.
    14.  Edgematch chart with adjacent covers using Arc Editor.
    15.  Archive matched vector cover.
    16.  Assemble vector cover with others in primary section.
    17.  Archive primary section coverage.
    18.  Partition primary section covers into regional  units.
    19.  Examine regional unit covers for problems.  Correct as necessary.
    20.  Examine regional covers Arc Attribute Tables for erroneous data and/or
    omissions.
    21.  Archive regional covers.
    22.  Distribute regional covers to beta test sites, place copies on line
    in-house.
    for testing and final checking of cover data.  Correct identified errors
    in data and reverify.
    23.  Reformat to meet Spatial Data Transfer Standard Compliance and
    distribute final version of data on CD-ROM.


    Revisions

    STATUS OF THE CURRENT RELEASE -- Beta Release

    Data is currently available at the reference scale of 1:70,000, nominal.

    Release date for the current data sets are: August 24, 1994.

    Coverage renamed on October 21, 1997 from shoreline to shore in
    preparation for publication to CD-ROM.

    Maintenance/Update frequency: Unknown.


    Reviews_Applied

    The data provided on this CD-ROM has been through several levels of
    quality checking for the purpose of error detection and rectification.
    This is to insure that we deliver a product which is as free of error as
    is possible.  However, in an effort to further improve the quality of the
    data, this release has been designated as beta.  In doing this, you, the
    user, are encouraged to make us aware of any and all problems which you
    encounter with regard to the positional and physiological accuracy of the
    shoreline, and the associated descriptive attributes.  Contact information
    is provided at the end of this document. Your cooperation and participation
    in this phase of the product release effort is greatly appreciated.
    Thank you.

    Quality Assessment:
    Spatial data was derived directly from National Ocean Service Navigation
    Charts.  The NOS Chart Products meet or exceed National Map Accuracy
    standards (hard copy)-- the digital data supplied in this compilation
    should, when plotted at scale, meet or exceed these same cartographic
    standards.


    Related_Spatial_and_Tabular_Data_Sets


    Other_References_Cited
    US Department of Commerce, NOAA, NOS Navigation Charts


    Notes

    DATA was RECREATED as an ARC/INFO Coverage

    The files in this directory are the geography files for the data set
    stored in a textual, ASCII, format.

    Each feature (arc) is stored sequentially in the data files beginning
    with a simple, uniquely numbered identification number, followed by the
    listing of vertices, (longitude and latitude).  The arc records are
    terminated with the string END.

    The structure of the files are as follows:

    For each arc the record structure is...

    n
    longitude 1 latitude 1
    longitude 2 latitude 2
    longitude 3 latitude 3
    .
    .
    .
    longitude n latitude n
    END

    where -n is the features unique identification number

    -the latitude and longitude pairs are the vertices which comprise the arc
    -END marks the end of the record for a given arc.

    All of the arcs in a section are represented in this format-- it is
    repeated sequentially for each.

    Note: The feature identification number corresponds to the
    identification number listed in the attribute listings (files with .ATR
    extension).  Use this number to index (join) attributes.

    DISTRIBUTION INFORMATION

    This data was produced by, and is available from:

    The Strategic Environmental Assessments Division
    Office of Ocean Resources, Conservation, and Assessment
    National Ocean Service
    National Oceanic and Atmospheric Administration

    Mail Stop N/ORCA1X2
    1305 East-West Highway
    Silver Spring, MD 20910

    301-713-3000  -voice, general office
    301-713-4384  -facsimile, general office
    This product is also distributed by:
    Marine Geology and Geophysics Division
    The National Geophysical Data Center
    National Ocean and Atmospheric Administration
    Mail Code E/GC3
    325 Broadway
    Boulder, CO  80303-3328

    303-497-4384 -voice
    303-497-6513 -facsimile


Time_Period_of_Content
    Range_of_Dates/Times
    Beginning_Date: 1988
    Ending_Date: 1992
    Currentness_Reference

    Data was sourced from National Ocean Service Coastal Series, Small Craft,
    General, and Harbor Charts of current addition (current as of date of
    capture).  These charts are available for unrestricted release (sale) to
    the general public.

    Data Sourced from the State of Florida

    The source of the data from the State of Florida actually points back to
    the National Ocean Service.  In the early 1980s, the NOS, through a
    private contractor, digitized the entirety of their navigational chart
    collection for the contiguous, lower 48 States of the Continental U.S.
    The State of Florida, in the mid 1980s, procured a copy of the Florida
    Section of this shoreline


Status
    Progress: Data is currently available at the reference scale of 1:70,000, nominal.
    Maintenance_and_Update_Frequency


Spatial_Domain
    Bounding_Coordinates
    West_Bounding_Coordinate: -82.09247806
    East_Bounding_Coordinate: -80.7897329
    North_Bounding_Coordinate: 33.55522577
    South_Bounding_Coordinate: 30.69737719

Keywords
    Theme
        Theme_Keyword_Thesaurus: None
        Theme_Keyword:  NOAA Medium Resolution Digital Vector Shoreline
    Place
        Place_Keyword_Thesaurus: None
        Place_Keyword:  State of Georgia
    Stratum
        Stratum_Keyword_Thesaurus: None
        Stratum_Keyword:
    Temporal
        Temporal_Keyword_Thesaurus: None
        Temporal_Keyword:

Access_Constraints

Use Restrictions: Not to be used for navigation or navigation planning.

Security Classification:  Unclassified.


Use_Constraints

Implied Accuracy of the Supplied Information:

The data supplied here is a compilation of information collected from some
270+ current or pre-release National Ocean Service Navigation Charts. In
compiling this product we made no attempt to ascertain the congruency
between the charted data, and the real world.  Our objective was to simply
capture the representative coastline as provided to us via the NOS Chart.
Every effort was made to capture the shoreline on these charts as
faithfully as our skills and technology allowed, and there is every
indication that we were successful to this end.  However, in doing so, we
automatically conveyed the character (all aspects, both good as well as
bad) of that data to our digital product.  A character which may or may
not be in agreement with the real world.  Because of this, the user is
advised to exercise caution in making any assumptions about the
fallibility, or infallibility, of the spatial information supplied here--
especially when circumstances warrant a high degree of absolute positional
accuracy.

Navigation Disclaimer:

PLEASE NOTE: This data is not to be used for navigation or navigation
planning. here is every indication that we were


Point_of_Contact: See Data_Set_Credit

Products of a magnitude as this archive cannot be attributed to the work
of a single individual.  Rather, such efforts demand the concerted and
dedicated efforts of many skilled and talented people.  Over the span of
the four years during which this product was under construction, I had the
good fortune to have been surrounded by so many whose skills and talents
were truly of the highest caliber-- all of these people are listed herein.
Were it not for their tireless efforts and dedication, this product would
have never been realized. To each of those individuals I wish to extend my
greatest appreciation for a job splendidly done.  Thank you.
Paul Paris,    July, 1994

The Players:
From the Strategic Environmental Assessments Division:
Shanta Ashton
Larry Claflin
Amy Clark
Christopher Clement
Paul Genovese
Richard Huzil
Mark Jacobsen
Marilyn King
John Mitchell
Steve Rohmann
Francine Stadmiller
Christine Taylor

From the National Geodetic Survey:
Pamela Fromhertz
Charles Schwarz

From the Navigational Charting Division:
Richard Cole
Clay Everett
Walter Fijn
Kirby Gean
Pierce Hunt
Ralph Ross

From the National Geophysical Data Center
George Sharman
Peter Sloss


Security_Information
    Security_Classification_System: None
    Security_Classification:  UNCLASSIFIED
    Security_Handling_Description: None

Native_Data_Set_Environment: dgux UNIX, ARC/INFO version 7.0.4

Cross_Reference
    Originator: The Strategic Environmental Assessments Division, OORCA, NOS, NOAA
    Publication_Date: 1994
    Publication_Time:
    Title: NOAA Medium Resolution Digital Vector Shoreline
    Edition: Beta
    Geospatial_Data_Presentation_Form: Map and CD-ROM
    Series_Information
        Series_Name:
        Issue_Identification:
    Publication_Information
        Publication_Place:
        Publisher:
    Other_Citation_Details:
    Online_Linkage: ftp://seaserver.nos.noaa.gov/datasets/shoreline/data
    Larger_Work_Citation:

---------------------------------------------------------------------------

Data_Quality_Information

Attribute_Accuracy
    Attribute_Accuracy_Report: See Logical_Consistency_Report: Chain-node topology present.

Completeness_Report

Geographic Extent of the Products/Completeness:
The NOAA Medium Resolution, 1:70,000, Digital Vector Shoreline
encompasses the entire contiguous United States coastline, some 80,000
nautical miles.  Coverage is divided into four primary units:

1.  East Coast -U.S./Canada Border at the St. Croix River to the
southern tip of the Florida Peninsula (including the Keys)
2.  Gulf of Mexico Coast -Southern tip of the Florida Peninsula (no
Keys) to the U.S./Mexico Border at Brownsville, Texas.
3.  West Coast -U.S./Mexico Border at Baja to U.S./Canada Border at
the Straits of Juan DeFuca.
4.  Great Lakes -All five lakes, in their entirety, including the
connecting waterways (except the St. Lawrence River/Seaway).

For practical reasons the sections were further divided into three or more
components:

Atlantic Coastal Section
ec80_01 -St Marys Inlet Florida to Little River Inlet South Carolina.
ec80_02 -Little River Inlet South Carolina to Cape Henry Virginia.
ec80_03 -Chesapeake Bay.
ec80_04 -Chincoteague Inlet Virginia to Block Island Sound Rhode Island.
ec80_05 -Point Judith to St. Croix River.
ec80_06 -St Marys River, Florida to Florida Bay (including Florida Keys.
Gulf Coastal Section
gc80_01 -Padre Island TX to Bayou Choupique, LA
gc80_02 -Lake Calcasieu, LA to Atchafalaya Bay, LA
gc80_03 -Point Au Fer, LA to Barataria Pass, LA
gc80_04 -Grand Terre Island, LA to Gulfport, MS, incl the Chandeleurs Is
gc80_05 -Biloxi River, MS to Chassahowitza Reefs, FL
gc80_06 -Chassahowitza Reefs, FL to Flamingo, FL
Pacific Coastal Section
wc80_01 -Semiahoo Bay, WA to Yaquina Head, OR
wc80_02 -Alsea Bay, OR to Point Sur, CA
wc80_03 -Point Sur, CA to U.S./Mexico Border
Great Lakes Section
gl80_01 -Lake Superior
gl80_02 -Lake Michigan incl. Lake Winnebago, WI.
gl80_03 -Lake Huron incl. North Channel, and Georgian Bay.
gl80_04 -Lake Erie incl Detroit, St. Clair, Niagara Rivers, and Lake St.
Clair
gl80_05 -Lake Ontario incl. St. Lawrence River to Ogdensburg, NY

Note: The boundary between the United States and Canada along the St.
Lawrence River/Seaway is included only from the Lake Ontario entrance to
Ogdensburg, NY.

Areas not included in the NOAA Medium Resolution, 1:70,000, Digital
Vector Shoreline are the following:

1.  Alaska
2.  Hawaii
3.  U.S. Possessions in the Caribbean and Pacific
4.  Any other non-North American U.S. interest.
5.  No portions of coastal Mexico or Canada (except those mentioned
above) are included.

Overall geographic extent of data (minimum bounding rectangle for entire
data set):

Northwest Corner:               Latitude 49.020 N,  Longitude  -124.762 W
Southeast Corner:               Latitude 24.502 N   Longitude  -66.849 W


Positional_Accuracy
    Horizontal_Positional_Accuracy
        Horizontal_Positional_Accuracy_Report:

        Data set resolution is nominally of a map scale of 1:70,000.  This is in
        keeping with original objectives for the project and the availability of
        NOS Charts at this scale.  Actual resolution of the shoreline data does,
        however, vary locally, as a result of non-continuous coverage of the U. S.
        Coast at the targeted scale.  Actual source chart scales range from
        1:10,000 to 1:600,000, depending on the particular section of coastline in
        question.  Most of the areas captured at non-target scales are quite small
        in extent, i.e., harbors, sections of rivers, channels and interior
        waterways with most charted scales at 1:40,000.  Other areas could be
        assembled only at  smaller, 1,500,000, scales due to limited availably

        of source data. Along the North California an Oregon Coasts, more detailed
        navigation charts are simply not available from the National Ocean Service.
        In the Great Lakes, the Northern Boundaries fall under the jurisdiction of
        Canada and the Canadian Hydrographic Service. NOS coverage in these areas,
        while complete, is none-the-less of minimal resolution, typically
        1:600,000. In spite of this, we chose to use the NOS sources in an effort
        to expedite the processing of the information.

        Horizontal Coordinate System Units:  Degrees and decimal degrees of arc.

        Longitudes all lie in the western hemisphere and are thus represented, in
        all cases, as values less than 0.0.

        Geodetic Model:
        Horizontal Datum:  North American Datum of 1983.
        Note: Source data from charts published using the North American
        Datums of 1902, 1927, and 1983.  1902 and 1927 referenced data was
        converted to 1983 via NOAA, National Geodetic Survey Software
        NADCON, version 2.1.

        Ellipsoid: Geodetic Reference System 1980.
        Semi-Major Axis Dimension(Equatorial):  6,378,137 meters.
        Semi-Minor Axis Dimension(Polar):  6,356,752.3 meters.

        Local Horizontal Control Points: A listing of all horizontal control
        points accompanies each of the Shoreline data sections-- all of the origina
        positions (collected during initial data capture operations) have been
        preserved.



        Quantitative_Horizontal_Positional_Accuracy_Assessment:
            Horizontal_Positional_Accuracy_Value: 40 meters or less
            Horizontal_Positional_Accuracy_Explanation:  Resolution as reported

    Vertical_Positional_Accuracy
        Vertical_Positional_Accuracy_Report:

        Vertical Datum: North American Vertical Datum of 1929.  Horizontal
        positions of the Shoreline are based on a vertical tidal datum.  This is
        typcially Mean Lower Low Water but can vary.  Consult the appropriate
        charts for additional information.

        Topology/Hydrography Reference: No topography or bathymetry is
        recorded in this data set.

        Coordinate Resolution:  Spatial data are stored on the CD-ROM as ASCII
        strings  8 digits in length.

        Minimum distance separating adjacent vertices on an arc is: 5.0 meters,
        ground distance.


Lineage: See Cloud_Cover

Notes:
=============================================================================
TABLE OF CONTENTS
CHAPTER ONE: PROCESSING INFORMATION
-Informational Overview of Processing Stages and Procedures.
-Process Synopsis
CHAPTER TWO:   SCANNING THE MASTER MANUSCRIPT
CHAPTER THREE: VECTOR RASTER REGISTRATION (ArcEdit
Heads Up Only)
CHAPTER FOUR:  DATA CAPTURE
-part A Using Hitachis CADCore CAD Product
-part B Using ArcInfo ArcEdit Heads Up
-Guidelines for Data Capture
CHAPTER FIVE:  VECTOR LAYER CONSTRUCTION
CHAPTER SIX:  SEGMENT ASSEMBLY
CHAPTER SEVEN:  DATA VERIFICATION
-Actions taken in checking and quality controlling Shoreline
-Generating the Verification Plot
CHAPTER EIGHT:  FINAL ARCHIVE AND DISTRIBUTION
=============================================================================
CHAPTER ONE:    PROCESSING INTRODUCTION

See Procedures Used

CHAPTER TWO:  SCANNING THE MASTER MANUSCRIPT

This section describes the steps required to scan an NOS Navigational Chart
Separate for processing in the National Medium Resolution Digital Vector
Shoreline Effort, (or other media not exceeding an E sized template (33 x 44
inches.)

Step 1.  Prepare the Chart Tracking Form for the chart to be scanned.  Fill in
the chart number, revision date, scale, projection, projection parameters,
whether or not rotation is required, and the date.

Step 2.  Remove dust cover and power up scanner.  An ON/OFF rocker
switch is located on the right side of the panel when facing the front of the
unit.  Allow the scanner to warm up (approx 30 to 60 sec.)  The LED display on
control panel should display the number "8.0" when it is ready for operation.

Step 3.  Enter scanner interface software, CADImage, on PC by typing
SCAN at the command prompt.

Step 4.  Select scanning option, "SCANNING", from the CADImage Main
Menu.  Use the keyboard cursor keys to navigate between options on the
Main Menu.  (You will use these same keys to make menu picks throughout
the various sub menus of the CADImage package.)  To make a menu
selection, press ENTER.

Step 5.  Set the media with on scanner.  Gauge size of media using scale
printed along scanner feeder slot on the top of the unit, and use the keypad
on scanner control panel to set the scan width.  Whole number changes can
be made by using the numeric labeled keys to the left of the LED.  Smaller
size steps are controlled using the two arrow keys located below the LED.
As a rule of thumb for sizing, chose scan widths which are slightly larger
than the actual gauged media width.  This provides a small margin of error
should the sheet be canted slightly during loading.

Step 6.  Locate the cardinal direction north on the media and insert sheet
face down into feed slot of scanner, north first, as far as it will go (do
not force. If the chart is in landscape format, wider than it is high, it may
be too wide to fit in to the scanner north first.  In these cases, orient the
chart such that it is face down and north is directed to the right as you
stand facing the front of the scanner.  Landscaped scans will require image
rotation to restore the proper orientation-- this can be done in either
CADImage, or CADCore anytime prior to data capture.  The ready light, a green
LED located on the media load button, will extinguish once the sheet is
correctly inserted.  (Note, the lad button is located in the lower left
corner of the control panel-- the icon on the button is a dog eared rectangle.
Press the load button, and as the scanner feeds the sheet, watch carefully
that there is now crumpling, wrinkling or binding of the media.  If a problem
with the feed is suspected, press the media unload button, located immediately
right of the load button, and hold until the sheet is completely free of the
device.

Step 7.  Set up scan configuration from the Configuration Menu in
CADImage. This menu should be displayed upon selecting "SCANNING"
from the Main Menu.  Use the following set up parameters:

image =

Scan Mode

BiLevel Process = None

Resoluti

Histogram Corr. = prescan

Scan File

All -press ENTER

-use the l

press ENTER to select it.

Step 8.  Enter name of scanned image file. A dialog box will appear and
prompt you to enter the name of the file which will contain the image you are
about to create.  Make sure to enter the full path, including root drive,
along with the name.  Make sure your path is correct-- if it is, press Enter.

Step 9.  Set

of tonal values detected during prescan is next displayed on screen.  This
histogram will be used as  a guide to set the tonal density cut off for the
scan

The default value is shown as a white vertical bar in the histogram.  All
values falling to the left of the threshold are eliminated (recorded as white,
pixel value=0), all those to the right of the threshold are retained
(recorded as a black pixel, value = 1.)  The threshold can be changed using
the left and right cursor keys to advance the bar in the graph left and right,
respectively.  The numeric value of the cutoff is shown in a field below the
histogram.

Most prescan information yields bimodal distribution of tonal values for the
to-be-scanned data.  Most of the tonal information to the left of the default
threshold in the histogram is due to media translucence and base density,
which is, in essence, noise-- something we would like to eliminate from the
final scanned image.  Values to the right of threshold also contain noise, but
are, for the most part, a reflection of the actual media resident information.
In selecting a threshold, rarely will we accept the default, we wish to
eliminate as much of the noise and clutter as is possible, of course, without
deleteriously affecting the actual data.  Specific guidance for selecting a
threshold which is applicable in all instances is not possible since threshold
selection depends on a great many factors, few of which, unfortunately, we
have any control.  Empirical evidence, however, indicates that for most scan
work, setting the threshold just to the right of the second peak in the
histogram (numeric value between 165 and 170) provides good results.  For
the shoreline work,  167 as a starting point and check the image during and
after scanning.  If it is not satisfactory, adjust the threshold accordingly
and re-scan.  In any case, some experimentation may be required to produce a
satisfactory image.

Step 10.  Scan chart.  Following threshold selection press ENTER to begin
the scan.  As chart is fed through scanner, a segment of the image scanned is
displayed in a window on the PC monitor.  Use the left and right cursor keys
to pan across the image from left to right, checking the scan quality as you
go.

Step 11.  Post Scan.  Once the scan is finished,  depress and hold the media
load button until the media is fed completely out of the scanner.  The pc
screen will display the scan configuration menu.  From here you can initiate
another scan  (the configuration set up earlier is preserved for you) just
load another sheet in the scanner, pressing ENTER 7 times to move through the
configuration set up, provide the file name, set a threshold, and start the
new scan.

When you have finished scanning, exit the CADImage program by pressing
ESCAPE to return to the Main Menu and ESCAPE a second time to exit the
software.  Power down the scanner and replace the dust cover.

CHAPTER THREE:   VECTOR RASTER REGISTRATION (ArcEdit Heads-Up Capture Only!).

Step One.  Following completion of scanning of the master manuscript, use
the CADIMAGE software to convert the captured raster from the native
HRF to RLC format.

Step Two.  Transfer image from pc to UNIX environment via ftp -type
binary.

First, place image on GeoCOAST Server (pc operations):

e\:> net logon

e:\>

q:\> cd shorline

q

q:\shorline> e:

e:\> net logoff

Retrieve image from GeoCOAST Server (move into UNIX environment):

(pct)ftp spro
ftp: enter user name: sea_e
ftp: enter password: orcasead
ftp: cd shorline
ftp: type binary
ftp get
ftp: bye

Step Three.  Enter Arc/Info by typing ARC at the command prompt.

Step Four.  Enter ArcEdit by typing AE or ARCEDIT at the Arc prompt.

Step Five.  Set the display device for the edit session:

ArcEdit: DISPLAY 9999 size canvas 1100 850

Step Six.  Set edit environment for the chart image you are about to capture:

ArcEdit: MAPEXTENT IMAGE
ArcEdit: IMAGE
ArcEdit: MAPWARP
ArcEdit: DRAW

Step Seven.  Use the AML ggp.aml to collect the coordinates of the graticule
intersections in the displayed image.

ArcEdit: (ampersand)r ggp

Ggp will initially ask for the NOS catalog number for the chart you are
working on.   After entering the chart number a menu will appear at the
bottom of the display.  Use the menu to capture as many graticule
intersections as can be accurately identified.  Use the zoom options on the
menu to navigate.

The isolation of registration points for the vector layer is done by first
locating a potential location on the chart (paper copy) and then attempting to
find the same point on the image.  Graticule intersections are the best
candidates for these.  Use the ggp pan and zoom options, or the ArcEdit pan
and zoom controls to locate the registration points on the image.  If you are
able to locate the intersection on the image (because of varying degrees of
source material quality and scanning limitations, line work is not always
faithfully reproduced) carefully position the cursor cross hair over the point
and press the number 7 key (collect point.)  This action records the location
of the registration point in image coordinates.  Repeat this procedure,
capturing as many registration points as you can.  You must collect at least
three, but no more than 60.  Five to ten should be sufficient for accurate
registration of image to vector layer.  Try also to select locations for
registration points close to the shoreline on the chart.  This will assist in
eliminating error associated with he section(s) of the graticule located away
from the shoreline data.

Close the ggp session by pressing the number 9 key.

When you exit ggp two files will be created :  the first is .tut, the
charts tic update table--the second is .gvt the charts graticule vector
table.  We will use these two tables to generate the vector chart layer, upon
which the shoreline data will be captured.

Step Eight.  Exit ArcEdit:

ArcEdit: SAVE
ArcEdit: QUIT

Step Nine.  Generate the vector layer:

Arc: GENERATE CC
GENERATE: input .gvt
GENERATE: lines
GENERATE: QUIT

Step Ten.  Register the newly created vector layer to the raster image of the
chart.

        ARC: REGISTER

Following the submission of the REGISTER command, a series of four
overlapping windows are displayed on screen.  One displays the vector layer,
the second the raster image, and the third, not yet displaying anything, and
quite a bit larger in size than the first two, will show the composite of the
overlay between the image and vector coverage.  The forth window contains
dialog information, containing the register commands menu, registration
coordinates, and the results of the transformation computation used to
register the image to the vector layer.  Shuffle the four windows so that they
do not overlap, you will want to see all four simultaneously during the
registration process.

The vector and image windows, you should notice, in addition to displaying
the vector intersections and the scanned chart image, respectively, also
contain a transparent rectangle outlined in either yellow or green.  These
rectangles represent the viewing windows for the image and vector data.
When you display the composite in the "Overlay" window, only those areas
within the two viewing rectangles will be displayed.  You can alter the size
of the viewing rectangles by using the center button of the mouse.  First,
position the mouse pointer either inside or outside the rectangle  and press
the center mouse button.  Notice how the size of the rectangle changes.
Now, place the cursor out side of the rectangle and click the mouse again,
noting the changes.  Experiment with resizing of the viewing rectangle until
you understand and are comfortable with the resizing operation.

The view rectangles can also be repositioned to display different areas of the
vector and raster layers, as desired.  As with resizing, repositioning is
performed using the mouse.  Position the cursor either inside or outside of
the current rectangle and click the left mouse button-- notice the change in
position.  Experiment with repositioning until you understand the process and
are comfortable with it.

Once the viewing rectangles are set, you depress the right mouse button,
while the cursor is located in wither the image or vector windows to display
the composite in the "Overlay" window.

To register the vector and raster layers, start by choosing a graticule
intersection in the vector layer and then resize/position the vector layers
view rectangle such that this intersection occupied the approximate center of
the view.  Position the rectangle of the raster image similarly, doing as best
you can to get the intersection on the image within the view range (this is
not always easy, again due to the limitations in scan resolution coupled with
the resolvability of the video screen.)  When both rectangles are positioned,
press the right mouse button-- the composite will be displayed in the
"Overlay" window.

If you cannot see the same intersection on both the vector and raster layers,
then reposition one or both of the view rectangles in the image and coverage
windows and redisplay.  Once the composite contains the desired
intersections, add a registration link (registration links are used to
register the two layers together>)  To add the link position the mouse cursor
over the image intersection in the "Overlay" window and press the left mouse
button. Next, position the cursor over the vector intersection on the
composite and press the left mouse button again.  This action places a link
between the two positions.  The link is represented visually by a green line
segment drawn between the image and vectors intersection positions.

Continue adding links to as many of the intersections as can be identified on
both the vector and raster layers-- as few as three, but no more than 60.
When you have captured all of the points you could identify, press the "Lock
Image" button in the "Register Actions" window.  This action will perform a
temporary, on the fly transformation of the image and vector layers so that
you can now view the overlain composite in the "Overlay"  port and visually
determine how good the fit is.  (Note that the image and vector view windows
will reset and the rectangles are now coordinated.  If you can the size and/or
position of one, you automatically alter the other simultaneously.)   Use the
view rectangles to pan around the composite, looking at the fit of the
registered vector/raster intersections.  If the registration is perfect, or
near so, the vector and raster intersections will overlay exactly.  This,
however, is unlikely.  Chances are the two will not coincide but instead be
slightly offset from one another.  The acceptable deviation is based on source
chart scale, but should be as small as possible.  Use the following as a
guide in determining whether the current fit is acceptable or not:

1:20,000 scale          5 meters shift, maximum.
1:40,000 scale          10 meters shift, maximum.
1:80,000 scale          20 meters shift, maximum.

Since, at this point, the coordinates for both layers are provided in CAD
units, not meters, you will have to estimate these distances using the
charts legend scale.

Check all registration points for positional errors.

If the visual examination of the fit looks acceptable then press the
"Register" button in the "Register Actions" window to compute the
transformation parameters and errors.  The statistic to review most
critically is the RMS Error associated with the transformation.  Look for
consistency in the values, not just absolute magnitude.  If one or more
points possess an unusually large error statistic, as compared to the others,
then you should be suspect of the quality of the fit of these points, and
also their influence on each other. If you have collected in excess of 15
positions, consider eliminating the outliers and rerunning the registration
in an effort to improve the fit at the remaining locations.

By all means, if there is any question about whether or not to accept or
reject a link, please ask.

Once all of the positions have been checked, and if you are satisfied that
they  are all of sufficient accuracy, press the "Save Transformation" button
in the "Register Actions" window. This saves the parameters of the current
registration/transformation permanently.  Should the current registration be
inadequate, start the process anew by pressing "Unlock Image" from the
"Register Actions" window.

CHAPTER FOUR:   DATA CAPTURE

Part A -Using Hitachis CADCore CAD Product.

The following is adapted from the instructional text "Creating an Arc/Info
Coverage from a Scanned Image:" by Amy Clark of DM/GIS and is to be
used in carrying out data capture operations for the high resolution shoreline
work.

NOTE: CADCore has large hard file memory requirements-- at least 10Mb of
space should be available on the drive containing the CADCore executable
software, and 10Mb (additional) on the drive where the captured vector data
is being stored.

Step 1.  Run the CADCore program by typing "VECTOR" or "CADC" at a
DOS command prompt.

Step 2.  Select the DRAFT option from the main menu.

Step 3.  First, set the view port pattern to display the raster by using the
pull down menus DISP-VIEWPORT-PATTERNS.  Use pattern 4.  This sets up
a large window for detailed work and a smaller window to view the whole
area.  The window can be adjusted during the work session using the DISP-
WINDOW-ZOOM option or with the PGDN and PGUP keys.  To return the
window to the size of the raster use DISP-WINDOWS-RFIT.  At all times
the active window is highlighted in yellow.  Click on the file name in the
upper left corner of the window to change active windows.

Step 4.  Load the raster into both view ports with the FILE-FLOAD-
RLOAD- command sequence-- always include
the raster images full path name when specifying the raster file name.

Step 5.  If the chart was scanned such that north is not oriented toward the
top of the image, you should rotate it prior to digitizing.  To do this select
UTIL-RADJUST-R90ROTAT-1 option from the menu bar.  This will rotate
the image 90 degrees in the counterclockwise direction.

Step 6.  Locate the area on the raster image where you would like to begin
digitizing and zoom in to this area using the WINDOW commands inside the
large view port, or the PGUP and cursor keys to zoom and move laterally,
respectively.

Step 7.  Actual data capture can be accomplished in two ways using
CADCore.  The first is manual tracing and the second is automatic tracing.
Only the former, manual tracing, will be considered here for shoreline work.
Select via the TRACER-TPOLYARC command from the menu bar.  Digitize
the shoreline arcs by moving the  cursor along the arc while pressing the left
mouse button.  To end an arc, press ENTER.

Begin the next arc at the terminal point of the previous one.  Try to position
adjacent arc terminal points such that they are placed as close together as
possible .

Part B  -Using ArcInfo-ArcEdit Heads Up.

Replace default coverage tics (created during generate) with tics from
update table (.tut.
ARC: ARCEDIT
ARCEDIT: EDITCOVERAGE CC
ARCEDIT: DRAWENVIRONMENT ARCS TICS
ARCEDIT: DRAW
ARCEDIT: EDITFEATURE TICS
ARCEDIT: SELECT ALL
ARCEDIT: DELETE
ARCEDIT: COORDINATE KEYBOARD XY
ARCEDIT: ADD
FROM INSIDE ADD MENU:
(ampersand)RUN .TUT
ARCEDIT: COORDINATE CURSOR
ARCEDIT: SAVE
ARCEDIT: QUIT

Step Twelve.  Set up capture environment in ArcEdit.

ARCEDIT: DISPLAY 9999 SIZE CANVAS 1100 850
ARCEDIT: MAPEXTENT IMAGE
ARCEDIT: IMAGE
ARCEDIT: MAPWARP
ARCEDIT: EDITCOVERAGE
ARCEDIT: DRAWENVIRONMENT ARCS NODES DANGLE
ARCEDIT: NODECOLOR DANGLE 2
ARCEDIT: SETLINESYMBOL EDITLIN.SYM
ARCEDIT: DRAW
ARCEDIT: EDITFEATURE ARC
ARCEDIT: NODESNAP CLOSEST
ARCEDIT: INTERSECTARCS ADD
ARCEDIT: WEED 0.00001

Step Thirteen: Capture data.

ARCEDIT: ADD

Digitize the shoreline on screen using the mouse as the digitizer cursor and
the background raster image shoreline data as the guide.  Pressing the center
mouse button, or optionally the number two key on the keyboard, to enter a
node at the beginning of an arc (and to end it as well)-- press the left mouse
button, or the number one key on the keyboard, to enter vertices.  The editor
will automatically place terminal nodes at the 500th vertex position and begin
a new arc for you so it is not necessary to track the vertex counts and
explicitly end each arc.

Capture the depicted shoreline as shown on the image, in its entirety.

Data Capture Guidelines

The rules provided here are adopted for data capture processing of the
NOAA Medium Resolution Digital Vector Shoreline.  These rules were
derived in response to many problematic areas which presented themselves
early in the capture phase of the project.  A definitive and consistent set of
methodologies was required for handling these special cases. as such, the
following eight guidelines were adopted.

1.)  Water bodies depicted as single line features on a 1:80,000 Chart
are not to be included in the shoreline.
2.)  Water bodies which are represented as two-line features, but which
do not visibly communicate with oceanic waters via a two-
line conduit, as shown at the 1:80,000 Chart scale, will not be
included in the NDSS-80.
3.)   Islands having a diameter of less than 20 meters (ground measure)
at the 1:80,000 scale are not to be included.
4.)  Periodically underwater features which do not have a coastline
delineations referenced to the charts vertical datum(solid line)
are not to be included.
5.)  Where an indeterminate shoreline exists (dashed line), it will be
digitized only if a datum referenced (solid) line is not
present.  Otherwise, indeterminate shorelines are not to be included.
6.)  Features such as emergent rocks, and detached man-made features
are not to be included.
7.)  Man made structures which are attached but have water flowing
under all or part of structures are not to be included.
8.) If a 1:80,000 NOS chart is not available, locate one with a map
scale as close  as possible to this value, but of higher
resolution.  If this is not available, then one of lesser scale
can be used.  Extrapolate the features shown to a representation at
the target scale (1:80,000) and test against the remaining exclusion rules.

CHAPTER FIVE:   VECTOR LAYER CONSTRUCTION

Detailed Instructions

---Use these instructions when converting data captured using Hitachi ---
CADCore/Tracer Digitizing Scheme.

Step Zero:

a.) Set up history file...

ARC> cat >>C.HIS

--type in the following information:

chart number=
created
method of capture used (choose one of the following:)
1. Heads Up using Hitachi CADCore.
2. Heads Up using ArcInfo ArcEdit.
3. Conventional Table Digitizing.
scanned from(choose one  of the following:)
1. mylar master copy of chart.
2. mylar reproduction (x-drawing) of master
manuscript.
3. published, water resist paper copy.
enter ^D to terminate history info entry.

b) rename cover to replace the E suffix with a C suffix. (ArcInfo
captured products, only!)

--from within shorelinedir type:

ARC> COPY CE  ../chartdir/CC


Step One:  Generate vector layer from CADCore/Tracer output, <>.lin.
(CADCore captured data only!)

ARC> GENERATE CC
Generate: Input ../lindir/C.lin
Generate: lines
Generate: quit

Step Two: Set coverage tolerances.
-Set value of fuzzy tolerance at 0.001.
-Set dangle length to 0.05

ARC> TOLERANCE CC fuzzy  0.001
ARC> TOLERANCE CC dangle  0.05

Step Three: Construct  initial topology for cover.

a) line (arc) topology

ARC> CLEAN CC  # # # line

b) area (polygon) topology
ARC> BUILD CC poly

Step Four: Generate labels for polygons in cover.

ARC> CREATELABELS CC 0

Step Five:  Rebuild polygon topology.

ARC> BUILD CC

Step Six:  Using ArcEdit, set up new tic set (CADCore capture only!)  and
check for digitizing blunders(both capture processes).

a.) replace tic set with CADCore derived.
ARC> ARCEDIT
ArcEdit: MAPEXTENT CC
ArcEdit: EDITCOVERAGE CC
ArcEdit: DRAWENVIRONMENT tics
ArcEdit: DRAW
ArcEdit: EDITFEATURE tics
ArcEdit: SELECT all
ArcEdit: DELETE
ArcEdit: COORDINATE keyboard xy
ArcEdit: ADD
ArcEdit: (ampersand)run ../pntdir/C.PNT
tic and boundary information.

ArcEdit: LIST
ArcEdit: SAVE
ArcEdit: COORDINATE cursor

-check new tic positions visually.  If an error occurred, check <>.PNT
file for miss-keyed point(s).  Eliminate the erroneous tic(s) from tic file
(remember, you are only required to have four of these guys!), delete all tics
again, and re-add those which remain in the tic file list.

-When all coordinate values in the <>.TIC table are correct, then set
up cover for for edit scan.

b.) check over data for digitizing blunders.
ArcEdit: DRAWENVIRONMENT arcs labels nodes dangle
ArcEdit: NODECOLOR dangle 2
ArcEdit: DRAW

-scan cover while in ArcEdit, searching for blunders.  Blunders are
errors which are obvious to the eye during a cursory scan of the data.  Gaps,
spikes, knots, and other odd looking vectors are all candidates for blunders.
Correct blunders as necessary using the paper chart as a guide..

-as you move along, save (SAVE command) your work from time to
time.  In  the event of a power failure you will be glad you did.

ArcEdit: SAVE

-When you have completed the error scan and correction operation,
quit Arcedit.
ArcEdit: QUIT

Step Seven  Reconstruct Cover Topology

ARC> build C<>C poly    --for polys

Step Eight: Check C<>C for errors.

a) for polygon label errors (leaky polygons)

ARC> labelerrors C<>C

-Make corrections as necessary using ArcEdit, re-BUILD, and check
again.  Only Polygon 1 should be without a label point.  There may be some
dangling arcs at truncations in the shoreline data on the edge of the chart.


Step Nine:  Transform cover.

a) Create a new, empty cover using the ex

ARC> CREATE CD CC

b) Update tic values in <>.TIC.  Replace existing with equivalent
spherical (Lat-Lon) coordinates.

ARC> INFO
ARC

Enter Command> SELECT CD.TIC
Enter Command> LIST
Enter Command> UPDATE

-Update records by replacing existing tic coordinate with
equivalent georeferenced spherical units.  When

completed:

Enter Command> QUIT STOP

-list updated tic file to screen and check update values again
against data sheet.

ARC> LIST CD.TIC

        -at this point look over the output from the LIST command.  Make

certain that the values entered are correct for each coordinate listed--
correct those which are not using UPDATE.  When all coordinate values in the
CD.TIC table are correct, continue...
c) Copy tic file listing to cover history file...

-first, drag-select (just like on a Macintosh) the entire tic table.
ARC> CAT >>C.HIS
type " Original control points..." and ENTER
-press center button of mouse to "paste" table to file
-press ENTER
^D

d) Project cover CD to cover CE
using projection parameter file, appropriate for the coastline you are
working on.

PROJECT.PARAMS.-all coasts

ARC> PROJECT cover  CD  C

E

e) Transform cover

ARC> TRANSFORM CC CE

f) Record transformation table in history file...

-first, drag-select (just like on a Macintosh) the

transformation table.

ARC> CAT >>C.HIS
-press center button of mouse to "paste" table to file
-press ENTER
^D
g) Record transformation error on Chart Tracking form (both map and
ground)

h) Define projection type for <>E

ARC> PROJECTDEFINE cover CE
: PROJECTION mercator    -or polyconic, as applicable.
: UNITS meters
: SPHEROID grs80
: PARAMETERS
-enter projection parameters as prompted-- use chart tracking
sheet                   for guidance


i) reconstruct topologies...

ARC> BUILD CE

j) delete cover CD

ARC> KILL CD all

Step Ten:  Add descriptive items to attribute tables

-Use Additem command.

a) to <>E.AAT.

items to add
l_side 1, 1, i
r_side 1, 1, i
s_scale 7, 7, i
s_chart 7, 7, c
source, 1, 1, i
arc_code,1, 1, i

ARC> ADDITEM CE.aat CE.aat l_side 1 1 i
ARC> ADDITEM CE.aat CE.aat r_side 1 1 i
ARC> ADDITEM CE.aat CE.aat s_scale 7 7 i
ARC> ADDITEM CE.aat CE.aat s_chart 7 7 c
ARC> ADDITEM CE.aat CE.aat source 1 1 i
ARC> ADDITEM CE.aat CE.aat arc_code 1 1 i

Step Eleven:  Enter descriptive topologies/attributes into <>E.AAT.

a) create artificial land polygon(s) by adding one or more dummy arcs

(as required) to shoreline chart data.  The arcs should be added such that the
shoreline and the added dummy arcs effectively create a polygon, or
polygons if more than one land area is involved.  Add label points for the
newly added polygon(s) and set the id attribute for each to 99999.  Leave all
other existing polygons  in cover, including the universe polygon, alone.

ARC> ARCEDIT
ARC> DISPLAY 9999 size canvas 1100 850    --if required.
ArcEdit: MAPEXTENT <>E
ArcEdit: EDITCOVER <>E
ArcEdit: DRAWENVIRONMENT arcs labels nodes
ArcEdit: NODECOLOR node 2
ArcEdit: DRAW
ArcEdit: NODESNAP closest *
ArcEdit: EDITFEATURE arcs
ArcEdit: ADD         -digitize (using mouse) construction arcs*

* make sure that nodes connecting construction arcs and
shoreline are correctly snapped together when they are added.

ArcEdit: CALCULATE arc_code = 2   -tag construction arcs
ArcEdit: DRAW

-look for dangle nodes at junctions between construction and
shoreline arcs (i.e., leaky polygons.)  Correct as required.

ArcEdit: DRAWENVIRONMENT node dangle
ArcEdit: DRAW

-digitize the label point(s)...

ArcEdit: EDITFEATURE labels
ArcEdit: AUTOINCREMENT off
ArcEdit: ADD      -digitize label point(s) for land polygon(s).

Set user id of first label point to = 99999, then digitize label(s).

ArcEdit: SAVE
ArcEdit: QUIT

b) reconstruct topologies

ARC> BUILD C<>E

c) check again for leaky polygons and node errors...

ARC> LABELERRORS <>E

-if all polygons are intact only polygon 1 should have 0 label points.
Polygon 1 is the universe polygon.  Correct if necessary.

ARC> NODEERRORS <>E dangle

-there should be no dangling arcs in the cover at this stage of the
process, correct as necessary.

Step Twelve: Provide left and right side topologies for shoreline arcs using
binary topology rules below.

ARC> ARCEDIT

ArcEdit: MAPEXTENT <>E
ArcEdit: EDITCOVER <>E
ArcEdit: DRAWENVIRONMENT arcs labels
ArcEdit: DRAW
ArcEdit: EDITFEATURE arcs
ArcEdit: SELECT all
ArcEdit: RESELECT lpoly# = 1 and rpoly# > 1
ArcEdit: CALCULATE r_side = 2
ArcEdit: CALCULATE l_side = 1
ArcEdit: SELECT all
ArcEdit: RESELECT rpoly# = 1 and lpoly# > 1
ArcEdit: CALCULATE r_side = 1
ArcEdit: CALCULATE l_side = 2
ArcEdit: SELECT all
ArcEdit: RESELECT rpoly# > 1 and lpoly# > 1
ArcEdit: CALCULATE r_side = 3
ArcEdit: CALCULATE l_side = 3

-Check over work by selecting various polygons at random and
listing values for the variables l_side and r_side, respectively.  Should you
find discrepancies or problems, attempt to correct them.  When you are
satisfied that everything is OK in the cover, continue.

-delete construction arcs and associated label points added above

ArcEdit: SAVE
ArcEdit: SELECT arc_code = 2
ArcEdit: DELETE
ArcEdit: EDITFEATURE label
ArcEdit: SELECT $id = 99999
ArcEdit: DELETE
ArcEdit: SAVE

-attribute other table fields. (Use Chart tracking Form for guidance)

ArcEdit: EDITFEATURE arc
ArcEdit: SELECT all
ArcEdit: RESELECT arc_code ne 3
ArcEdit: CALCULATE s_scale =
ArcEdit: MOVEITEM   to s_chart **

** notice the chart number string in the above MOVEITEM command is
enclosed in single quotation marks.

ArcEdit: CALCULATE source = 1(Arc/Info Heads Up)
=  2(CADCore)
=  3(ArcInfo Digitizer)

ArcEdit: CALCULATE arc_code =1
ArcEdit: SAVE
ArcEdit : QUIT

Step Thirteen: Reconstruct topologies and calculate the shoreline miles
statistic.

a) reconstruct topologies...

ARC> BUILD CE

b) calculate shoreline miles...

ARC> ARCEDIT
ArcEdit: MAPEXTENT <>E
ArcEdit: EDITCOVER <>E
ArcEdit: EDITFEATURE arcs
ArcEdit: SELEC
ArcEdit: STATISTICS
statistics: SUM length
statistics: END

-record the resulting length total (this is the total length of all arcs
in the cover in meters) on the Chart Tracking Form for the cover.  Convert
the meter value to nautical miles (round to the nearest tenth) and enter this
value in the N Miles of Shoreline on the Chart Tracking Form.  (1852 meters
= 1 nautical mile.)

ArcEdit: QUIT

Step Fourteen:   Export the cover data to the archive directory:

ARC> EXPORT cover C<>E ./archivedir/C<>E n
ARC> COMPRESS ./archivedir/C<>E.E00
ARC> COPY C<>E ./archivedir/<>E
ARC> mv c<>.HIS ./archivedir

Step Fifteen:   Clean up the workspace...

ARC> KILL C<>C all
ARC> KILL C<>E all

CHAPTER SIX:  SEGMENT ASSEMBLY

In the Segment Assembly Stage the individual chart covers,  each assigned to
a regionally contiguous group, are appended together to form a single,
continuous section of shoreline.

Step 1.  Project chart from its current projection (Mercator or Polyconic)
into the projects national projection, Lambert Conformal Conic.

ARC> PROJECT COVER CE C

you will be prompted for additional information to complete the projection
recalculation.  At the colon prompt (:) enter the following:

: OUTPUT
: PROJECTION Lambert
: UNITS meters
: SPHEROID grs80
: PARAMETERS
Enter First Standard Parallel  29 00 00
Enter Second Standard Parallel 45 00 00
Enter Central Meridian        -96 00 00
Enter Projections Origin       24 00 00
Enter False Easting  0.0
Enter False Northing  0.0
: END

Step 2  Align/adjust cover edges to match adjacent charts.

Select two covers which are to be matched.  Place set up one as the edit
cover and the other in the background.

ARC> ARCEDIT
:  DISPLAY 9999 SIZE CANVAS 1100 850
:  BACKCOVERAGE
:  BACKENVIRONMENT ARCS
:  MAPEXTENT
:  EDITCOVERAGE
:  DRAWENVIRONMENT ARCS NODES DANGLE
:  NODECOLOR DANGLE 2
:  DRAW

The objective of this step is to prepare the data in each of the chart covers
which comprise a region so that they can be appended together. To do this
we must do three things: first, locate the overlap areas between adjacent
chart covers, second,  isolate positions  (connection points) within these
overlap areas where the two adjoining charts could be connected together
(appended), and finally, edit the data in each chart cover to remove the arcs
in the overlap sections beyond the connection points.   This leaves us with
data whose adjacent boundaries abut, rather than overlap.
Perfect registration between two adjacent covers is unlikely, so we have to
find places in the overlap regions where the charts can be merged most easily
and conveniently, without modifying the data on any one chart any more than
is necessary.  Candidate positions for the matching of two charts are
situations where two arcs intersect, angles of intersection should be close to
180-, if possible, and places where two arcs, while not actually intersecting,
are nearly parallel and closest together.   In addition, the following is a
set of guidelines are to be used in the selection of connection points and in
the actual adjustment of the data:

1.  When there is a difference in chart scale, the higher resolution
charts data takes precedence.  When and where adjustment of the data is
required, move only the lower resolution (smaller map scale) arcs.

2.  If the two charts are of the same map scale, and ground control
points are available, utilize the ground control positions to guide
adjustment. The control points are fixed aids to navigation, (i.e., tanks,
towers, lights, etc.) whose ground positions are known, and which can be
located on the appropriate navigation chart.  We can use these points to get
some idea (qualitative) about how accurate is the placement of the shoreline
data near that particular point by comparing the relative position of the
shoreline and points on the display to their relationship on the chart.  If we
assume that the control locations are reasonably accurate, and we do, then we
adjust the shoreline of both chart covers relative the these points. remember,
adjust as little as possible, we do not want to modify the information any
more than is absolutely necessary to obtain a match.

3.  If the two charts are of the same scale, but no controlling points
are available, then adjust both charts approximately equally to obtain the
match.

4.  If two charts both contain the same island features, and of
differing chart scales, the higher resolution chart takes precedence.  In
cases where both charts are of the same scale, and the islands are complete
polygons in both covers, then you can eliminate either one.  Should a cover
have an incomplete section of an island, or the terminator of a peninsula,
while the adjacent chart contains the features in their entirety, then remove
the data from the incomplete chart.

5.  Should no overlap exist between two adjacent coverages, and the
distance separating them is greater than 1 km, the missing section(s) should
be located on the appropriate navigational charts, digitized, and included in
the existing data.  If the gap is less than 1 km, an estimation arc (arc_code=
5, integrity = 5) can be added to connect the two adjoining covers.

When you isolate connection point locations, split the arcs at these points
and delete the arc section beyond it in the overlap region.  Next, swap edit
and back covers, split the arcs of the new edit cover at the connection points
and delete the tails.  Try to position the terminal nodes of the individual
covers such that they are as close to coincident as is possible to those of
the adjacent cover.  If it is necessary to move nodes/vertices on one or both
of the covers to gain coincidence, refer to the edge matching rules above.

Several of the ArcEdit commands useful in matching the two covers are
listed below:

SPLIT
UNSPLIT
VERTEX MOVE
VERTEX ADD
VERTEX DELETE
NODE
MOVE

It is important to stress that when performing the adjustment, every effort
should be made to keep data modification to a absolute minimum.

All covers in a region must be properly edge matched prior to joining.

Step 3.  Append chart covers to create the regional section.

ARC> APPEND  line all

Enter cover 1: C        -name of 1st cover.
Enter cover 2:  C       -name of 2nd cover.

Enter cover 3:  C       -name of 3rd cover.
.
.
.
Enter cover n:  C       -name of nth cover.

Enter cover n+1: end

where n is the number of chart covers which make up the region.

Step 4.  Connect charts segments in regional cover.

The Append step places the individual charts making up a section into the
regional cover, but does not actually join them to the connection points. This
must be done manually using the Arc Editor.  (Actually, there are a number of
ways in which the terminal nodes of the adjacent covers could be connected,
or "snapped" together, using ArcInfo.  With many of these techniques,
however, you sacrifice some or all  positional control during processing.
Since it is desired to maintain strict control over the modification of the
shoreline data at all stages of the process, we choose not to employ them
opting, instead, to retain as much control as we can.  The drawbacks to this
approach are manifested in increased time and effort required to complete the
process, and the greater likelihood of operator error.)

Set up the following environment in ArcEdit:

ARC> ARCEDIT
ArcEdit: MAPEXTENT
ArcEdit: EDITCOVERAGE
ArcEdit: DRAWENVIRONMENT arcs nodes dangle
ArcEdit: NODECOLOR dangle 2
ArcEdit: DRAW
ArcEdit: EDITFEATURE arcs
ArcEdit: NODESNAP closest  100  - set snap distance to 100m.

Locate nodes (dangling nodes/arcs) which are to be connected.  Select
one of the arcs and the node (here we treat the node as a vertex and, as such,
edit it using the VERTEX edit commands in ArcEdit) and move it atop the
node of the adjacent chart segment (previously the adjoining cover) where it
should be connected.

ArcEdit: SELECT         - select arc.
ArcEdit: VERTEX MOVE    - select vertex.

The 1 key (the left mouse button) selects vertices.  The selected vertex is
marked using a small, transparent triangle.  If the vertex selected (marked by
the selection triangle) is the correct one then press the 4 key, position the
mouse cursor over the node to which you will snap to and press the 1 key
(left mouse button.)  If the two nodes are within the snap tolerance you
specified (100 meters), they will snap together automatically.  A successful
snap is indicated by the placement of a pseudo node (diamond shaped
symbol) at the position where the two dangling nodes were located.

If the selected vertex is not the one you intended to select, use the 2 key to
"walk" your way along the arc, vertex by vertex, until the desired one is
selected.  Then , press the 4 key and move it as described.

You will "snap" the terminal nodes at each of the connection points in the
regional cover.  When you have completed connecting the chart segments in
the regional cover, save it and exit ArcEdit.

ArcEdit: SAVE
ArcEdit: QUIT

Step 5.  Reconstruct arc-line topology.

ARC> BUILD  line
-Note: We do not want to maintain polygonal topologies in regional data sets.
Step 6.  Export and archive the regional cover.

ARC> EXPORT COVER   n

Copy and compress the resulting export file and store in the local archive
subdirectory.  Also, place a copy of the export archive on other back up
media and store off site, if possible, in the event of data loss in the local
file system.

CHAPTER SEVEN: DATA VERIFICATION

Actions taken in checking and quality controlling Shoreline information.

Descriptive data was furnished to give users information describing the
source of the spatial components (arcs) as well as provide a brief, and
qualitative estimate of the integrity of the sourced elements.  Confidence in
the accuracy of these data are high, however, because the attribute
information was quality checked via manual scanning of the tables, it cannot
be considered free from error.

Several data checking methodologies were employed in making data quality
determinations-- the following is a brief synopsis of these efforts:

1.  During data capture, and immediately following, the vector data was
checked directly against the raster background for omissions, redundancies,
and digitizing errors.

2.  As a part of the initial phases of construction, the vector data was once
again scanned visually for errors and/or inconsistencies.

3.  The geo-referencing transformation RMS error provided us a means to
check our data registration and control point capture techniques.

4.  Prior to completion of coverage assembly, each chart section was once
again visually scanned and compared to the NOS Chart sheet.

5.  Proof plots a E-plot size were generated for select areas of shoreline.
These plots were scaled to allow direct overlay and comparison with the
original NOS Chart Separates.
6.  Each shoreline coverage attribute table (Arc Attribute Table) was manually
checked for erroneous data or omissions.

7.  Each section was checked finally for intersections, dangling arcs (except
at edges), and for nodes with valence values > 2.  The data was then
renoded.
8.  The data set was sent to various users within NOAA, as well as to several
State Agencies, and other private concerns.  Each recipient was asked to use
the data as they saw fit, keeping an eye out for problems, or potential
trouble spots, and report back to us any problems.   Forty four problems were
reported using the supplied Data Defect Reporting Forms (see list below)
from the beta test groups.  All of the reported defects have been rectified.

Generating the Verification Plot:
These instructions describe the process used to generate a verification plot
for selected portions of the regional shoreline cover data to be checked and
compared with the master copy.

This work is to be performed on the PC using DOS version 5.0 and
pcArcInfo version 3.4D+.

Step 1.  Obtain a master copy (mylar sheet) of the chart or charts in the area
to be checked from the appropriate Charting Division Section.

Step 2.  Overlay a clean, E-sized, sheet of vellum on the master copy and
locate two  positions on the master for which accurate ground positions are
known-- these will be used as registration points in generating a verification
plot.  The intersection lines of the charts graticule are probably the best
choice for these-- select one in the lower left corner and the other in the
upper right corner of the copy.  The only requirement is that the two points
be located within the confines of the charted data-- make sure the points are
within minimally enclosing rectangle as defined by the shoreline data itself,
and not the neat line of the chart.  Use a sharpened pencil to mark and
number these two positions very carefully on the vellum overlay, labeling
them as registration points 1 and 2, respectively.  Make such the vellum is
held flat and motionless atop the master copy when marking.  Also, using a
Post-it Note, or some other non-permanent stick on label, mark the locations
of the points  (registration points 1 and 2) on the master copy-- be certain t
number them correctly.

Step 3.  Prepare the digital over plot data to be used in the verification
plot.
a.)  Enter the two registration point coordinates collected in step 2,
above, converted from DMS to DD format (remember to keep west longitudes
negative), into a text file and project this file using the Arc PROJECcommand.
The  following formula can be used in converting between GP formats:

DD = Degrees + Minutes/60 + Seconds/3600

Using the DOS 5.0 screen editor, EDIT:  (If you are in the pcArcInfo
environment, you will have to exit to use EDIT.  If you do not wish to do
this, QEDIT, or another text editor could be used in lieu of EDIT.)

f:> EDIT

when the edit window is displayed enter the two coordinates pairs,

longitude1 latitude1
longitude2  latitude2

save the file and exit EDIT.

From inside ArcInfo project the file from decimal degrees (GPs) to Mercator
meters.

ARC> PROJECT FILE

:INPUT
:PROJECTION geographic
:UNITS dd
:SPHEROID GRS80
:PARAMETERS
: OUTPUT
: PROJECTION mercator
: UNITS meters
: SPHEROID GRS80
: PARAMETERS
Enter central meridian (dms)  -122 45 00*
Enter latitude of true scale (dms) 36 29 45*
False Easting: 0.0
False Northing: 0.0
: END

* use values for central meridian and latitude of true scale applicable to the
charted data you are verifying.  Data entry here is in DMS format only.

Save this file and quit the EDIT program.

Create a preliminary map composition for the verification data.

ARC> ARCPLOT
: DISPLAY 4
: PAGESIZE 33 44
: MAPEXTENT
: MAP
: OPC3
< you will be prompted to enter the full name of file containing
projected registration points>

: ARCS
: --add any labeling or other additional information now, if you wish--

-- examine the map on screen at this point-- make certain that the two
registration points are visible, as well as all of the shoreline data which is
to be included in the verification plot.  If you cannot locate the
registration points on the map on screen, enter the command MFRESH to redraw
the map composition.  If you still cannot see these points, check the
coordinates of the points against the shoreline data map extent-- you cannot
proceed with the verification process if both registration points are not
included in the map/plot file you are now creating.  The registration points
should fall within the zone bounded by the map extent of the shoreline
coverage.

When you are ready to exit the map composer enter:

: MAP END

d.)  create an ESRI 1039 plot file from the preliminary map
composition above:

: DISPLAY 1039
Enter name of plot file
: PAGESIZE 33 44
: MAPEXTENT
PLOT
: QUIT

Step 4.  Export the over plot plot file to an ESRI 1039 graphics interchange
file.

ARC> EXPORT PLOT  name of over
plot plot file> n

Step 5.  Convert the ESRI graphics interchange text file to an over plot file
using the over plot conversion utility.

ARC> OPC3
the name of the converted file will be the same root

Step 6.  Set up and prepare media and plotter for over plot.

a.)  Power up plotter and let it run through its initialization sequence.
b.)  Load vellum into plotter.
c.)  Check the pen carousel making sure that the digitizing site is
installed in    one of the pen slots (if you do not know what the
digitizing site is, ask.)
d.)  Return the carousel to the plotter, and select the digitizing site
using the pen select keys on the front panel.
e.)  Map the registration points to the plotter scaling points.  Two
scaling points, referred to as P1 and P2, are programmed into the HP
7585bs ROM.  These points provide the means by which data can be
positioned and scaled on the media.  By changing the locations of P1
and P2, both relative to one another, and with respect to the
plotting sheet, and changing the coordinate values assigned to these
two points, we can effectively translate, rotate, mirror, and re-
scale our plotted output as we please.  In taking advantage of these
control features, we can effectively position our plotted data such
that it is correctly oriented with respect to any information which
is already on the media.  This technique is known as coincidence or
over plotting and we  utilize this capability in producing the
verification plot.

To map the shoreline data registration points to the plotters scaling points,
P1 and P2, we must perform two operations on P1 and P2:  first, we physically
shift their positions  within the hard clip limits so that they are coincident
with the registration points marked on the plotting media, and secondly, we
assign the actual coordinates of the registrations points, in 1039 plot file
units, to them.  The first operation is done as follows:

Using the joystick on the front panel of the plotter, position the digitizing
site so that it is over the first registration point on the media (make
certain that you position the site over the correct registration point when
performing the mapping, map registration point 1 to P1 and registration point
2 to P2).

Press the PEN DOWN key on the front panel.  Look down through the top
of the site-- you should see a small black dot, this is the alignment mark. Us
the joystick to carefully position the sites alignment mark over the
registration point.  Align the two points as accurately as you can, this is
very important! When you are satisfied with the alignment, press the ENTER
key followed by the P1 key, both on the plotter front panel.  Now, press
PEN UP.  Repeat this procedure for the second registration point and P2.
When these are aligned, press ENTER  followed by P2.   Lastly, press PEN UP.

Check the alignment after you have finished by pressing the P1 key. The site
should position itself directly over the new location of P1.  Press PEN
DOWN and look down through the site glass-- you should see the site mark
and registration point aligned.  Now, press the P2 key.  The site will move
over the new location of P2, that is, on top of the second registration point
on the sheet.  Check this point for accuracy as you did P1.  If there is any
discrepancy or change in alignment, repeat the remapping process, above.

Step 7.  Plot the over plot data.

--to initiate plotting of the over plot data set use the DOS COPY
command to copy the over plot file (.OPC extension) to the plotter.

ARC> COPY  COM1

the plot should begin immediately, first the two registration points
should be drawn.  The points will be red in color or whatever color is in pen
holder number 2 on the carousel.  The line work of the shoreline will follow
in the color of the pen in pen slot number 1,  probably black.

Step 8.  Perform the data verification between the digital shoreline and the
master.

--When the plot is complete, unload the vellum from the plotter.  Lay
the vellum sheet over the master copy of the chart and align the registration
points on the vellum with the concomitant positions on the master.  Look
over the plotted and master data and compare the locations of the two.
Ideally, the two will be coincident, that is, they should exactly overly/
underline on another.  As specified in the statement of work for the shoreline
project, the digital data must not deviate from the chart data by more than
0.25 inches, which is approximately a line width of a shoreline weight line
on a 1:80000 map coastal series chart. Mark areas where the shoreline appears
to deviate from the master by more than a line width.  Areas where
discrepancies between the over plot and the master copy are found might
indicate that the shoreline data requires reworking, or, in the worst case,
replacement.  Detailed guidance in these instances, short of a skeletal set of
instructions, is well beyond the scope of this document.  Therefore, we will
make determinations on these "deviation" incidents on a case by case basis.

Note: It is a good idea to do the comparisons between the verification plot
and the master copy as soon as possible after generation since the vellum is
not dimensionally stable over time. Delays in doing the check might result in
a slight shift in one or both dimensions of the verification plot sheet.  Any
shift will manifest itself as data error-- and it is error which is not
actually there! Course of action could force us to do unnecessary repair/
replacement work.

Step 9.   Clean up your mess.

--in the event that rework or replacement is found necessary, a new
verification plot will be required to check the updated/corrected work.  Thus,
if reworking of the data in any capacity is going to be required, save the
projected registration point file you created during initial plot processing.
This will reduce redundancy during reverification.

--if the verification is successful, remove (delete) files and covers you
generated from the over plot/verification operations which are longer needed.
Power down the plotter and return it, if you moved it in the first place, to
its storage location, and file away the verification plot hard copy.

CHAPTER EIGHT: FINAL ARCHIVE AND DISTRIBUTION

The shoreline data is to be distributed on Compact Disc in two ASCII
formats.  Conversion of the source data will involve operations to convert
from native ArcInfo Geodata Sets to each respective format.

To ASCII Format One:
Use the ArcInfo UNGENERATE Command with the Line Option.

To ASCII Format Two:
Use Strategic Mapping Inc.  ArcAtlas Importer/Exporter Utility to generate
Boundary Named ASCII Files (BNA.)

Following successful conversion of the shoreline data into the three
distribution formats, the information will be transferred to the National
Geophysical Data Center in Boulder, CO where a master CD will be created.
We will review the master product, checking it for errors, omissions, and any
other flaws.  Once approved, the master will sent for reproduction.



---------------------------------------------------------------------------

Spatial_Data_Organization_Information

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information
    SDTS_Terms_Description
        SDTS_Point_and_Vector_Object_Type: Point
        Point_and_Vector_Object_Count: 0
        SDTS_Point_and_Vector_Object_Type: String
        Point_and_Vector_Object_Count: 1865
        SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains'
        Point_and_Vector_Object_Count:  0

---------------------------------------------------------------------------

Spatial_Reference_Information

Horizontal_Coordinate_System_Definition
    Planar
        Map_Projection:
        Map_Projection_Name:  ALBERS
        Longitude_of_Central_Meridian: -83.5
        Latitude_of_Projection_Origin: 23
        Latitude_of_First_Standard_Parallel: 29.5
        Latitude_of_Second_Standard_Parallel: 45.5
        False_Easting:  0.00000
        False_Northing:  0.00000
    Geodetic Model
        Horizontal_Datum_Name: North American Datum of 1983
        Ellipsoid_Name:  GRS 80
        Semi-major_Axis: 6,378,206.4
        Denominator_of_Flattening: 294.98

---------------------------------------------------------------------------

Entity_and_Attribute_Information

Detailed_Description
    Entity_Type
    Entity_Type_Label: SHORE.AAT
    Entity_Type_Definition: ARC/INFO Arc Attribute Table
    Entity_Type_Definition_Source: NOAA, NOS
    Attribute:
        Attribute_Label: -
        Attribute_Definition: ARC/INFO Arc Attribute Table
        Attribute_Definition_Source: NOAA, NOS
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: -
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: FNODE#
        Attribute_Definition: Internal number of from-node
        Attribute_Definition_Source: Computed
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: Sequential unique positive integer
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: TNODE#
        Attribute_Definition: Internal number of to-node
        Attribute_Definition_Source: Computed
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: Sequential unique positive integer
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: LPOLY#
        Attribute_Definition: Internal number of poly to left of arc
        Attribute_Definition_Source: Computed
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: Sequential unique positive integer
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: RPOLY#
        Attribute_Definition: Internal number of poly to right of arc
        Attribute_Definition_Source: Computed
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: Sequential unique positive integer
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: LENGTH
        Attribute_Definition: Length of arc in coverage units
        Attribute_Definition_Source: Computed
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: Positive real numbers
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: SHORE#
        Attribute_Definition: Internal feature number
        Attribute_Definition_Source: Computed
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: Sequential unique positive integer
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: SHORE-ID
        Attribute_Definition: User-assigned feature number
        Attribute_Definition_Source: User-defined
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: Integer
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: ID
        Attribute_Definition: Temporary Variable Corresponds to Individual Section IDs
        Attribute_Definition_Source: n/a
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 1-9999
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: F-NODE
        Attribute_Definition: Arcs starting, or from, node.
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: All positive integers from 1 to number of arcs in section, discrete
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: T-NODE
        Attribute_Definition: Arcs ending, or to, node.
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: All positive integers from 1 to number of arcs in section.
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: LEN
        Attribute_Definition: Length of original arc, in geographic units (decimal degrees)
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: All positive real numbers
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: L-SIDE
        Attribute_Definition: Environment on left side of shoreline arc
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 1=water 2=land
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: R-SIDE
        Attribute_Definition: Environment on right side of shoreline arc
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 1=water 2=land
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: SOURCE-SCALE
        Attribute_Definition: map scale of the source chart from which the arcs were captured
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 10000-600000 discrete
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: NOS-NO
        Attribute_Definition: NOS chart catalog number for chart which the arcs were captured
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 11301-18800 discrete
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: DATUM-SOURCE
        Attribute_Definition: Source chart horizontal reference datum
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: set of valid horizontal datums used by NOS (02
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: REV-DATE
        Attribute_Definition: 'Source chart''s date of revision'
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: any valid date string (mm/yy) 1/87 through 12/92
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: SOURCE-MEDIA
        Attribute_Definition: Identifies method used to capture source data
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 1=Arc/Info-Arc/Edit 2=Hitachi CADCore 3=Digitizing Table 4=Estimation 5=Florida
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: ARC-CODE
        Attribute_Definition: Coding identifying arc type
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 1=shoreline from capture 3=shoreline truncation 5=shoreline estimation
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:
    Attribute:
        Attribute_Label: INTEGRITY
        Attribute_Definition: Qualitative assessment of arcs accuracy based on source media
        Attribute_Definition_Source:
        Attribute_Domain_Values
            Enumerated_Domain
                Enumerated_Domain_Value: 1=master mylar 2=light mylar 3=water resist paper 4=Florida 5=estimate 6=unknown
                Enumerated_Domain_Value_Definition
                Enumerated_Domain_Value_Definition_Source:

 Overview_Description
    Entity_and_Attribute_Overview

    DATA ATTRIBUTES TOPOLOGICAL ASSOCIATIONS

    Spatial topology support:  Arc.

    Descriptive topological Associations: Arc.

    Attribute items and their domains (encoding key):

    Attribute:  FNODE#
    Description: Arcs starting, or from, node.
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain:  All positive integers from 1 to number of arcs in section.

    Attribute:  TNODE#
    Description: Arcs ending, or to, node.
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain:  All positive integers from 1 to number of arcs in section.

    Attribute:  LPOLY#
    Description: Id number of polygon on left side of arc.
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain:  All positive integers from 0 to number of polys in section.

    Attribute:  RPOLY#
    Description: Id number of polygon on right side of arc.
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain:  All positive integers from 0 to number of polys in section.

    Attribute:  LENGTH
    Description: Physical length of arc, in cover units.
    Data type: floating point
    Data size: 4 bytes (F12.3)
    Encoded in attribute table listing? no
    Domain type: continuous
    Domain:  All positive real numbers.

    Attribute:  COVER#
    Description: Id number of arc-- Arc/Info artifact.
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain:  All positive integers from 1 to number of arcs in section.

    Attribute: ID
    Description: arc identification number -unique.
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain: The set of all positive integers.

    Attribute:  L_SIDE
    Description: Environment on left side of shoreline arc (see note)
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? yes
    Domain type: discrete
    Domain: 1 = Water--   2 = Land.

    Attribute:  R_SIDE
    Description: Environment on right side of shoreline arc (see note)
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? yes
    Domain type: discrete
    Domain: 1 = Water--   2 = Land.

    A brief explanation of the rational behind the left and right side
    topologies. By definition, a coastline or shoreline demarcates the
    horizontal position of land-sea interface at a given point in time.
    On a map this feature is depict simply as a line with water on one
    side and land on the other (the exception to this definition is the
    truncation arc, defined below).  If we can ascertain and we can,  the
    left and right sides of the arcs which comprise the shoreline we can
    then assign the appropriate type, either land or water, to its left and
    right sides in the form of associated descriptive attributes.

    Attribute: S_SCALE
    Description: map scale of the source chart from
    which arcs were captured
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain: 10000 - 600000

    Attribute: S_CHART
    Description: NOS chart catalog no. for chart from which arcs were
    captured
    Data type: character
    Data size: 7 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain: 11301 - 18800.

    Attribute:  S_DATUM
    Description: Source chart horizontal reference datum
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? no
    Domain type:discrete
    Domain: set of valid horizontal datums used by NOS   (02 27 83)

    Attribute:  REV_DATE
    Description: Source charts date of revision
    Data type: character
    Data size: 5 bytes
    Encoded in attribute table listing? no
    Domain type: discrete
    Domain: any valid date string (mm/yy), 1/87 through 12/92.

    Attribute:  SOURCE
    Description: identifies method used to capture source data.
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? yes
    Domain type: discrete
    Domain: 1 = Arc/Info-ArcEdit Heads Up
    2 = Hitachi CADCore Heads Up
    3 = Digitizing Table
    4 = Estimation or truncation arc added post capture(see note)
    5 = Data obtained from the State of Florida

    Attribute:  ARC_CODE
    Description: Coding identifying the arc type
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? yes
    Domain type: discrete
    Domain: 1 = shoreline data arc from capture process
    3 = shoreline truncation arc -post capture addition(see note)
    5 = shoreline estimation arc -post capture
    modification/addition (see note below)

    Truncation arcs are arcs inserted into the data to provide continuity/closure
    in places where the cartographic information on the chart was incomplete.
    Often, small water bodies (rivers, streams, and creeks), in locations beyond
    the point of navigability are terminated to facilitate the insertion of non-
    cartographic information such as title blocks and notations.  Continuity of
    the data, a requirement our data set specification, is interrupted at these
    location if they are captured and retained as depicted on the navigation
    chart.  To reestablish the necessary topological continuity an artificial
    closure arc is placed across the truncated section of shoreline.  These arcs
    make no attempt to simulate the position of the missing shoreline section(s),
    but rather simply terminate the feature.  To easily identify these arc
    features in the data field they are given the attribute codes: SOURCE = 4
    and ARC_CODE = 3.

    Estimation arcs are used for two purposes: first, to fill in gaps in the
    shorelinew as depicted on the chart (other than those areas which would be
    considered truncations), and secondly, to identify captured (digitized)
    shoreline arcs which have been modified in some way either for error
    rectification or edge matching adjustments.   The span of these arcs range
    from five meters to several tens of meters in length.  In the first case,
    estimator arcs attempt to simulate or mimic the actual shape or course of
    the coastline in the missing area.  Insertion of these arcs into the data is
    done using heads up methods with the appropriate navigational chart(s) as a
    guide.  In the second case, an existing arcs terminal to node is moved from
    its original captured location to a position where it can be connected to the
    concomitant arcs node from an adjacent chart.  Additional vertices may then
    be added to replicate the course of the original information.  Modification
    of existing arcs was carried out such that disruption of the information was
    minimized.  Estimate arcs are identified in the data by the codes:
    SOURCE = 4, ARC_CODE = 5.

    Attribute: INTEGRITY
    Description: qualitative assessment of arcs accuracy based on source
    media
    Data type: integer
    Data size: 2 bytes
    Encoded in attribute table listing? yes
    Domain type: discrete
    Domain: 1 = master compilation -heavy gauge mylar (0.007 in).
    2 = X-drawing, reproduction of master on lighter
    grade(0.003) mylar.
    3 = Water resistant paper.
    4 = Data sourced from the State of Florida.
    5 = Estimate or truncation arc.
    6 = Unknown.

    If the accuracy of the data could not be assessed and thus categorized into
    one of the five qualitative integrity classes, the arc was classified with an
    integrity of unknown.  Most of the arcs grouped into the unknown category
    were those captured early in the project.  During that time source materials
    (primarily master compilations and X-drawings) were assumed to be of equal
    stability and accuracy.  This was not, however, the case. Once this disparity
    was recognized, source tracking procedures were implemented and the
    integrity of the captured information, based on the stability and clarity of
    the source media was tracked and assessed.


    Entity_and_Attribute_Detail_Citation: Not Available

---------------------------------------------------------------------------

Distribution_Information

Distributor
    Contact_Person_Primary
        Contact_Person: Jonathan W. Musser
        Contact_Organization: U.S. Geological Survey
    Contact_Position: Hydrologist

    Contact_Address
        Address_Type: mailing address
        Address: U.S. Geological Survey
                 3039 Amwiler Road
                 Suite 130
        City: Atlanta
        State_or_Province: GA
        Postal_Code: 30360-2824
        Country: USA

    Contact_Facsimile_Telephone: 770-903-9199
    Contact_Electronic_Mail_Address: jwmusser@usgs.gov


Standard_Order_Process
    Digital_Form
        Digital_Transfer_Information
        Format_Name: ARCE ARC/INFO Export format
        File_Decompression_Technique: gzip

        Format_Name: SDTS Spatial Data Transfer Standards (FIPS 173)
        File_Decompression_Technique: gzip & tar
        Digital_Transfer_Option
        Online_Option
        Computer_Contact_Information
        Network_Address
        Network_Resource_Name: http://csat.er.usgs.gov/statewide/layers/shore.html



---------------------------------------------------------------------------

Metadata_Reference_Section

Metadata_Date: 19980109
Metadata_Contact: nybunek
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version:  19940608
Metadata_Time_Convention:  Local Time
Metadata_Security_Information:
    Metadata_Security_Classification_System:  None
    Metadata_Security_Classification:  UNCLASSIFIED
    Metadata_Security_Handling_Description:  None

---------------------------------------------------------------------------
Last modified: 2008-03-20