Ontologia

Ruisseau· 2 segments

愛知用水

Crosses 5 administrative regions : Kasugai, Nagakute, Nagoya, Owariasahi, Seto

ruisseau

Total length

115km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

2

River geography5 admin regions · 0 communes

Parent watershed

hybas-40800453402185 km²

5 administrative regions crossed (GADM L2)

  • Nagakute
    Aichi · Japan
    5.0 km
    in this dpt
  • Nagoya
    Aichi · Japan
    3.9 km
    in this dpt
  • Kasugai
    Aichi · Japan
    1.9 km
    in this dpt
  • Owariasahi
    Aichi · Japan
    0.6 km
    in this dpt
  • Seto
    Aichi · Japan
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

383 distinct species · 1 852 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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 愛知用水 : 30 espèces reliées par 77 interactions GloBI sur 5 types (connectance 8.5%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
77
Connectance
0.085
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

115km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

2

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