Name: Fish_FishPresenceStreams

Display Field: HName

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: Presence and potential presence of fish in streams. Potential Presence or Distribution data extrapolates from presence data to describe what species would probably be found in similar habitat for which there might not be any data. It is not necessary to sample every waterbody to determine which species occur where. The purpose is to have a value for every stream (or stream segment) and thereby show the full extent of a specie's distribution. An example would be the data from the presence-absence database in FisRef: It has a value for every 1:100k EPA River Reach number in Idaho. The value is based upon the expert opinion of fisheries biologists and their knowledge of fish habitat and use. Presence data describes what species were found by sampling (sometimes not found) for a given place, time, and method. The purpose is to document the presence for a given fraction of a specie's range based upon actual observations. Often, only a target species and a few incidental species were enumerated. Therefore, one cannot say that a species absolutely does not occur for a given waterbody. Fish move and waterbodies change. The probability that a species is or is not detected increases with the number of suveys. Therefore, one would not query for one record of presence for a waterbody in order to answer the question "what fish are in this stream or lake". It would be better to query for all records of presence (or absence). The data from the FIS Ref and GIS are mostly from published documents (reviewed by peers) and expert opinion. That data is more reliable than some of the raw, FishData survey data. The source documents are archived at IDFG and/or CRITFC libraries. The expert opinion used to generate the distribution updates is an extrapolation of the survey observations and published reports. Every water body cannot be surveyed. Therefore, findings from surveyed segments of water bodies are also applied to similar water bodies that are not surveyed. There are usually multiple surveys for a species per stream segment. The GIS distribution data should overlap most of the other data because it is, by definition, the estimated extent of distribution for a species at a given time. The other data are smaller segments that provide a detailed snapshot (or index) of the bigger GIS data. The FishData references are mostly surveys by IDFG regional personnel. They were stored in a wide variety of database formats (Dbase, Word documents, Excel workbooks, Lotus spreadsheets, Paradox databases, Access datases, etc.). The FisColp references are from the IDFG Collectors Permit files (IDFGHQ). They are the reports sent to IDFG by people given collectors permits. They were historically quite incomplete: Sometimes a stream name and a common name of game fish only were reported. A specific section of stream and scientific name was not supplied. The process has been refined and the quality of the data is much improved. GPS coordinates and scientific names of both game and non-game species of fish and amphibians, reptiles are often included. Shapefiles have been included to aid in analysis of the data. Hydrologic Unit Codes (HUC) are provided at the 4th and 6th code levels. The massive amounts of data can be selected for an area of interest and "whittled down to size" using the HUCs. Do's and Don'ts: Do use this presence data to get a snapshot of fish distribution for a given time, place, and methodology which can be extrapolated to similar water bodies. Do not use this presence data to say that there absolutely are not fish in this stream forever (check dates, methods, etc.). Do use the distribution data to get an estimate of the extent of a specie's range.

Service Item Id: d928785c2d9a4859a490b31dafd5a2a8

Copyright Text:

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Supports Datum Transformation: true

Extent:

XMin: 2269447.1202999996
YMin: 1373957.6063
XMax: 2300729.636
YMax: 1404400.3653999995
Spatial Reference: 102605  (8826)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [115, 223, 255, 255]
Width: 5
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID_1 ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
• HName ( type: esriFieldTypeString, alias: HName, length: 100 )
• LLID ( type: esriFieldTypeString, alias: LLID, length: 13 )
• Year_ ( type: esriFieldTypeString, alias: Year_, length: 254 )
• PName ( type: esriFieldTypeString, alias: PName, length: 100 )
• Mfrom ( type: esriFieldTypeInteger, alias: Mfrom )
• LoBound ( type: esriFieldTypeString, alias: LoBound, length: 100 )
• Mto ( type: esriFieldTypeInteger, alias: Mto )
• UpBound ( type: esriFieldTypeString, alias: UpBound, length: 100 )
• BeginDate ( type: esriFieldTypeDate, alias: BeginDate, length: 8 )
• EndDate ( type: esriFieldTypeDate, alias: EndDate, length: 8 )
• SName ( type: esriFieldTypeString, alias: SName, length: 64 )
• FED_STATa ( type: esriFieldTypeString, alias: FED_STATa, length: 254 )
• NFish ( type: esriFieldTypeInteger, alias: NFish )
• SampleMeth ( type: esriFieldTypeString, alias: SampleMeth, length: 40 )
• UseType ( type: esriFieldTypeString, alias: UseType, length: 30 )
• Presence ( type: esriFieldTypeString, alias: Presence, length: 30 )
• Notes ( type: esriFieldTypeString, alias: Notes, length: 254 )
• RefDB ( type: esriFieldTypeString, alias: RefDB, length: 8 )
• Title ( type: esriFieldTypeString, alias: Title, length: 254 )
• TypeID ( type: esriFieldTypeInteger, alias: TypeID )
• HydroID ( type: esriFieldTypeInteger, alias: HydroID )
• SPECIESID ( type: esriFieldTypeInteger, alias: SPECIESID )
• SciName ( type: esriFieldTypeString, alias: SciName, length: 75 )
• Rfederal ( type: esriFieldTypeString, alias: Rfederal, length: 10 )
• Rstate ( type: esriFieldTypeString, alias: Rstate, length: 10 )
• Shape_Leng ( type: esriFieldTypeDouble, alias: Shape_Leng )
• Shape_Length ( type: esriFieldTypeDouble, alias: Shape_Length )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata