Ontologia

Ruisseau· 2 segments

鈴川

Crosses 4 administrative regions : Atsugi, Hadano, Hiratsuka, Isehara

ruisseau

Total length

32km

Max discharge

1,1m³/s

Max Strahler

1

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-4080044940269 km²

4 administrative regions crossed (GADM L2)

  • Isehara
    Kanagawa · Japan
    18.7 km
    in this dpt
  • Hiratsuka
    Kanagawa · Japan
    3.7 km
    in this dpt
  • Atsugi
    Kanagawa · Japan
    0.0 km
    in this dpt
  • Hadano
    Kanagawa · Japan
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

1 036 distinct species · 3 783 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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 鈴川 : 26 espèces dont 3 patrimoniales (LR IUCN CR/EN/VU) reliées par 77 interactions GloBI sur 4 types (connectance 11.0%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
38
Interactions affichées
77
Connectance
0.110
Patrimoniales
3
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

32km

Max discharge

1,1m³/s

Max Strahler

1

Segments matched

2

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