Ontologia

Ruisseau· 2 segments

Nordgraben

Crosses 4 administrative regions : Berlin, Cottbus, Oberhavel, Spree-Neiße

ruisseau

Total length

33km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080363370388 km²

4 administrative regions crossed (GADM L2)

  • Berlin
    Berlin · Germany
    10.9 km
    in this dpt
  • Spree-Neiße
    Brandenburg · Germany
    3.3 km
    in this dpt
  • Oberhavel
    Brandenburg · Germany
    2.0 km
    in this dpt
  • Cottbus
    Brandenburg · Germany
    0.2 km
    in this dpt

21 intersecting protected areas

12 more protected areas

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

Species present

3 109 distinct species · 99 684 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 47 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 Nordgraben : 27 espèces reliées par 165 interactions GloBI sur 6 types (connectance 13.5%, filtre Serrano α=0.2). 23 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

33km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

2

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