. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Northern Spotted Owl Site Summary 2016 Publication Point

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Northern Spotted Owl Site Summary 2016 Publication Point

Abstract:
NSO_SITESUM_PUBLIC_POINT: Data describing Northern Spotted Owl (NSO) nest sites, pair status, reproductive data, visits, etc. See Supplemental Information for greater detail and a list of Owl Species abreviations used in this data.

Supplemental information:
Bureau of Land Management (BLM). Northern Spotted Owl (NSO A published revision of the Department Manual's Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at: http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm.) The spotted owl Site data are coordinates that have been determined to be unique locations through evidence of continued use by owls. A Site is designated for any location of breeding spotted owls, the presence of young before dispersal, the repeated location of a pair during a single season or over several years, or some other strong indication of continued occupation. The repeated detection of a single owl during the same season or over several years usually does not warrant a Site designation. If the owl's center of activity/nest grove has moved sufficiently to change critical Site file information, a new Alternate is designated. An Alternate Site Center will normally result from the location of a new nest tree or newly fledged juveniles at a new location for a previously known pair. Some examples of a sufficient change are; location in a different 1/16 Section, location greater than ΒΌ mile from a previous Alternate, landowner change, different administrative designation, change in land classification such as critical habitat, etc. One exception to this is when barred owls occupy historic Sites or Alternates. The presence of barred owls may result in abandonment of a site center, documenting the new spotted owl use area is important in these instances. A new Alternate that is not based on a nest grove should have at least 2 years of known activity at that location without use of another Alternate. Each Site location is assigned a unique four digit master site number (MSNO), the MSNO followed by a letter designating the Alternate (O, A, B, etc) is the assigned five digit Identification number (IDNO). A single, or multiple IDNO's may exist for each Site. The spotted owl summary portion of the data includes a single record for each year at every owl site with survey effort (and some with no survey effort), and is compiled from all survey visits during the given year. The summary data is attached to the coordinate for a unique IDNO at each site. Each summary record includes information such as survey effort, occupancy, nesting status, and reproductive status. When using the information from the summary data, be aware of the definitions so the data is correctly interpreted. STOC Northern Spotted Owl, only spotted owls are surveyed for or detected. STVA Barred Owl, only barred owls are detected. STNE Great Gray Owl, only great gray owls are detected. SBOH Spotted Owl Barred Owl hybrid, any generation, (no pure bred spotted owls present). This code will also be used on the rare instances when a hybrid/STVA mixed pair are encountered. STMX - Mixed pair (one pure bred spotted owl present). Provide a description of the species composition in the Comment field, e.g. Male spotted owl with a female barred owl. Be conservative when making this determination since this implies that the individuals are actually a social pair. A male and female should be detected in close proximity several times during the year. STUN Genus Strix, unknown species. BUVI Great Horned Owl detected.

  1. How should this data set be cited?

    Bureau of Land Management, BLM OR Northern Spotted Owl Site Summary 2016 Publication Point.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.312174
    East: -121.985674
    North: 45.856465
    South: 42.023569

  3. What does it look like?

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

  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 (30460)

    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 8.98315284119521e-009. Longitudes are given to the nearest 8.98315284119521e-009. Latitude and longitude values are specified in Decimal Degrees.

      The horizontal datum used is D North American 1983.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    OSODBA.NSO_SITESUM_PUBLIC_POINT
    Northern Spotted Owl site location and species data. (Source: BLM)

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    Location_Name
    Common name of location (Source: BLM)
                      

    SUMMARY_MSNO
    A unique 4 digit Master Site Number assigned to each designated site under a statewide numbering system coordinated by the Oregon Department of Fish and Wildlife (ODFW), Northwest Region Office. (Source: BLM)
                      

    SUMMARY_IDNO
    A concatenation of the MSNO and Location Identifier (Alternate) in the Site table.  When there are multiple Alternates, this narrows down the specific location within the MSNO site where the summary data has been collected. (Source: BLM)
                      

    SUMMARY_YEAR
    A 4 character field representing the year the summary data is collected. (Source: BLM)
                      

    DAY_VISITS
    The number of day visits to the site during the year, these do not include the opportunistic or incomplete "Additional" visits. (Source: BLM)
                      

    NIGHT_VISITS
    The number of night visits to the site during the year, these do not include the opportunistic or incomplete "Additional" visits.  Night visits include visits spanning day and night if the majority of the survey occurred during the night. (Source: BLM)
                      

    SUMMARY_PAIR_STATUS
    A single character code which lists the Pair Status for the IDNO for the summary year.  For sites with an owl confirmed at another site, both sites will be summarized as occupied.  Manually edit the summary file with comments regarding possible duplicate occupation, the need to combine nesting or reproduction, or justification for limited surveys at one of the sites.  Since only STOC is summarized by the application, any visits with a species STMX (mixed species, one pure spotted owl) or STUN (unknown Strix) will need manual edits.  Pair Status is determined as follows for species STOC: (Source: BLM)
                      

    MALES
    The maximum number of males present at the site during the year.  All for species STOC, for the particular IDNO. (Source: BLM)
                      

    FEMALES
    The maximum number of females present at the site during the year.  All for species STOC, for the particular IDNO (Source: BLM)
                      

    UNKNOWNS
    The maximum number of non-juveniles at the site during the year where the sex is not determined.  Use this field only if the number of unknown sex birds exceeds the number of known sex birds.  For example, if 2 unknown sex birds are detected on one visit, and a male is detected on another visit, the number of unknown sex equals 1 and the number of males equal 1.  If all of the Visits to the IDNO resulted in nothing but unknowns, the number of unknowns is counted. All for species STOC, for the particular IDNO. (Source: BLM)
                      

    FLEDGLINGS
    The maximum number of fledglings detected audibly or visually at the site during the year.  Fledglings are defined as young that have left the nest tree.  All for species STOC, for the particular IDNO. (Source: BLM)
                      

    SUMMARY_NESTING_STATUS
    A single character code which lists the Nesting Status for the IDNO for the summary year. (Source: BLM)
                      

    REPRO_SUCCESS
    A single character code which indicates the reproductive success for species STOC for the summary year. (Source: BLM)
                      

    FINAL_NEST_REPRO
    A single character code indication of the final nesting and reproduction status for species STOC for the summary year.  This field summarizes the LATEST stage of nesting or reproduction at the site during the year. (Source: BLM)
                      

    UTMX
    A 6 digit code for the site center in UTM coordinates. A typical entry of UTMX would be 513623.  The last digit indicates an accuracy to within 1 meter.  If you do not feel that the location is accurate to 1 meter, fill the last place(s) with 0 (513620).  All UTM entries are in North America Datum 27, Zone 10. (Source: BLM)
                      

    UTMY
    A 7 digit code for the site center in UTM coordinates. A typical entry of UTMY would be 513623.  The last digit indicates an accuracy to within 1 meter.  If you do not feel that the location is accurate to 1 meter, fill the last place(s) with 0 (513620).  All UTM entries are in North America Datum 27, Zone 10. (Source: BLM)
                      

    L1_PRI_SITE_LO
    The Level 1 landowner is a 2 digit code indicating the landowner or agency administering the land at the nest site, core area, or whatever point on the map is the site center(primary landowner).  This is ownership at the actual point, and may be different from the Resource Area boundary designated in the field SI_GI above.  If a second landowner exists within the immediate vicinity (e. g. 1/4 mile) of the owl, the Level 1 secondary landowner is entered as SI_L1S. (Source: BLM)
                      

    L2_PRI_SITE_LO
    .A 3 digit code for the secondary level of land ownership, such as National Forest, BLM District, Private Company, Municipality, Reservation, etc. for the nest site, core area, or whatever point on the map is the site center.  If a second landowner exists within the immediate vicinity (e. g. 1/4 mile) of the owl, the secondary landowner is entered as SI_L2S. (Source: BLM)
                      

    DEMOGRAPHY_AREA
    2 character alphabetical code for demographic area (Source: BLM)
                      

    TOWNSHIP
    Township number of site (Source: BLM)
                      

    District
    BLM District that contains the site. (Source: BLM)
                      

    SITE_SECTION
    Section number of site (Source: BLM)
                      

    QUARTER_SECTION
    Quarter Section location of site (Source: BLM)
                      

    SIXTEENTH_SECTION
    Sixteenth Section location of site (Source: BLM)
                      

    Range
    Range number of site (Source: BLM)
                      

    RESOURCE_AREA
    BLM Resource Area (Source: BLM)
                      

    Shape
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    SUMMARY_SPECIES
    Summary species type (Source: BLM)
                      

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)

    • Bureau of Land Management

  2. Who also contributed to the data set?

    OR/WA BLM

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

    Bruce Hollen
    Bureau of Land Management
    Wildlife Biologist
    P.O. Box 2965
    Portland, OR 97208
    US

    503-808-6604 (voice)
    bhollen@blm.gov
Back to Top

Why was the data set created?

Data is the public release of BLM corporate source NSO site data to be used for planning and resource management.

Back to Top

How was the data set created?

  1. Where did the data come from?

    NSO_SUMMARY_20160608 (source 1 of 3)

    Bureau of Land Management, 20160608, NSO (Northern Spotted Owl) network database, BLM Oregon State Office..

    Other citation details:
    No metadata or title for this table.

    Type of source media: onLine
    Source contribution:
    OR?WA BLM

    NSO_MSNO_20160608 (source 2 of 3)

    Bureau of Land Management, 20160608, NSO (Northern Spotted Owl) network database, BLM Oregon State Office..

    Other citation details:
    No metadata or title for this table.

    Type of source media: onLine
    Source contribution:
    OR/WA BLM

    NSO_SITE_20160608 (source 3 of 3)

    Bureau of Land Management, 20160608, NSO (Northern Spotted Owl) network database, BLM Oregon State Office..

    Other citation details:
    No metadata or title for this table.

    Type of source media: onLine
    Source contribution:
    OR/WA BLM

  2. What changes have been made?

    Date: 20140901 (change 1 of 2)
    The NSO network database Site and Summary tables were queried. Two files were created, one consisting of only Site information, and one consisting of all Summary information with Site file coordinates attached to it. Within each of these files the data has been broken into 2 categories, the "internal" category includes all data points, the "external" does not include data points on private land.

    Person responsible for change:
    Eric Hiebenthal
    Bureau of Land Management
    GIS Data Administrator
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6565 (voice)
    ehiebent@blm.gov

    Date: 20160608 (change 2 of 2)
    1. Snapshot taken of NSO Site, Summary, and MSNO tables. NSO_Snapshot_20160608.mdb NSO_SUMMARY_20160608 NSO_SITE_20160608 NSO_MSNO_20160608 2. Edited NSO_SITE_20160608 to remove BSNO and TSNO sites. 3. Tables displayed as event tables using Site UTM fields, UTM 10 NAD 83 projection. Exported as feature classes. NSO_SITE_20160608_PT NSO_SUMMARY_20160608_PT (Joined to NSO_SITE_20160608_PT for geographic attributes) 4. Added MS_LNAME (Master Site Number Location Name) field to the NSO_SITE_20160608_PT feature class. 5. Joined NSO_SITE_20160608_PT to a copy of the MSNO (Master Site Number) table and calculated the Location Name field. 6. Copied existing spotted_owl geodatabase from g:\corp\BLMReplication\ORWA_rep_gdb. Truncated feature classes. Updated field data types and max lengths to match the NSO database. It appears the existing data types were taken from the excel spreadsheet that was used to generate the data and are less precise. 7. Created geodatabase domains for the fields in the template geodatabase using the latest NSO lists of values. Removed the Geographic Province and Summary Tree Location fields because they no longer exist within the NSO database. Added species fields. 8. Loaded data from NSO_SITE_20160608_PT into nso_site_point in the spotted_owl_2015 geodatabase. 9. Loaded data from NSO_SUMMARY_20160608_PT into nso_sitesum_point in the spotted_owl_2015 geodatabase. 10. Assigned domains to the appropriate fields to improve the usability of the data. Did not include domains for Summary Code fields as per Mike Blow. 11. Select data from nso_site_point and nso_sitesum_point where the location of records is within BLM ownership. Where the Primary Landowner is BLM (code 07) and USFS (code 06) 12. Exported data to spotted_owl_pub_2015 geodatabase. Assigned domains to the appropriate fields in the public geodatabase.

    Person responsible for change:
    Dana Baker-Allum
    OR?WA BLM
    GIS Application Developer / eGIS
    P.O. Box 2965
    Portland, OR 97208
    US

    503 808-6320 (voice)
    dbakerallum@blm.gov

Back to Top

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

  1. How well have the observations been checked?

    No formal logical accuracy tests were conducted.

  2. How accurate are the geographic locations?

    No formal logical accuracy tests were conducted.

  3. How accurate are the heights or depths?

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

    Data is complete and accurate for BLM managed lands in Oregon and Washington.

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

    No formal logical accuracy tests were conducted.

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: PUBLIC DATA: None, these data are considered public domain.
Use constraints:
These data are provided by Bureau of Land Management (BLM) "as is" and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification.

Distributor 1 of 1

  1. Who distributes the data set?

    Eric Hiebenthal
    Bureau of Land Management
    GIS Data Management Specialist
    P.O Box 2965
    Portland, OR 97208
    US

    503-808-6340 (voice)
    503-808-6419 (FAX)
    ehiebent@blm.gov
    Contact Instructions:
    contact instructions

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.

  4. How can I download or order the data?

    • Availability in digital form:


    • Data format:
      in format Arc GIS Feature Class (version Feature Class) Winzip

    • Cost to order the data: Contact distributor.


    • Special instructions:

      Data are only available through the Oregon/Washington State office of the Bureau of Land Management.

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

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR 97208
US

(503) 808-6340 (voice)
(503) 808-6419 (FAX)
r2mills@blm.gov
Hours of Service: 8:00-4:00
Contact Instructions:
None

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

Back to Top