National Petroleum Reserve Alaska Boundary (Arcs) NAD83

Metadata also available as

Frequently anticipated questions:


What does this data set describe?

Title: National Petroleum Reserve Alaska Boundary (Arcs) NAD83
Abstract:
The NPRA Boundary (arcs) are a composite of 5 sets of arcs. Each arc is attributed with the data source of the arc.
Supplemental_Information:
1. Spatial Data Management System bearings and distances for NPRA - 1876 arcs
2. High, High Water Line within USS 9571 - one arc
3. Connecting Line Between MC2, T11N, R39W and the point of intersection of the administrative lease line of the N.P.R.A. and the surveyed W. bdy. of the N.P.R.A. - one arc
4. Southern boundary of the N.P.R.A. from a point in unsurveyed township Sec19, T31N, R13E, KRM northeasterly along the Continental Divide to Closing Corner 1, T11S, R43W, UM - one arc
5. Final Administrative Lease Line of the National Petroleum Reserve - Alaska (administrative lease line) - one arc made up of 8011 points of Latitude and Longitude
  1. How should this data set be cited?

    bureau of Land Management, 20071028, National Petroleum Reserve Alaska Boundary (Arcs) NAD83.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -161.878861
    East_Bounding_Coordinate: -150.913388
    North_Bounding_Coordinate: 71.389543
    South_Bounding_Coordinate: 68.067262

  3. What does it look like?

    \\ilmakso0db10\metadata\documents\images\npra_boundary_arcs.png (PNG)
    Composite Arcs of the NPRA Boundary

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

    Calendar_Date: 06-Nov-2007
    Currentness_Reference: publication date

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

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

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

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • String (1882)

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

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

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

  7. How does the data set describe geographic features?

    npra_boundary_arcs_gcsnad83
    Arcs that describe the exterior boundary of the NPRA (Source: BLM)

    line_id
    Line ID is the primary key which uniquely identifies each record or occurence in the Line entity. Each record in the Line entity has a unique Line Id. For Arcs from SDMS only. (Source: SDMS)

    Varies

    modified_user_id
    The system User ID of the person who modified the original data for this record. For Arcs from SDMS only. (Source: SDMS)

    Varies

    bcor_id
    Beginning Corner Id is a system field which identifies the Corner that forms the beginning point for the Boundary, Line or Circular Curve. For Arcs from SDMS only. (Source: SDMS)

    Varies

    ecor_id
    End Corner Id is a system field which identifies the Corner that forms the ending point for the Boundary, Line or Circular Curve. For Arcs from SDMS only. (Source: SDMS)

    Varies

    bound_typ_cd
    Boundary Type Code identifies the type of boundary, such as, straight line(s), circular curve(s), or other type of curve(s), or, a document listing individual courses. For Arcs from SDMS only. (Source: SDMS)

    Varies

    line_course_txt
    Line Course Text is a narrative description of a line's measurement. Typically, it is a concatenation of the bearing and distance. This is the display or label field when a line is spatially depicted. This portrays the originator's recordation of a meaurement and represents that organization's record format. For Arcs from SDMS only. (Source: SDMS)

    Varies

    modified_date
    Date Modified is a system field to record the date that an existing record was last modified. For Arcs from SDMS only. (Source: SDMS)

    Varies

    shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    entered_date
    The system date that the original data was entered for this record. For Arcs from SDMS only. (Source: SDMS)

    Varies

    objectid
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    meas_source_id
    Source ID is the system-generated primary key for a Source. Source ID may be used as a reference to record the basis of a survey meaurement or legal description. It implies the authority under which a measurement or legal description was defined. For SDMS arcs only. (Source: SDMS)

    Varies

    user_id
    The system User ID, identifying the person who entered the original data for a record. (Source: SDMS)

    Varies

    line_cmnts_txt
    Line Comments is a document which describes any decisions made in the collection process or in the interpretation of documents. Decisions may include a decision to override information on a survey plat because more recent information is available, or, recording an error on a survey plat found during the collection process. For SDMS arcs only. (Source: SDMS)

    Varies

    line_meas_type_cd
    Line Measurement Type indicates if the line is recorded as a line of true-mean-bearing, or a line of sight. For SDMS arcs only. (Source: SDMS)

    Varies

    source
    Text field that refers to the source of the arc. (Source: BLM Alaska)

    ValueDefinition
    Spatial Data Management SystemArcs from Spatial Data Management System
    NPRA Administrative Lease LineLines from NPRA Administrative Lease Line
    Continental Divide along the Brooks Range; Original bndy_16 layerContinental Divide along the Brooks Range; Original bndy_16 layer
    High, High Water Line of the NPRA W/I USS 9571Original bndy_16 layer W/I USS 9571
    Connecting Line between MC1, LOT2, USS 11974; MC2, T11N, R29W, UM and the point of intersection of the administrative coastal bdy. of the N.P.R.A. and the surveyed W. bdy. of the N.P.R.A.Line snapped from MC1, LOT2, USS 11974; MC2, T11N, R29W, UM and the point of intersection of the administrative coastal bdy. of the N.P.R.A. and the surveyed W. bdy. of the N.P.R.A.


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?

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

    Tim Varner
    Bureau of Land Management
    IT Specialist
    222 W 7th Ave #13
    Anchorage, AK 99513
    USA

    (907) 271-5799 (voice)
    tvarner@blm.gov


Why was the data set created?

Arcs used to create the NPRA (polygon) Boundary.


How was the data set created?

  1. From what previous works were the data drawn?

    none (source 1 of 3)
    Bureau of Land Management, 20071024, National Petroleum Reserve Alaska - Administrative Coastal Boundary Points.

    Type_of_Source_Media: ArcSDE Arc Feature Class - digital data
    Source_Contribution: Bureau of Land Management

    none (source 2 of 3)
    Bureau of Land Management, 20071101, Spatial Data Management System Line Layer, Surveyed Lines, Alaska.

    Type_of_Source_Media: ArcSDE Arc Feature Class - digital data
    Source_Contribution: Bureau of Land Management

    none (source 3 of 3)
    Bureau of Land Management, Unknown, bndry_16.

    Online Links:

    • none

    Type_of_Source_Media: ArcInfo Coverage - Arc Feature Class - digital data
    Source_Contribution: Bureau of Land Management

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

    Date: 25-Oct-2007 (process 1 of 2)
    Arcs were copied from 5 source data layers.
    Arcs were created/copied from:
    1. High, High Water Line within USS 9571 a. One arc b. Created from rectangular survey plat
    2. Connecting Line Between MC2, T11N, R39W and the point of intersection of the administrative lease line of the N.P.R.A. and the surveyed W. bdy. of the N.P.R.A. a. One arc b. Created from snapping line along rectangular survey to points described above.
    3. Southern boundary of the N.P.R.A. from a point in unsurveyed township Sec19, T31N, R13E, KRM northeasterly along the Continental Divide to Closing Corner 1, T11S, R43W, UM a. One arc copied from original bndry_16 layer.
    4. Final Administrative Lease Line of the National Petroleum Reserve - Alaska (administrative lease line) a. One arc created from 8011 points b. Arc Copied from npra_admin_coastal_bndy
    5. Spatial Data Management System - 1876 arcs a. 1876 arcs copied from SDMS Surveyed boundaries

    Person who carried out this activity:

    Tim Varner
    Bureau of Land Management
    IT Specialist
    222 W 7th Ave #13
    Anchorage, AK 99513
    USA

    (907) 271-5799 (voice)
    tvarner@blm.gov

    Date: 06-Nov-2007 (process 2 of 2)
    Dataset transformed from GCS NAD27 to GCS NAD83 using NAD27_to_NAD83_NADCON_For_Alaska

    Person who carried out this activity:

    Tim Varner
    Bureau of Land Management
    IT Specialist
    222 W 7th Ave #13
    Anchorage, AK 99513
    USA

    (9070 271-5799 (voice)
    tvarner@blm.bov

  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?

    A Source attribute was assigned depending on record source of the data. Line attributes only for data abstracted from SDMS line data.

  2. How accurate are the geographic locations?

    Line topology exists

  3. How accurate are the heights or depths?

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

    Complete - no omissions.

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

    Arctopology exists


How can someone get a copy of the data set?

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

Access_Constraints:
Discretionary, contains no sensitive information - generally considered releasable.
Use_Constraints:
Any hardcopies or published datasets using this data shall clearly indicate their source.
Any users wishing to modify this data are obligated to report the extent of their modifications. User specifically agrees not to misrepresent modifications to this data, as approved or endorsed by the BLM.

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

    Tim Varner
    Bureau of Land Management
    IT Specialist
    222 W 7th Ave #13
    Anchorage, AK 99513
    USA

    (907) 271-5799 (voice)
    tvarner@blm.gov

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    No warranty is made by the Bureau of Land Management as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 06-Nov-2007
Last Reviewed: 06-Nov-2007
To be reviewed: 06-Nov-2008
Metadata author:
Bureau of Land Management
Attn: Tim Varner
IT Specialist
222 W 7th Ave #13
Anchorage, AK 99513
USA

(907) 271-5799 (voice)
tvarner@blm.gov

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


Generated by mp version 2.9.12 on Thu Sep 28 14:43:18 2017