Ontologia

Rivière· 3 segments

丸子川

Crosses 2 administrative regions : Daisen, Misato

rivière

Total length

36km

Max discharge

10,9m³/s

Max Strahler

4

Segments matched

3

River geography2 admin regions · 0 communes

Parent watershed

hybas-40804738502215 km²

2 administrative regions crossed (GADM L2)

  • Misato
    Akita · Japan
    9.0 km
    in this dpt
  • Daisen
    Akita · Japan
    7.3 km
    in this dpt

3 intersecting protected areas

  • Himekami

    IUCN IV

    Prefectural Wildlife Protection Area

  • Hotokezawa

    IUCN IV

    Prefectural Wildlife Protection Area

  • Hotta

    IUCN IV

    Prefectural Wildlife Protection Area

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

Species present

162 distinct species · 252 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 18 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 丸子川 : 15 espèces reliées par 17 interactions GloBI sur 4 types (connectance 11.1%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
18
Interactions affichées
17
Connectance
0.111
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

36km

Max discharge

10,9m³/s

Max Strahler

4

Segments matched

3

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