Boise Basin Experimental Forest Boundary within Boise National Forest, Idaho

Boise Basin Experimental Forest Boundary within Boise National Forest, Idaho

Frequently-asked questions:

What does this data set describe?

Title:
Boise Basin Experimental Forest Boundary within Boise National Forest, Idaho

Abstract: 
This data set reflects the Boise Basin Experimental Forest boundary within Boise National Forest, Idaho. The Experimental Forest, encompassing 6,865 acres in the Idaho City, Idaho area, was established to make permanently available an area for silvicultural and other related research in the ponderosa pine type.  Timber cutting is limited to that necessary for research studies or to provide areas suitable for future research programs.  Research in the Experimental Forest began in 1933.

Supplemental information: 
Procedures_Used:
Arc: log bbexpf
End      End   Elapsed CPU     I/O
Date     Time  Minutes Seconds Blocks User Command
-------- ----- ------- ------- ------ ---- -------
04/03/98 11:03       0       0      0 shayes build bbsnef line
04/03/98 11:04       0       0      0 shayes rename bbsnef bbef_bnd
04/03/98 11:05       0       2      0 shayes clean bbef_bnd bbefbnd2
04/03/98 11:11       0       1      0 shayes projectdefine cover bbefbnd2
04/03/98 11:12       0       0      0 shayes projectdefine cover bbefbnd2
04/03/98 11:13       0       0      0 external bbefbnd2

Here is where I (DWall) started working on this coverage.  I got it through ftp from the Forestry Sciences Laboratory in Moscow, ID from a person named Steve Hayes, at 208 883-2331.  Steve said they got the digital file from someone on the Idaho City Ranger District, Boise National Forest.  This coverage also contained some of the RNAs or Research Natural Areas which I removed, because I had another layer with the Research Natural Areas.

04/03/98 14:39       1       1      0 dwall import cover bbefbnd2 bbefbnd2
04/03/98 17:32       0       0      0 dwall ARCEDIT BBEFBND2
04/03/98 17:35       0       0      0 dwall ARCEDIT BBEFBND2
04/03/98 17:36       0       1      0 dwall build BBEFBND2 poly
04/03/98 17:37       0       0      0 dwall idedit BBEFBND2 poly
04/06/98 10:59       0       0      0 dwall ARCEDIT BBEFBND2
04/06/98 11:38       0       1      0 dwall build BBEFBND2 poly
04/06/98 11:39       0       1      0 dwall idedit BBEFBND2 line
04/06/98 11:40       0       0      0 dwall idedit BBEFBND2 poly
04/06/98 11:46       0       1      0 dwall rename BBEFBND2 bbexpf
08/06/98 15:13       0       0      0 dwall ARCEDIT BBEXPF

  1. How should this data set be cited?

    Boise National Forest GIS Staff, Unknown, Boise Basin Experimental Forest Boundary within Boise National Forest, Idaho: Boise National Forest GIS Staff, Boise, ID, USA.

    Online links:
  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -115.86154284
    East: -115.72653114
    North: 43.87366987
    South: 43.75889033

  3. What does it look like?

    http://insideidaho.org/data/BNF/image/bbexpfor_bnf_bnf.gif (GIF)
    Simple image of the data set at full extent

    Thumbnail image:

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

    Calendar date: unknown
    Currentness reference: 
    Unknown

  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):
      • Point (3)
      • String (7)
      • GT-polygon composed of chains (4)
      • Point (224)

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

      The grid coordinate system used is Universal Transverse Mercator

      Universal Transverse Mercator
      UTM zone number: 11
      Transverse Mercator projection parameters:
      Scale factor at central meridian: 0.999600
      Longitude of central meridian: -117.000000
      Latitude of projection origin: 0.000000
      False easting: 500000.000000
      False northing: 0.000000

      Planar coordinates are encoded using Coordinate Pair.
      Abscissae (x-coordinates) are specified to the nearest 1.
      Ordinates (y-coordinates) are specified to the nearest 1.
      Planar coordinates are specified in meters.

      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.
      The flattening of the ellipsoid used is 1/294.9786982.

  7. How does the data set describe geographic features?

    BBEXPFOR.PAT
    Attribute table of BBEXPFOR.PAT (Source: ARC/INFO)

    -
    Attribute table of BBEXPFFOR_BNF_BNF.PAT (Source: ARC/INFO)

    Sequential unique whole numbers that are automatically generated.

    AREA
    Area of poly/region in square coverage units (Source: Computed)

    Coordinates defining the features.

    BBEXPFOR#
    Internal feature number (Source: Computed)

    Whole numbers that are automatically generated.

    BBEXPFOR-ID
    User-assigned feature number (Source: User-defined)

    Whole numbers that are automatically generated.

    NAME
    Alpha (Source: User-defined)

    Whole numbers that are automatically generated.

    PERIMETER
    Perimeter of poly/region in coverage units (Source: Computed)

    Whole numbers that are automatically generated.

    LENGTH
    Length of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    BBEXPFOR#
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    BBEXPFOR-ID
    User-defined feature number. (Source: ESRI)

    BBEXPFOR.AAT
    Attribute table of BBEXPFOR.AAT (Source: ARC/INFO)

    -
    Attribute table of BBEXPFOR_BNF_BNF.AAT (Source: ARC/INFO)

    Sequential unique whole numbers that are automatically generated.

    BBEXPFOR#
    Internal feature number (Source: Computed)

    Coordinates defining the features.

    BBEXPFOR-ID
    User-assigned feature number (Source: User-defined)

    Positive real numbers that are automatically generated.

    FNODE#
    Internal number of from-node (Source: Computed)

    Positive real numbers that are automatically generated.

    LENGTH
    Length of arc in coverage units (Source: Computed)

    Sequential unique whole numbers that are automatically generated.

    LPOLY#
    Internal number of poly to left of arc (Source: Computed)

    RPOLY#
    Internal number of poly to right of arc (Source: Computed)

    TNODE#
    Internal number of to-node (Source: Computed)

    Entity and attribute overview: 
    ArcInfo Poly layer.
Bbexpfor.aat only system generated items.
bbexpf.pat only system generated items and NAME added:  Bear Run, Headquarters, and Bannock-Pine.

    Entity and attribute detail citation: 
    Not Available
Back to Top

Who produced the data set?

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

    • Boise National Forest GIS Staff

  2. Who also contributed to the data set?

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

    Diane McConnaughey
    Boise National Forest GIS Staff
    GIS Specialist
    1249 South Vinnell Way
Suite 200
    Boise, ID 83709
    USA

    (208) 373-4247 (voice)
    dmcconnaughey@fs.fed.us
Back to Top

Why was the data set created?

This dataset was designed to be used for map display, and analysis in future Forest Plan Revisions. These data should be displayed and analyzed at scales appropriate for 1:24,000-scale data - it is believed that this layer was digitized from 1:24000 maps, most likely mylar. No responsibility is assumed by the Boise National Forest GIS Staff in the use of these data.

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: 19980403 (change 1 of 22) 
    SHAYES BUILD BBSNEF LINE

    Date: 19980403 (change 2 of 22) 
    SHAYES RENAME BBSNEF BBEF_BND

    Date: 19980403 (change 3 of 22) 
    SHAYES CLEAN BBEF_BND BBEFBND2

    Date: 19980403 (change 4 of 22) 
    SHAYES PROJECTDEFINE COVER BBEFBND2

    Date: 19980403 (change 5 of 22) 
    SHAYES PROJECTDEFINE COVER BBEFBND2

    Date: 19980403 (change 6 of 22) 
    EXTERNAL BBEFBND2

    Date: 19980403 (change 7 of 22) 
    DWALL IMPORT COVER BBEFBND2 BBEFBND2

    Date: 19980403 (change 8 of 22) 
    DWALL ARCEDIT /.../CELL1.BOISE-NF.R4.FS.FED.US/FS/FSFILES/OFFICE/GISDEV/BNFDEV/B

    Date: 19980403 (change 9 of 22) 
    DWALL ARCEDIT /.../CELL1.BOISE-NF.R4.FS.FED.US/FS/FSFILES/OFFICE/GISDEV/BNFDEV/B

    Date: 19980403 (change 10 of 22) 
    DWALL BUILD BBEFBND2 POLY

    Date: 19980403 (change 11 of 22) 
    DWALL IDEDIT BBEFBND2 POLY

    Date: 19980406 (change 12 of 22) 
    DWALL ARCEDIT /.../CELL1.BOISE-NF.R4.FS.FED.US/FS/FSFILES/OFFICE/GISDEV/BNFDEV/B

    Date: 19980406 (change 13 of 22) 
    DWALL BUILD BBEFBND2 POLY

    Date: 19980406 (change 14 of 22) 
    DWALL IDEDIT BBEFBND2 LINE

    Date: 19980406 (change 15 of 22) 
    DWALL IDEDIT BBEFBND2 POLY

    Date: 19980406 (change 16 of 22) 
    DWALL RENAME BBEFBND2 BBEXPF

    Date: 19980806 (change 17 of 22) 
    DWALL ARCEDIT /FSFILES/OFFICE/GISDEV/BNFDEV/BBEXPF

    Date: 19980810 (change 18 of 22) 
    DWALL   DOCUMENT BBEXPF CREATE DWALL

    Date: 19980810 (change 19 of 22) 
    DWALL   DOCUMENT BBEXPF UPDATE DWALL

    Date: 19980810 (change 20 of 22) 
    DWALL COPY BBEXPF /FSFILES/REF/LIBRARY/GIS/BOISE/FORESTMGT/BBEXPF

    Date: 19980810 (change 21 of 22) 
    DWALL   DOCUMENT BBEXPF UPDATE DWALL

    Date: 20000707 (change 22 of 22) 
    EXPORT COVER BBEXPFOR BBEXPFOR_BNF_BNF.E00

The orginal coverage contributed by Diane McConnaughey was imported into ARC/INFO, renamed, and exported.  The file was then compressed using GZIP.

Metadata included with the original coverage (created using DOCUMENT.AML) was imported.  If the metadata was not FGDC compliant, it was updated to be compliant.

    Person responsible for change:
    Bruce Godfrey
    University of Idaho Library
    GIS Specialist
    PO Box 442350
    Moscow, ID 83844-2350
    USA

    208-885-6463 (voice)
    208-885-6817 (FAX)
    bgodfrey@uidaho.edu

Back to Top

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

  1. How well have the observations been checked?

    See Entity_Attribute_Information

  2. How accurate are the geographic locations?

    Unknown

  3. How accurate are the heights or depths?

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

    Complete to the best of my knowledge

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

    Polygon and chain-node topology present.

Back to Top

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

Distributor 1 of 1

  1. Who distributes the data set?

    Bruce Godfrey
    University of Idaho Library
    GIS Specialist
    PO Box 442350
    Moscow, ID 83844-2350
    USA

    208-885-6463 (voice)
    208-885-6817 (FAX)
    bgodfrey@uidaho.edu

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    Although these data have been processed successfully on a computer system at the University of Idaho Library, no warranty, expressed or implied, is made regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty.

  4. How can I download or order the data?

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

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

Back to Top

Who wrote the metadata?

Dates:
Last modified: 19980810
Last reviewed: 20040527

Metadata author:
Diane McConnaughey
Boise National Forest GIS Staff
GIS Specialist
1249 South Vinnell Way
Suite 200
Boise, ID 83709
USA

(208) 373-4247 (voice)
dmcconnaughey@fs.fed.us

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

Metadata extensions used:
  • http://www.esri.com/metadata/esriprof80.html

    • Back to Top