Ontologia

Ruisseau· 9 segments

Dragon Run

Crosses 4 administrative regions : Essex, Gloucester, King and Queen, Middlesex

ruisseau

Total length

64km

Max discharge

4,5m³/s

Max Strahler

3

Segments matched

9

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080041710438 km²

4 administrative regions crossed (GADM L2)

  • Middlesex
    Virginia · United States
    25.3 km
    in this dpt
  • King and Queen
    Virginia · United States
    19.0 km
    in this dpt
  • Essex
    Virginia · United States
    16.2 km
    in this dpt
  • Gloucester
    Virginia · United States
    3.8 km
    in this dpt

7 intersecting protected areas

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

Species present

356 distinct species · 3 041 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 47 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 Dragon Run : 35 espèces reliées par 112 interactions GloBI sur 4 types (connectance 9.5%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
49
Interactions affichées
112
Connectance
0.095
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

64km

Max discharge

4,5m³/s

Max Strahler

3

Segments matched

9

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