Ruisseau· 16 segments
Big Laurel Creek
Crosses 10 administrative regions : Ashe, Floyd, Harlan, Johnson, Madison +5
Total length
141km
Max discharge
7,1m³/s
Max Strahler
3
Segments matched
16
River geography10 admin regions · 0 communes
10 administrative regions crossed (GADM L2)
- MadisonNorth Carolina · United States29.2 kmin this dpt
- AsheNorth Carolina · United States10.5 kmin this dpt
- HarlanKentucky · United States8.5 kmin this dpt
- PulaskiVirginia · United States6.1 kmin this dpt
- WebsterWest Virginia · United States4.4 kmin this dpt
- PocahontasWest Virginia · United States4.2 kmin this dpt
- MontgomeryVirginia · United States0.8 kmin this dpt
- FloydVirginia · United States0.0 kmin this dpt
- NicholasWest Virginia · United States0.0 kmin this dpt
- JohnsonTennessee · United States0.0 kmin this dpt
3 intersecting protected areas
1 page = 1 named river (aggregation of 16 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
241 distinct species · 2 648 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 40 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).
Indicateurs du tissu écologique
Tissu écologique de Big Laurel Creek : 30 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 89 interactions GloBI sur 4 types (connectance 11.4%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
141km
Max discharge
7,1m³/s
Max Strahler
3
Segments matched
16
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.