Ruisseau· 3 segments
Podunk River
Crosses 1 administrative regions : Hartford
Total length
28km
Max discharge
0,9m³/s
Max Strahler
2
Segments matched
3
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- HartfordConnecticut · United States11.4 kmin this dpt
15 intersecting protected areas
Windsor Meadows
IUCN IIIState Park
Open Space
Private Conservation
Private Conservation
Five Acre Meadow
IUCN VPrivate Conservation
Chapel Hill
IUCN VOpen Space
Town of Windsor 2
IUCN Not AssignedLocal Other or Unknown
Private Conservation
Shad Run Vacant Land
IUCN VLocal Conservation Area
6 more protected areassorted by area
Pleasant Valley Estates
IUCN VOpen Space
Private Conservation
Woodland Park
IUCN VOpen Space
Community Hall (Former)
IUCN VLocal Conservation Area
Ayers Road Parcel
IUCN VLocal Conservation Area
Pleasant Valley, R.O.W.
IUCN VLocal Conservation Area
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
1 225 distinct species · 23 656 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 46 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 Podunk River : 34 espèces reliées par 105 interactions GloBI sur 4 types (connectance 10.1%, filtre Serrano α=0.2). 12 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
28km
Max discharge
0,9m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.