Ontologia

Rivière· 4 segments

Whetstone Creek

Crosses 3 administrative regions : Ashtabula, Lewis, Osceola

rivière

Total length

221km

Max discharge

83,2m³/s

Max Strahler

5

Segments matched

4

River geography3 admin regions · 0 communes

Parent watershed

hybas-70804429501083 km²

3 administrative regions crossed (GADM L2)

  • Lewis
    New York · United States
    19.2 km
    in this dpt
  • Ashtabula
    Ohio · United States
    6.0 km
    in this dpt
  • Osceola
    Michigan · United States
    2.1 km
    in this dpt

5 intersecting protected areas

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

Species present

255 distinct species · 14 476 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 36 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 Whetstone Creek : 25 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 75 interactions GloBI sur 4 types (connectance 11.3%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
37
Interactions affichées
75
Connectance
0.113
Patrimoniales
1
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

221km

Max discharge

83,2m³/s

Max Strahler

5

Segments matched

4

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