Ontologia

Ruisseau· 11 segments

栗山川

Crosses 5 administrative regions : Katori, Sanmu, Sōsa, Tako, Yokoshibahikari

ruisseau

Total length

47km

Max discharge

5,5m³/s

Max Strahler

3

Segments matched

11

River geography5 admin regions · 0 communes

Parent watershed

hybas-4080044580262 km²

5 administrative regions crossed (GADM L2)

  • Yokoshibahikari
    Chiba · Japan
    17.0 km
    in this dpt
  • Tako
    Chiba · Japan
    11.0 km
    in this dpt
  • Katori
    Chiba · Japan
    5.2 km
    in this dpt
  • Sōsa
    Chiba · Japan
    0.3 km
    in this dpt
  • Sanmu
    Chiba · Japan
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

524 distinct species · 1 509 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 栗山川 : 20 espèces reliées par 42 interactions GloBI sur 4 types (connectance 12.0%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

47km

Max discharge

5,5m³/s

Max Strahler

3

Segments matched

11

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