Ontologia

Ruisseau· 8 segments

Martins Fork Cumberland River

Crosses 3 administrative regions : Bell, Harlan, Lee

ruisseau

Total length

61km

Max discharge

4,6m³/s

Max Strahler

3

Segments matched

8

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806188803151 km²

3 administrative regions crossed (GADM L2)

  • Harlan
    Kentucky · United States
    41.5 km
    in this dpt
  • Bell
    Kentucky · United States
    0.0 km
    in this dpt
  • Lee
    Virginia · United States
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

174 distinct species · 923 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Martins Fork Cumberland River : 32 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 67 interactions GloBI sur 3 types (connectance 8.2%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
67
Connectance
0.082
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

61km

Max discharge

4,6m³/s

Max Strahler

3

Segments matched

8

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