Ontologia

Rivière· 27 segments

Canaseraga Creek

Crosses 4 administrative regions : Allegany, Livingston, Madison, Steuben

rivière

Total length

96km

Max discharge

13,2m³/s

Max Strahler

4

Segments matched

27

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080471330857 km²

4 administrative regions crossed (GADM L2)

  • Livingston
    New York · United States
    64.0 km
    in this dpt
  • Madison
    New York · United States
    21.9 km
    in this dpt
  • Allegany
    New York · United States
    19.0 km
    in this dpt
  • Steuben
    New York · United States
    5.0 km
    in this dpt

6 intersecting protected areas

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

Species present

470 distinct species · 41 063 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 37 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 Canaseraga Creek : 28 espèces reliées par 71 interactions GloBI sur 4 types (connectance 10.7%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
37
Interactions affichées
71
Connectance
0.107
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

96km

Max discharge

13,2m³/s

Max Strahler

4

Segments matched

27

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