Ontologia

Rivière· 6 segments

Fisher Creek

Crosses 4 administrative regions : Cuming, Jackson, Park, Rock

rivière

Total length

581km

Max discharge

52,8m³/s

Max Strahler

5

Segments matched

6

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080498410223 km²

4 administrative regions crossed (GADM L2)

  • Cuming
    Nebraska · United States
    23.7 km
    in this dpt
  • Park
    Montana · United States
    4.4 km
    in this dpt
  • Jackson
    North Carolina · United States
    3.5 km
    in this dpt
  • Rock
    Wisconsin · United States
    1.0 km
    in this dpt

3 intersecting protected areas

1 page = 1 named river (aggregation of 6 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

26 distinct species · 47 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 20 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Fisher Creek : 18 espèces reliées par 27 interactions GloBI sur 2 types (connectance 14.2%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
20
Interactions affichées
27
Connectance
0.142
Patrimoniales
0
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

581km

Max discharge

52,8m³/s

Max Strahler

5

Segments matched

6

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.