Ontologia

Ruisseau· 8 segments

Piasa Creek

Crosses 4 administrative regions : Jersey, Macoupin, Madison, Saint Charles

ruisseau

Total length

47km

Max discharge

2,3m³/s

Max Strahler

3

Segments matched

8

River geography4 admin regions · 0 communes

Parent watershed

hybas-70805696501629 km²

4 administrative regions crossed (GADM L2)

  • Jersey
    Illinois · United States
    22.9 km
    in this dpt
  • Madison
    Illinois · United States
    9.0 km
    in this dpt
  • Macoupin
    Illinois · United States
    3.1 km
    in this dpt
  • Saint Charles
    Missouri · United States
    0.0 km
    in this dpt

2 intersecting protected areas

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

Species present

107 distinct species · 168 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 45 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 Piasa Creek : 38 espèces reliées par 73 interactions GloBI sur 5 types (connectance 7.4%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
45
Interactions affichées
73
Connectance
0.074
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

47km

Max discharge

2,3m³/s

Max Strahler

3

Segments matched

8

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