Ontologia

Ruisseau· 11 segments

Seneca Creek

Crosses 4 administrative regions : Loudoun, Montgomery, Pendleton, Randolph

ruisseau

Total length

98km

Max discharge

5m³/s

Max Strahler

3

Segments matched

11

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080565050837 km²

4 administrative regions crossed (GADM L2)

  • Pendleton
    West Virginia · United States
    38.6 km
    in this dpt
  • Montgomery
    Maryland · United States
    9.9 km
    in this dpt
  • Loudoun
    Virginia · United States
    0.0 km
    in this dpt
  • Randolph
    West Virginia · United States
    0.0 km
    in this dpt

8 intersecting protected areas

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

Species present

138 distinct species · 698 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 36 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 Seneca Creek : 26 espèces reliées par 74 interactions GloBI sur 4 types (connectance 11.1%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
37
Interactions affichées
74
Connectance
0.111
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

98km

Max discharge

5,0m³/s

Max Strahler

3

Segments matched

11

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