Ontologia

Fleuve

Tusher Wash

⚠ Partial coverage : only 1 named segment matched so far. The real fleuve extends much further (Strahler order 7 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.

Crosses 2 administrative regions : Emery, Grand

fleuve

Max discharge

208,1m³/s

Max Strahler

7

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-70805706602121 km²

2 administrative regions crossed (GADM L2)

  • Grand
    Utah · United States
    1.4 km
    in this dpt
  • Emery
    Utah · United States
    0.0 km
    in this dpt

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

Species present

242 distinct species · 1 180 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Tusher Wash : 34 espèces reliées par 123 interactions GloBI sur 4 types (connectance 13.0%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
123
Connectance
0.130
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)

Matched len.

7,2km

Max discharge

208,1m³/s

Max Strahler

7

Segments matched

1

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