Ontologia

Ruisseau

軍川

Crosses 1 administrative regions : Nanae

ruisseau

Total length

11km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-40800388406362 km²

1 administrative regions crossed (GADM L2)

  • Nanae
    Hokkaido · Japan
    8.6 km
    in this dpt

4 intersecting protected areas

  • Onuma

    IUCN IV

    Prefectural Wildlife Protection Area

  • Onuma

    IUCN V

    Quasi National Park

  • Esan

    IUCN V

    Prefectural Natural Park

  • Onuma

    IUCN Not Reported

    Wetland of International Importance (Ramsar Site)

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

Species present

117 distinct species · 230 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 39 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 軍川 : 31 espèces reliées par 90 interactions GloBI sur 4 types (connectance 11.5%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
90
Connectance
0.115
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

11km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

1

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