Ontologia

Ruisseau

Loomattbach

Crosses 3 administrative regions : Affoltern, Dietikon, Zürich

ruisseau

Total length

1km

Max discharge

0,8m³/s

Max Strahler

1

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-20804954302407 km²

3 administrative regions crossed (GADM L2)

  • Affoltern
    Zürich · Switzerland
    9.2 km
    in this dpt
  • Dietikon
    Zürich · Switzerland
    2.2 km
    in this dpt
  • Zürich
    Zürich · Switzerland
    0.0 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

2 597 distinct species · 51 768 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 32 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 Loomattbach : 20 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 136 interactions GloBI sur 6 types (connectance 22.9%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
136
Connectance
0.229
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)

Total length

1km

Max discharge

0,8m³/s

Max Strahler

1

Segments matched

1

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