Ontologia

Ruisseau· 11 segments

Sand Fork

Crosses 4 administrative regions : Gallia, Gilmer, Lawrence, Lewis

ruisseau

Total length

48km

Max discharge

3,5m³/s

Max Strahler

3

Segments matched

11

River geography4 admin regions · 0 communes

Parent watershed

hybas-70805664601031 km²

4 administrative regions crossed (GADM L2)

  • Gallia
    Ohio · United States
    18.3 km
    in this dpt
  • Gilmer
    West Virginia · United States
    16.8 km
    in this dpt
  • Lewis
    West Virginia · United States
    4.2 km
    in this dpt
  • Lawrence
    Ohio · United States
    2.5 km
    in this dpt

1 intersecting protected areas

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

Species present

34 distinct species · 47 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 13 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 Sand Fork : 11 espèces reliées par 10 interactions GloBI sur 2 types (connectance 12.8%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
13
Interactions affichées
10
Connectance
0.128
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

48km

Max discharge

3,5m³/s

Max Strahler

3

Segments matched

11

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