Ontologia

Ruisseau· 16 segments

Honeoye Creek

Crosses 3 administrative regions : Livingston, Monroe, Ontario

ruisseau

Total length

86km

Max discharge

10,3m³/s

Max Strahler

3

Segments matched

16

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080466090710 km²

3 administrative regions crossed (GADM L2)

  • Monroe
    New York · United States
    31.1 km
    in this dpt
  • Ontario
    New York · United States
    27.4 km
    in this dpt
  • Livingston
    New York · United States
    2.1 km
    in this dpt

3 intersecting protected areas

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

Species present

234 distinct species · 1 351 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
50
Interactions affichées
128
Connectance
0.104
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

86km

Max discharge

10,3m³/s

Max Strahler

3

Segments matched

16

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