Ontologia

Ruisseau· 12 segments

Sycamore Creek

Crosses 4 administrative regions : Crawford, Ingham, Seneca, Wyandot

ruisseau

Total length

822km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

12

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080514160312 km²

4 administrative regions crossed (GADM L2)

  • Crawford
    Ohio · United States
    27.2 km
    in this dpt
  • Ingham
    Michigan · United States
    23.4 km
    in this dpt
  • Wyandot
    Ohio · United States
    12.2 km
    in this dpt
  • Seneca
    Ohio · United States
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

728 distinct species · 11 824 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Sycamore Creek : 30 espèces reliées par 92 interactions GloBI sur 5 types (connectance 10.2%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
92
Connectance
0.102
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

822km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

12

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