Ontologia

Ruisseau· 4 segments

Havelkanal

Crosses 3 administrative regions : Havelland, Potsdam, Potsdam-Mittelmark

ruisseau

Total length

35km

Max discharge

0,3m³/s

Max Strahler

2

Segments matched

4

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080367250411 km²

3 administrative regions crossed (GADM L2)

  • Havelland
    Brandenburg · Germany
    13.7 km
    in this dpt
  • Potsdam
    Brandenburg · Germany
    8.3 km
    in this dpt
  • Potsdam-Mittelmark
    Brandenburg · Germany
    0.0 km
    in this dpt

12 intersecting protected areas

3 more protected areas

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

Species present

852 distinct species · 3 083 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 Havelkanal : 18 espèces reliées par 116 interactions GloBI sur 6 types (connectance 26.7%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
30
Interactions affichées
116
Connectance
0.267
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

35km

Max discharge

0,3m³/s

Max Strahler

2

Segments matched

4

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