Name: Spotted Owl Observations
Display Field: CNAME
Type: Feature Layer
Geometry Type: esriGeometryPoint
Description: This dataset is a new and improved version of the original Spotted Owl Territories [ds97] dataset. The original dataset represented spotted owl territories as activity center observation points with thousands of additional owl observations available in a separate table but not spatially enabled. In this new dataset, the additional owl observations (both positive and negative sightings) have been spatially enabled as points and are now displayed along with the activity center points. See the attribute "TYPEOBS" for a determination of whether an observation is positive (POS), negative (NEG) or an activity center (AC). Many of the observation locations were approximated by plotting them to a grid of the Public Land Survey System (PLSS) based on PLSS references in their record descriptions. What is an activity center? "Activity Center: Spotted owls have been characterized as central-place foragers, where individuals forage over a wide area and subsequently return to a nest or roost location that is often centrally-located within the home range (Rosenberg and McKelvey 1999). Activity centers are location or point within the core use area that represent this central location. Nest sites are typically used to identify activity centers, or in cases where nests have not been identified, breeding season roost sites or areas of concentrated nighttime detections may be used to identify activity centers." U.S. Fish and Wildlife Service. 2011. Revised Recovery Plan for the Northern Spotted Owl (Strix occidentalis caurina). U.S. Fish and Wildlife Service, Portland, Oregon. xvi + 258 pp. A copy of the Revised Recovery Plan and other related materials can be found at: http://www.fws.gov/species/nsoAn additional dataset (Spotted Owl Observations Spider Diagram [ds705]) is available that shows lines representing relationships between activity centers and observations in this dataset. The spider diagram dataset is meant to accompany this observations dataset to assist with territory visualizations and dataset review efforts. This dataset combines information on the location and status of Northern Spotted Owls, California Spotted Owls in the Sierra Nevada, and California Spotted Owls in southern California. Almost all records have been gathered since the early 1970s. Some observations from early 20th century literature also are included. The vast majority of data were collected in the field by biologists and technicians mainly working for US Forest Service, Bureau of Land Management, California Department of Fish and Wildlife, consultants, National Park Service, industrial timber companies, universities conducting surveys and doing research, and the local birding community. Most observations were obtained using standard survey protocols ("Protocol for surveying proposed management activities that may impact northern spotted owls." US Fish and Wildlife Service. 2011). The protocols are available at http://www.dfg.ca.gov/wildlife/nongame/survey_monitor.htmlOTHER THINGS TO KNOW: - Sites are not dropped from the dataset due to lack of occupancy over time. - Coordinates listed in the dataset use the NAD83 datum. - Many site locations in this dataset were approximated using a grid of the Public Land Survey System (PLSS, also known as the Meridian, Township, Range, and Section, or MTRS system). The PLSS grid originated from 1:100,000-scale US Geological Survey topographic maps and also included additional protracted/extrapolated linework within Spanish land grants and other areas not covered by the PLSS process. At the time of data processing, this PLSS grid represents the most complete statewide grid available for California. However, the linework from this grid does not always exactly follow the PLSS linework used on other sources such as 1:24,000-scale US Geological Survey topographic maps, which may have been used for site reporting. New mapping and compilations of PLSS linework are occurring in many areas in California but may not be available statewide. As more improved and complete statewide PLSS data become available, it may be possible to better approximate some site locations in this dataset.
Service Item Id: 4745cc6d213e475ebe5254cb9a2def10
Copyright Text:
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 100000
Max Scale: 0
Supports Advanced Queries: false
Supports Statistics: false
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
XMin: -1.3858595756812368E7
YMin: 3856635.071004594
XMax: -1.289781883929288E7
YMax: 5176299.435003015
Spatial Reference: 102100
(3857)
Drawing Info:
Renderer:
Simple Renderer:
Symbol: Style: esriSMSCircle
Color: [47, 141, 163, 255]
Size: 4.0
Angle: 0.0
XOffset: 0
YOffset: 0
Outline:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: false
Supports Having Clause: false
Supports Count Distinct: false
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: false
Supports Query With Current User: true
HasZ: false
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
-
FID
(
type: esriFieldTypeOID, alias: FID
)
-
Shape
(
type: esriFieldTypeGeometry, alias: Shape
)
-
SNAME
(
type: esriFieldTypeString, alias: SNAME, length: 31
)
-
CNAME
(
type: esriFieldTypeString, alias: CNAME, length: 22
)
-
OBSID
(
type: esriFieldTypeInteger, alias: OBSID
)
-
MASTEROWL
(
type: esriFieldTypeString, alias: MASTEROWL, length: 7
)
-
TYPEOBS
(
type: esriFieldTypeString, alias: TYPEOBS, length: 4
)
-
OBSERVER
(
type: esriFieldTypeString, alias: OBSERVER, length: 25
)
-
DATEOBS
(
type: esriFieldTypeString, alias: DATEOBS, length: 10
)
-
TIMEOBS
(
type: esriFieldTypeString, alias: TIMEOBS, length: 10
)
-
NUMADOBS
(
type: esriFieldTypeString, alias: NUMADOBS, length: 5
)
-
AGESEX
(
type: esriFieldTypeString, alias: AGESEX, length: 5
)
-
PAIR
(
type: esriFieldTypeString, alias: PAIR, length: 1
)
-
NEST
(
type: esriFieldTypeString, alias: NEST, length: 1
)
-
NUMYOUNG
(
type: esriFieldTypeString, alias: NUMYOUNG, length: 5
)
-
SUBSPECIES
(
type: esriFieldTypeString, alias: SUBSPECIES, length: 2
)
-
LONDD_N83
(
type: esriFieldTypeDouble, alias: LONDD_N83
)
-
LATDD_N83
(
type: esriFieldTypeDouble, alias: LATDD_N83
)
-
COORDSRC
(
type: esriFieldTypeString, alias: COORDSRC, length: 25
)
-
DOCID
(
type: esriFieldTypeString, alias: DOCID, length: 50
)
-
COMMENTS
(
type: esriFieldTypeString, alias: COMMENTS, length: 254
)
-
MTRS
(
type: esriFieldTypeString, alias: MTRS, length: 16
)
-
HIGHESTUSE
(
type: esriFieldTypeString, alias: HIGHESTUSE, length: 254
)
-
SYMBOLOGY
(
type: esriFieldTypeString, alias: SYMBOLOGY, length: 15
)
-
LSASource
(
type: esriFieldTypeString, alias: LSASource, length: 250
)
Supported Operations:
Query
Query Attachments
Query Analytic
Generate Renderer
Return Updates
Iteminfo
Thumbnail
Metadata