Ontologia

Ruisseau

神明沢 (Jinmyousawa)

Crosses 5 administrative regions : Akiruno, Fussa, Hamura, Okutama, Ōme

ruisseau

Total length

0km

Max discharge

11,5m³/s

Max Strahler

3

Segments matched

1

River geography5 admin regions · 0 communes

Parent watershed

hybas-40800448601253 km²

5 administrative regions crossed (GADM L2)

  • Ōme
    Tokyo · Japan
    16.2 km
    in this dpt
  • Okutama
    Tokyo · Japan
    1.9 km
    in this dpt
  • Akiruno
    Tokyo · Japan
    1.6 km
    in this dpt
  • Hamura
    Tokyo · Japan
    1.1 km
    in this dpt
  • Fussa
    Tokyo · Japan
    0.0 km
    in this dpt

7 intersecting protected areas

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

Species present

507 distinct species · 1 486 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 神明沢 (Jinmyousawa) : 40 espèces reliées par 47 interactions GloBI sur 5 types (connectance 4.7%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
45
Interactions affichées
47
Connectance
0.048
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

0km

Max discharge

11,5m³/s

Max Strahler

3

Segments matched

1

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