onemap_prod.SDEADMIN.basdcm

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

Frequently-anticipated questions:


What does this data set describe?

Title: onemap_prod.SDEADMIN.basdcm
Abstract:
The Division of Coastal Management provides financial support to coastal communities who wish to provide public access to waterfront areas. This GIS data set provides point locations of such access sites in North Carolina. Attributes that can be taken from this layer include: the municipality or county responsible for the site (sponsor), the general size of the parking lot, the type of waterfront (urban, ocean, estuarine), the date the data were collected and the DCM contract number of the site.
Supplemental_Information:
system filename: basdcm     file size = 0.15 mb

Revisions and updates to this layer include:
3.) filename: basdcm1298  The December 1998 update to this layer
consisted of projecting the data from NAD27 datum, State Plane
projection, units of measure feet TO: NAD83 DATUM, State Plane
PROJECTION, UNITS OF MEASURE METERS.  This was done to comply with
the NC Geographic Information Coordinating Council's "Statement
of Direction for North Carolina Corporate Geographic Database
Horizontal Reference, Datum and Unit of Measure".  This reprojecting
was done in various ways depending on the data type and content.
Vector data was projected using the 'project' command in ESRI's Arc
software and topology was cleaned and built based on coverage needs.
Raster data was projected using ESRI's Grid module and various steps
as applicable.
2.)filename: basdcm598. Update included the addition of 3 beach
access sites to the datalayer, and the addition of 2 items to the
polygon attribute table, X-coord and Y-coord.
1.)filename: basdcm796  This is the first version of the data.
The 796 in the filename stands for the July 8, 1996 version.
  1. How should this data set be cited?

    NC DEHNR, Division of Coastal Management, 19981201, onemap_prod.SDEADMIN.basdcm: Department of Environment, Health and Natural Resources, Division of Coastal Management, Raleigh, North Carolina.

    Online Links:

    Other_Citation_Details: NCCGIA distributes this dataset

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -78.516209
    East_Bounding_Coordinate: -75.467644
    North_Bounding_Coordinate: 36.416349
    South_Bounding_Coordinate: 33.817559

  3. What does it look like?

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

    Calendar_Date: REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.
    Currentness_Reference: Data creation and release dates

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

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      Indirect_Spatial_Reference: _Method: County-name
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • Entity point (205)

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

      Grid_Coordinate_System_Name: State Plane Coordinate System 1983
      State_Plane_Coordinate_System:
      SPCS_Zone_Identifier: 3200
      Lambert_Conformal_Conic:
      Standard_Parallel: 34.333333
      Standard_Parallel: 36.166667
      Longitude_of_Central_Meridian: -79.000000
      Latitude_of_Projection_Origin: 33.750000
      False_Easting: 609601.220000
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000512
      Ordinates (y-coordinates) are specified to the nearest 0.000512
      Planar coordinates are specified in meters

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

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Resolution: 1.000000
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    onemap_prod.SDEADMIN.basdcm
    Point feature attribute table (Source: NC DEHNR - Division of Coastal Management)

    SHAPE
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    PERIMETER
    Total perimeter in coverage units (Source: Software computed)

    Frequency of measurement: None planned

    Range of values
    Minimum:0
    Maximum:0
    Units:meters
    Resolution:0.001

    PROJECT_LOCATION
    Location of beach access site (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    Access site locations vary in length and number of words

    LOCAL_SPONSOR
    Local government receiving DCM grant (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    Access site locations vary in length and number of words

    NEIGHBORHOOD
    site with 10-15 parking spaces (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoParking spaces do not exist
    Yes10 - 15 parking spaces do exist

    REGIONAL
    Site with more than 25 parking spaces (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoParking spaces do not exist
    YesMore than 25 parking spaces do exist

    LOCAL
    No parking available. Site is simply a dune crossover. (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoParking does not exist
    YesParking exists

    OCEAN
    Oceanfront access site. (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoOceanfront access does not exist
    YesOceanfront access exists

    URBAN_WATERFRONT
    Urban area access site. (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoUrban area access does not exist
    YesUrban area access exists

    ESTUARINE
    Sound side access site. (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoSound side access does not exist
    YesSound side access exists

    HANDICAP_ACCESS
    Does handicap access exist at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoSite is not handicap accessible
    YesSite is handicap accessible

    RESTROOMS
    Do restrooms exist at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoRestrooms are not available
    YesRestrooms are available

    SHOWERS
    Are showers available at site (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoShowers are not available
    YesShowers are available

    PARKING
    Is parking available at site (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoParking is not available
    YesParking is available

    SPACES
    Number of parking spaces available (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    Number of parking spaces varies according to site

    STREET_PARKING
    Is street parking available at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoStreet parking is not available
    YesStreet parking is available

    BULKHEAD
    Does bulkhead exist at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoBulkhead does not exist
    YesBulkhead does exist

    DUNE_CROSSOVER
    Is there a dune crossover at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoA dune crossover does not exist
    YesA dune crossover does exist

    BOARDWALK
    Is there a boardwalk at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoA boardwalk does not exist
    YesA boardwalk does exist

    PICNIC_TABLES
    Do picnic tables exist at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoPicnic tables do not exist
    YesPicnic tables do exist

    LENGTH
    Length of pier (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    Lengths vary according to site

    Range of values
    Minimum:0
    Maximum:999
    Units:Feet
    Resolution:1

    COMMENTS
    Access site comments (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    Comments vary according to site

    CONTRACT_NUMBER
    DCM contract number (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    Contract numbers vary according to site

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    GAZEBO
    Is there a gazebo at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoA gazebo does not exist
    YesA gazebo does exist

    PIER
    Does a pier exist at site? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoA pier does not exist
    YesA pier does exist

    BASDCM_

    NATURE_TRAIL
    Does a nature trail exist? (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    ValueDefinition
    NoA nature trail does not exist
    YesA nature trail does exist

    BASDCM_ID

    DATE
    Date of data collection (Source: Division of Coastal Management)

    Frequency of measurement: None planned

    Dates vary according to site

    CO_

    CO_NAME

    CO_ABBR

    X_COORD

    Y_COORD

    POLYGONID

    SCALE

    ANGLE

    onemap_prod.SDEADMIN.basdcm.AREA

    Entity_and_Attribute_Overview:
    A point coverage depicting the location of beach access sites along the North Carolina coast. The table consists of both internal software items (area, perimeter, cov#, cov-id) and user added IDs (all the rest).
    BASDCM.PAT  Point Attribute Table
    COLUMN  ITEM NAME             WIDTH OUTPUT TYPE   N.DEC DESCRIPTION
    1   AREA                   4    12     F      3     Total area in meters
    5   PERIMETER              4    12     F      3     Total perimeter in meters
    9   BASDCM#                4     5     B      -     Internal id number
    13  BASDCM-ID              4     5     B      -     User id number
    17  PROJECT_LOCATION      40    40     C      -     Location of access site
    57  LOCAL_SPONSOR         25    25     C      -     Local government receiving DCM grant
    82  NEIGHBORHOOD          20    20     C      -     Site with 10-15 parking spaces
    102 REGIONAL              20    20     C      -     Site with >25 parking spaces
    122 LOCAL                 20    20     C      -     Parking availability
    142 OCEAN                 20    20     C      -     Oceanfront access site
    162 URBAN_WATERFRONT      20    20     C      -     Urban area access site
    182 ESTUARINE             20    20     C      -     Sound side access site
    202 HANDICAP_ACCESS       20    20     C      -     Status of handicap access
    222 RESTROOMS             20    20     C      -     Status of restrooms
    242 SHOWERS               20    20     C      -     Status of showers
    262 PARKING               20    20     C      -     Status of vehicle parking
    282 SPACES                 4     4     I      -     Number of parking spaces
    286 STREET_PARKING        20    20     C      -     Status of street parking
    306 BULKHEAD              20    20     C      -     Status of bulkhead
    326 DUNE_CROSSOVER        20    20     C      -     Status of dune crossover
    346 BOARDWALK             20    20     C      -     Status of boardwalk
    366 GAZEBO                20    20     C      -     Status of gazebo
    386 PICNIC_TABLES         20    20     C      -     Status of picnic tables
    406 PIER                  20    20     C      -     Status of pier
    426 LENGTH                 4     4     I      -     Length of pier
    430 NATURE_TRAIL          20    20     C      -     Status of nature trail
    450 COMMENTS             100   100     C      -     Site comments
    550 DATE                  20    20     C      -     Date of data collection
    570 CONTRACT_NUMBER       10    10     C      -     DCM contract number
    580 CO#                    4     7     B      -     County number
    584 CO-NAME               15    15     C      -     County in which site resides
    599 CO-ABBR                4     4     C      -     Abbreviation of county in which site resides
    603  X-COORD               4    12     F      3     X coordinate
    607  Y-COORD               4    12     F      3     Y coordinate
    
    Entity_and_Attribute_Detail_Citation: None


Who produced the data set?

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

  2. Who also contributed to the data set?

    Department of Environment, Health and Natural Resources
    Division of Coastal Management
    2728 Capital Blvd.
    Raleigh, NC 27609
    
    NCCGIA Director, Karen Siderelis
    Database Administration, Zsolt Nagy
    Database Management, Ken Shaffer
    Project Manager, David Giordano
    Governor's Office
    Office of State Planning
    North Carolina Center for Geographic Information and Analysis
    301 North Wilmington Street, Suite 700
    Raleigh, NC 27601-2828
    

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

    Chris Bruce
    NC DEHNR, Division of Coastal Management
    P.O. Box 27687
    Raleigh, North Carolina 27611-7687
    U.S.A.

    (919) 733-2293 (voice)
    (919) 733-1495 (FAX)

    Hours_of_Service: 8am to 5pm, M-F
    Contact_Instructions: Preferred contact is by phone.


Why was the data set created?

This data was created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System (GIS).


How was the data set created?

  1. From what previous works were the data drawn?

    None (source 1 of 2)
    NC DEHNR, Division of Coastal Management, 199512, GPS data: NC DEHNR, Division of Coastal Management, Raleigh, North Carolina.

    Type_of_Source_Media: computer program
    Source_Contribution: Beach Access Sites location GIS export file with attributes.

    None (source 2 of 2)
    NC Center for Geographic Information and Analysis, 19980508, Beach Access Sites - Division of Coastal Management: NC DEHNR, Division of Coastal Management, Raleigh, North Carolina.

    Other_Citation_Details: NCCGIA distributes this data
    Type_of_Source_Media: disc
    Source_Contribution:
    The supplied Arc/Info export file was imported and is managed as part of the North Carolina Corporate Geographic Database.

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

    Date: Dec-1995 (process 1 of 4)
    Beach Access Sites were collected on a Trimble GPS Datalogger. The data were downloaded to a UNIX Sun SPARC Station using Arc/Info GIS software. The data were then converted into an Arc/Info coverage, and projected to the Stateplane Coordinate System. Only 3-D points were accepted (4 satellites) while standing at the seaward end of the crossover to collect the point. An Arc Macro Language (AML) program was used to input attribute information. The completed coverage was then exported and sent to CGIA for inclusion in the NC Corporate Geographic Database.

    Person who carried out this activity:

    Chris Bruce
    NC DEHNR, Division of Coastal Management
    P.O. Box 27687
    Raleigh, North Carolina 27611-7687
    U.S.A.

    (919) 733-2293 (voice)
    (919) 733-1495 (FAX)

    Hours_of_Service: 8:30AM - 5:30PM
    Contact_Instructions: Phone and electronic mail preferred
    Date: 08-May-1998 (process 2 of 4)
    The supplied export file was imported into ESRI's Arc/Info, GIS software, version 7.0.3. The file was checked for completeness and the metadata created.

    Person who carried out this activity:

    David Giordano
    NCCGIA
    GIS Analyst
    301 North Wilmington Street, Suite 700
    Raleigh, North Carolina 27601-2828
    U.S.A.

    (919) 733-2090 (voice)
    (919)715-0725 (FAX)
    dataq@cgia.state.nc.us

    Hours_of_Service: 8:30AM - 5:30PM
    Contact_Instructions: Phone and electronic mail preferred
    (process 3 of 4)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\david\LOCALS~1\Temp\xml7.tmp

    (process 4 of 4)
    Dataset copied.

    Data sources used in this process:

    • Server=cgiatdb; Service=5151; Database=onemap_test; User=sdeadmin; Version=sde.DEFAULT

  3. What similar or related data should the user be aware of?


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

  1. How well have the observations been checked?

    Attribute information was input onsite from observations made by field personnel and backed by information previously gathered and stored in the project files. An AML program was used to check for consistency.

  2. How accurate are the geographic locations?

    Reviewed differential correction results. Only 0/0/0/0 corrections accepted (meaning all locations were corrected for SA and all data were acceptable). Ground positional accuracy is 2-5 meters. Data were collected using a Trimble Pro-Lite GPS receiver, accepting no less that 180 uncorrected locations per site. Locations are accepted at one second intervals from the satellites. The locations were differentially corrected using data from the closest base station on PFINDER software. The corrected points were then GENERATED into an Arc/INFO point coverage.

  3. How accurate are the heights or depths?

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

    Only located beach access sites funded by DCM grants. Other access sites exist, and some of these are marked with DCM access site signage.

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

    The data was built for points, using ARC/INFO's "build" command, to ensure topological consistency. There have been no edits since the last build or clean was performed.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:
Acknowledgement of products derived form this data set should cite the following: The source of the Beach Access Sites - Division of Coastal Management data is the North Carolina Corporate Geographic Database. Earlier versions of this data set may exist. The user must be sure to use the appropriate data set for the time period of interest. While efforts have been made to ensure that these data are accurate and reliable within the state of the art, CGIA cannot assume liability for any damages or misrepresentation caused by any inaccuracies in the data or as a result of changes to the data caused by system transfers.

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

    NC Center for Geographic Information and Analysis
    Production Services
    301 North Wilmington Street, Suite 700
    Raleigh, North Carolina 27601-2825
    USA

    (919) 733-2090 (voice)
    (919) 715-0725 (FAX)
    dataq@cgia.state.nc.us

    Hours_of_Service: 8:30AM - 5:30PM
    Contact_Instructions:
    Phone and electronic mail preferred For current COST INFORMATION, use a web browser: <http://www.cgia.state.nc.us/cost.html>
  2. What's the catalog number I need to order this data set?

    Beach Access Sites - Division of Coastal Management

  3. What legal disclaimers am I supposed to read?

    NCCGIA is charged with the development and maintenance of the State's corporate geographic database and, in cooperation with other mapping organizations, is committed to offering its users accurate, useful, and current information about the state. Although every effort has been made to ensure the accuracy of information, errors and conditions originating from physical sources used to develop the corporate database may be reflected in the data supplied. The client must be aware of data conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to certain data. NCCGIA does not support secondary distribution of this data. The use of trade names or commercial products does not constitute their endorsement by the NCCGIA or North Carolina State Government.

  4. How can I download or order the data?

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

    Data creation and large data analysis jobs contact Database Administration P:(919)733-2090. All data is available through standard ordering procedures on a cost recovery basis.

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

    All formats supplied are created using ARC/INFO GIS software on Unix workstations. Other formats are available. Format compatibility is the user's responsibility. For current FORMAT/MEDIA INFORMATION, use a web browser: <http://www.cgia.state.nc.us/cost.html>


Who wrote the metadata?

Dates:
Last modified: 02-Oct-2006
Metadata author:
North Carolina Center for Geographic Information and Analysis
c/o REQUIRED: The person responsible for the metadata information.
Database Management
301 North Wilmington Street, Suite 700
Raleigh, North Carolina 27601-2828
USA

(919) 733-2090 (voice)
(919) 715-0725 (FAX)
dataq@cgia.state.nc.us

Hours_of_Service: 8:30AM - 5:30PM
Contact_Instructions: Phone and electronic mail preferred
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.9.5 on Wed Aug 27 10:29:09 2008