Ruisseau· 8 segments
Beaver Creek
Crosses 8 administrative regions : Carbon, Chester, Delaware, Gloucester, Luzerne +3
Total length
7 489km
Max discharge
0,9m³/s
Max Strahler
2
Segments matched
8
River geography8 admin regions · 0 communes
8 administrative regions crossed (GADM L2)
- SchuylkillPennsylvania · United States9.6 kmin this dpt
- CarbonPennsylvania · United States8.9 kmin this dpt
- ChesterPennsylvania · United States8.9 kmin this dpt
- SalemNew Jersey · United States3.0 kmin this dpt
- New CastleDelaware · United States1.8 kmin this dpt
- DelawarePennsylvania · United States0.0 kmin this dpt
- LuzernePennsylvania · United States0.0 kmin this dpt
- GloucesterNew Jersey · United States0.0 kmin this dpt
3 intersecting protected areas
Brandywine Conservancy
IUCN Not AssignedEasement
Private Conservation
Brandywine Conservancy
IUCN Not AssignedEasement
1 page = 1 named river (aggregation of 8 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
849 distinct species · 11 675 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 41 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 Beaver Creek : 22 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 142 interactions GloBI sur 4 types (connectance 16.5%, filtre Serrano α=0.2). 20 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
7 489km
Max discharge
0,9m³/s
Max Strahler
2
Segments matched
8
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.