Ontologia

Ruisseau

枝谷

Crosses 1 administrative regions : Hakusan

ruisseau

Total length

6km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-4080042680741 km²

1 administrative regions crossed (GADM L2)

  • Hakusan
    Ishikawa · Japan
    1.2 km
    in this dpt

4 intersecting protected areas

  • Mount Hakusan

    IUCN Not Applicable

    UNESCO-MAB Biosphere Reserve

  • Hakusan

    IUCN II

    National Park

  • Hakusan

    IUCN IV

    National Wildlife Protection Area

  • Hakusan

    IUCN Ib

    Forest Ecosystem Reserve

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

Species present

169 distinct species · 255 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 27 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 枝谷 : 23 espèces reliées par 25 interactions GloBI sur 5 types (connectance 7.1%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
27
Interactions affichées
25
Connectance
0.071
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

6km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

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