Ontologia

Rivière

Lock 30 - Lovesick

⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 5 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.

Crosses 1 administrative regions : Peterborough

rivière

Max discharge

83,5m³/s

Max Strahler

5

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-708042582096 km²

1 administrative regions crossed (GADM L2)

  • Peterborough
    Ontario · Canada
    9.3 km
    in this dpt

2 intersecting protected areas

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

Species present

1 327 distinct species · 14 098 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Lock 30 - Lovesick : 27 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 102 interactions GloBI sur 4 types (connectance 13.1%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
102
Connectance
0.131
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)

Matched len.

0,0km

Max discharge

83,5m³/s

Max Strahler

5

Segments matched

1

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