First results

This is a first complete set of results from this code. Data were pulled from PISCES at the time of the run on October 21, 2019. Only data for species categorized as "Wide Ranging" in PISCES were included.

The tag for this code references the exact code used to create this output (sans the parts in PISCES that pulled the data). In summary, a species is considered to be in every stream within its current range with a stream order above its prime stream order (see the README for calculation of prime stream order). These segments receive a probability of 1. Segments within a species range with a Strahler stream order equal to the prime stream order are given a probability of 0.9.

Below the prime stream order, the values decay, being cut in half each time (0.45 for the first stream order below the prime stream order, 0.225 for the next one, etc). Few taxa reach even 0.225 though, because most wide-ranging species have prime stream orders of 2 or below.

The data attached to this release is a zipped geopackage (compatible in all major open source and proprietary GIS packages, and is also just a SQLite database compatible with virtually every programming language). rows are stream segments, and the later columns are 5 character PISCES species codes. See https://pisces.ucdavis.edu for more about these species codes and determining the actual species for them. Values in those columns represent the probability for a species on that segment.

MAJOR NOTE: This data isn't ready for prime time. This is a first pass! Generally speaking, we think segments with higher probabilities very likely have the species, at least at relevant times of year, and segments with lower probabilities are less likely to have them, but that's about as certain as the values are. The exact probability values are not backed by research - instead, it's meant to determine which segments most likely have them, and then not rule everything else out, instead saying "probably not". Please get in touch with Nick Santos (contact link at bottom of README) with questions.