Ontologia

Ruisseau· 13 segments

Hackers Creek

Crosses 4 administrative regions : Harrison, Lewis, Pope, Upshur

ruisseau

Total length

51km

Max discharge

3,2m³/s

Max Strahler

3

Segments matched

13

River geography4 admin regions · 0 communes

Parent watershed

hybas-70805541602306 km²

4 administrative regions crossed (GADM L2)

  • Lewis
    West Virginia · United States
    31.7 km
    in this dpt
  • Upshur
    West Virginia · United States
    8.5 km
    in this dpt
  • Pope
    Arkansas · United States
    6.0 km
    in this dpt
  • Harrison
    West Virginia · United States
    3.7 km
    in this dpt

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

Species present

41 distinct species · 90 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 21 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 Hackers Creek : 18 espèces reliées par 28 interactions GloBI sur 2 types (connectance 13.3%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
21
Interactions affichées
28
Connectance
0.133
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)

Total length

51km

Max discharge

3,2m³/s

Max Strahler

3

Segments matched

13

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