Ontologia

Ruisseau· 16 segments

飯梨川

Crosses 1 administrative regions : Yasugi

ruisseau

Total length

43km

Max discharge

8,6m³/s

Max Strahler

3

Segments matched

16

River geography1 admin regions · 0 communes

Parent watershed

hybas-40800423702044 km²

1 administrative regions crossed (GADM L2)

  • Yasugi
    Shimane · Japan
    32.1 km
    in this dpt

5 intersecting protected areas

  • Nakaumi

    IUCN IV

    National Wildlife Protection Area

  • Nakaumi

    IUCN Not Reported

    Wetland of International Importance (Ramsar Site)

  • Kiyomizu gassan

    IUCN V

    Prefectural Natural Park

  • Fube dam

    IUCN IV

    Prefectural Wildlife Protection Area

  • Gassan

    IUCN IV

    Prefectural Wildlife Protection Area

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

Species present

61 distinct species · 86 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 2 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 飯梨川 : 2 espèces reliées par 1 interaction GloBI sur 1 type (connectance 100.0%, filtre Serrano α=0.2).

Espèces affichées
2
Interactions affichées
1
Connectance
1.000
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

43km

Max discharge

8,6m³/s

Max Strahler

3

Segments matched

16

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