Ontologia

Rivière

Bean Lateral

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

Crosses 2 administrative regions : Bannock, Power

rivière

Max discharge

16m³/s

Max Strahler

5

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-7080466160488 km²

2 administrative regions crossed (GADM L2)

  • Bannock
    Idaho · United States
    8.5 km
    in this dpt
  • Power
    Idaho · United States
    6.6 km
    in this dpt

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

Species present

530 distinct species · 11 870 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 27 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 Bean Lateral : 17 espèces reliées par 99 interactions GloBI sur 4 types (connectance 26.2%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
28
Interactions affichées
99
Connectance
0.262
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.

3,8km

Max discharge

16,0m³/s

Max Strahler

5

Segments matched

1

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