Rivière· 85 segments
Swift Current Creek
Crosses 3 administrative regions : Division No. 4, Division No. 7, Division No. 8
Total length
396km
Max discharge
3m³/s
Max Strahler
4
Segments matched
85
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- Division No. 8Saskatchewan · Canada211.6 kmin this dpt
- Division No. 4Saskatchewan · Canada114.7 kmin this dpt
- Division No. 7Saskatchewan · Canada62.9 kmin this dpt
8 intersecting protected areas
Wildlife Habitat Protection
IUCN Not ApplicableWildlife Habitat Protection
Private Conservation Lands
IUCN IVPrivate Conservation Lands
Water Security Agency
IUCN Not ApplicableWater Security Agency
Crown Conservation Easement
IUCN IVCrown Conservation Easement
Migratory Bird Sanctuary
Fish and Wildlife Development Fund Land
Fish and Wildlife Development Fund Land
Fish and Wildlife Development Fund Land
1 page = 1 named river (aggregation of 85 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
17 distinct species · 18 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 8 species (selected proportionally per kingdom among those with at least one documented interaction here) to keep the graph readable. Hover for details, click to explore the full ecosystem of a species.
ℹ️ The territory contains many more species than displayed and all their documented interactions: the graph is intentionally the structural skeleton (top-N species by composite local score, edges filtered by Serrano 2009 disparity filter α=0.2).
Indicateurs du tissu écologique
Tissu écologique de Swift Current Creek : 6 espèces reliées par 7 interactions GloBI sur 3 types (connectance 25.0%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
396km
Max discharge
3,0m³/s
Max Strahler
4
Segments matched
85
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.