Ontologia

Rivière· 5 segments

Cane Creek

Crosses 4 administrative regions : Caswell, Danville, Person, Pittsylvania

rivière

Total length

1 007km

Max discharge

81,8m³/s

Max Strahler

5

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-70806199402831 km²

4 administrative regions crossed (GADM L2)

  • Pittsylvania
    Virginia · United States
    8.4 km
    in this dpt
  • Person
    North Carolina · United States
    4.5 km
    in this dpt
  • Danville
    Virginia · United States
    1.7 km
    in this dpt
  • Caswell
    North Carolina · United States
    1.5 km
    in this dpt

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

Species present

248 distinct species · 6 577 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 39 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 Cane Creek : 27 espèces reliées par 93 interactions GloBI sur 4 types (connectance 12.6%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
93
Connectance
0.126
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

1 007km

Max discharge

81,8m³/s

Max Strahler

5

Segments matched

5

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