Ontologia

Ruisseau· 29 segments

Shavers Fork

Crosses 3 administrative regions : Pocahontas, Randolph, Tucker

ruisseau

Total length

148km

Max discharge

12,5m³/s

Max Strahler

3

Segments matched

29

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080562560519 km²

3 administrative regions crossed (GADM L2)

  • Randolph
    West Virginia · United States
    95.2 km
    in this dpt
  • Tucker
    West Virginia · United States
    11.5 km
    in this dpt
  • Pocahontas
    West Virginia · United States
    6.6 km
    in this dpt

6 intersecting protected areas

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

Species present

112 distinct species · 285 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 Shavers Fork : 34 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 36 interactions GloBI sur 5 types (connectance 4.6%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
36
Connectance
0.046
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

148km

Max discharge

12,5m³/s

Max Strahler

3

Segments matched

29

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