Ontologia

Ruisseau

万才川

Crosses 1 administrative regions : Yasugi

ruisseau

Total length

5km

Max discharge

5,3m³/s

Max Strahler

3

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-40800423702044 km²

1 administrative regions crossed (GADM L2)

  • Yasugi
    Shimane · Japan
    4.9 km
    in this dpt

3 intersecting protected areas

  • Nakaumi

    IUCN IV

    National Wildlife Protection Area

  • Nakaumi

    IUCN Not Reported

    Wetland of International Importance (Ramsar Site)

  • Shanichi

    IUCN IV

    Prefectural Wildlife Protection Area

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

Species present

205 distinct species · 1 381 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 21 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 万才川 : 11 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 73 interactions GloBI sur 2 types (connectance 28.9%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
23
Interactions affichées
73
Connectance
0.288
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

5km

Max discharge

5,3m³/s

Max Strahler

3

Segments matched

1

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