Ontologia

Ruisseau· 9 segments

可児川

Crosses 5 administrative regions : Kani, Minokamo, Mitake, Mizunami, Tajimi

ruisseau

Total length

24km

Max discharge

4,8m³/s

Max Strahler

3

Segments matched

9

River geography5 admin regions · 0 communes

Parent watershed

hybas-4080607140463 km²

5 administrative regions crossed (GADM L2)

  • Kani
    Gifu · Japan
    11.7 km
    in this dpt
  • Mitake
    Gifu · Japan
    10.1 km
    in this dpt
  • Mizunami
    Gifu · Japan
    0.3 km
    in this dpt
  • Minokamo
    Gifu · Japan
    0.0 km
    in this dpt
  • Tajimi
    Gifu · Japan
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

365 distinct species · 694 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 7 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 可児川 : 5 espèces reliées par 6 interactions GloBI sur 3 types (connectance 28.6%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
7
Interactions affichées
6
Connectance
0.286
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

24km

Max discharge

4,8m³/s

Max Strahler

3

Segments matched

9

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