Ontologia

Ruisseau· 3 segments

Blue Spring Branch

Crosses 3 administrative regions : Carter, McMinn, Perry

ruisseau

Total length

36km

Max discharge

0,4m³/s

Max Strahler

1

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-70805991702561 km²

3 administrative regions crossed (GADM L2)

  • Perry
    Missouri · United States
    5.7 km
    in this dpt
  • Carter
    Tennessee · United States
    3.4 km
    in this dpt
  • McMinn
    Tennessee · United States
    0.7 km
    in this dpt

1 intersecting protected areas

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

Species present

70 distinct species · 136 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Blue Spring Branch : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 52 interactions GloBI sur 3 types (connectance 9.3%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
34
Interactions affichées
52
Connectance
0.093
Patrimoniales
1
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

36km

Max discharge

0,4m³/s

Max Strahler

1

Segments matched

3

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