Ontologia

Ruisseau· 3 segments

Lighthouse Creek

Crosses 4 administrative regions : Berrien, Haliburton, Hastings, Lake Michigan

ruisseau

Total length

49km

Max discharge

4,1m³/s

Max Strahler

3

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-70804913701111 km²

4 administrative regions crossed (GADM L2)

  • Berrien
    Michigan · United States
    5.2 km
    in this dpt
  • Hastings
    Ontario · Canada
    4.9 km
    in this dpt
  • Lake Michigan
    Michigan · United States
    1.4 km
    in this dpt
  • Haliburton
    Ontario · Canada
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

63 distinct species · 123 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 Lighthouse Creek : 31 espèces reliées par 46 interactions GloBI sur 3 types (connectance 7.3%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
36
Interactions affichées
46
Connectance
0.073
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

49km

Max discharge

4,1m³/s

Max Strahler

3

Segments matched

3

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