Rivière
Ringgraben
⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 6 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.
Crosses 2 administrative regions : Heidekreis, Verden
Max discharge
129,6m³/s
Max Strahler
6
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- HeidekreisNiedersachsen · Germany3.6 kmin this dpt
- VerdenNiedersachsen · Germany0.0 kmin this dpt
7 intersecting protected areas
Aller (mit Barnbruch), untere Leine, untere Oker
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Untere Allerniederung
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Aller-Leinetal
IUCN VLandscape Protection Area
Aller-Leinetal
IUCN IVNature Reserve
Nature Reserve
Nature Reserve
Nature Reserve
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
631 distinct species · 986 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 37 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).
Indicateurs du tissu écologique
Tissu écologique de Ringgraben : 27 espèces reliées par 96 interactions GloBI sur 7 types (connectance 13.0%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Matched len.
17,0km
Max discharge
129,6m³/s
Max Strahler
6
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.