National Petroleum Reserve Alaska - Administrative Coastal Boundary Points (NAD83)

Metadata also available as

Frequently anticipated questions:


What does this data set describe?

Title:
National Petroleum Reserve Alaska - Administrative Coastal Boundary Points (NAD83)
Abstract:
The NPRA Administrative Coastal Boundary Points dataset is a continuous, point to point listing of all angle points for the Final Administrative Lease Line of the National Petroleum Reserve - Alaska (administrative lease line). The listing runs from east to west.
All Public Land Survey System references are for the Umiat Meridian, Alaska.
N.P.R.A. refers to National Petroleum Reserve - Alaska.
No angle points for the administrative lease line of the N.P.R.A. fall in the interior of T. 17 N., R. 26 W., and T. 22 N., R. 18 W.
All latitudes and longitudes are on the North American Datum 1927.
The ASCII character ` (hex 60) represents the degree symbol.
Supplemental_Information:
The source information for the latitudes, longitudes, and comments comes from the manuscript entitled, "FedReg NPRA text bndy continuous with ASCII symbol.doc"
This manuscript was produced on 30 MAY, 2003.
  1. How should this data set be cited?

    Bureau of Land Managment Alaska State Office, 20071102, National Petroleum Reserve Alaska - Administrative Coastal Boundary Points (NAD83).

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -161.867545
    East_Bounding_Coordinate: -151.118045
    North_Bounding_Coordinate: 71.383995
    South_Bounding_Coordinate: 70.283946

  3. What does it look like?

    \\ilmakso0db10\metadata\documents\images\admin_coastal_points.png (PNG)
    Image showing four points from the NPRA Adminstrative Coastal Point layer.

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

    Calendar_Date: 24-Oct-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):

      • Entity point (8011)

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

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

  7. How does the data set describe geographic features?

    npra_admin_coastal_points
    National Petroleum Reserve Alaska Administrative Coastal Latitude and Longitude Pairs (Source: Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line).)

    objectid
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    corner_number
    Corner Number (Source: Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line))

    Range of values
    Minimum:1
    Maximum:8011

    dms_latitude
    Degrees, Minutes, and Seconds of Latitude (Source: Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line))

    Range of values
    Minimum:Lat. 71`23'23.83509" N.
    Maximum:Lat. 71`23'23.83509" N.

    dms_longitude
    Degrees, Minutes, and Seconds of Longitude (Source: Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line).)

    Range of values
    Minimum:Long. 151`07'49.61180" W.
    Maximum:Long. 151`07'49.61180" W.

    comment
    Descriptive text that defines the origin of the Latitude and Longitude pair. (Source: Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line).)

    Varies with the point. There are 159 distinct comments for 8011 points.

    dd_latitude
    Decimal Degree Latitude (Source: Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line).)

    Range of values
    Minimum:70.289454741666660
    Maximum:71.389954191666680

    dd_longitude
    Decimal Degree Longitude (Source: Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line).)

    Range of values
    Minimum:-161.875450000000000
    Maximum:-151.130447722222240

    shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.


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?

    Frank Hardt
    Bureau of Land Management
    Land Surveyor
    222 W. 7th Ave. #13
    Anchorage, AK 99513
    USA

    (907) 271-3182 (voice)
    Frank_Hardt@ak.blm.gov

    Hours_of_Service: 8am - 4:30pm


Why was the data set created?

This dataset was created as a spatial representation of the angle points the NPRA Final Administrative Lease Line and points of intersection with the Public Land Survey System and the NPRA Final Administrative Lease Line.


How was the data set created?

  1. From what previous works were the data drawn?

    none (source 1 of 1)
    Bureau of Land Management, 20030530, FedReg NPRA txt bndy continuous with ASCII symbol.doc.

    Type_of_Source_Media: Microsoft Word Document
    Source_Contribution:
    Frank Hardt - BLM Cadastral Land Surveyor Federal Register Final Administrative Lease Line of the National Petroleum Reserve - Alaska (Administrative Lease Line).

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

    Date: 02-Nov-2007 (process 1 of 1)
    1. Save source document as ASCII text file. 2. Remove blank lines and extraneous text lines at beginning and end of file. 3. Use copy and paste to format text file as Lat, Long, Comment fields. 4. Used AWK script to parse source manuscript text file: #!/bin/ksh # Tim Varner 20071022 # parse_npra.txt # Based on an input file of dms coordinates below: #Lat. 70`22'30.10583" N.|Long. 151`07'49.61180" W.|Beginning at the most southwesterly point of the N.P.R.A. in sec. 21 shown on the plat of T. 12 N., R. 4 E., accepted May 31, 1994 #Lat. 70`22'27.99466" N.|Long. 151`07'54.91558" W.|Angle points along a portion of the administrative coastal bdy. of the N.P.R.A. in surveyed T. 12 N., R. 4 E. # Put parse_npra.awk somewhere in your PATH # CAN BE OUTPUT TO A FILE... # AT THE COMMAND LINE TYPE: # gawk -f parse_npra.awk (file containing dms coordinates) > (new file of dd coords) # # CAN BE OUTPUT TO THE SCREEN... # AT THE COMMAND LINE TYPE: # gawk -f parse_npra.awk (file containing dms coordinates) { FS = "|" OFS = "|" dmslat = $1 dmslon = $2 comment = $3
    latdd = (substr($0,6,2)) latmm = (substr($0,9,2)/60) latss = (substr($0,12,8)/3600) lat = latdd + latmm + latss latdec = sprintf("%16.14f", lat)
    londd = (substr($0,31,3)) lonmm = (substr($0,35,2)/60) lonss = (substr($0,38,8)/3600) lon = londd + lonmm + lonss
    londir = (substr($0,48,1)) if (londir = "W") londec1 = (lon * (-1)) else londec1 = lon
    londec = sprintf("%17.14f", londec1)
    shp = "2 point ("londec " " latdec")"
    print NR, NR, dmslat, dmslon, comment, latdec, londec, shp "|"
    5. Once text file is parsed using parse_npra.awk script, resulting load file is used to load into new empty database table.
    CREATE TABLE npra_admin_coastal_points ( objectid INTEGER NOT NULL, corner_number INTEGER NOT NULL, dms_latitude VARCHAR(30), dms_longitude VARCHAR(30), comment VARCHAR(255), dd_latitude DECIMAL, dd_longitude DECIMAL, shape ST_Point )
    6. Load file was loaded into the database table, "npra_admin_coastal_points." 7. Comments were inserted into table to reflect table values for lines without comments. Comments were copied from last known comment for each row up to next not null comment. Database table was compared line by line to source manuscript.

    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

  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?

    Attributes are correct as agreed upon by the Bureau of Land Management and the Alaska Department of Natural Resources.

  2. How accurate are the geographic locations?

    Positions are abstracted to the nearest 5 decimal places in seconds. Example: Lat. 70`22'30.10583" N., Long. 151`07'49.61180" W.

  3. How accurate are the heights or depths?

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

    Point manuscript is complete as agreed upon.

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

    Point listings are complete as agreed upon by the Bureau of Land Management and the Alaska Department of Natural Resouces. Latitude and Longitudes were abstracted from known positions.


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: 02-Nov-2007
Last Reviewed: 02-Nov-2007
To be reviewed: 02-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:59 2017