Ontologia

Ruisseau· 6 segments

장선천

Crosses 3 administrative regions : Jinan, Nonsan, Wanju

ruisseau

Total length

18km

Max discharge

2,7m³/s

Max Strahler

3

Segments matched

6

River geography3 admin regions · 0 communes

Parent watershed

hybas-4080577520675 km²

3 administrative regions crossed (GADM L2)

  • Wanju
    Jeollabuk-do · South Korea
    18.1 km
    in this dpt
  • Nonsan
    Chungcheongnam-do · South Korea
    1.4 km
    in this dpt
  • Jinan
    Jeollabuk-do · South Korea
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

789 distinct species · 1 531 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 장선천 : 30 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 108 interactions GloBI sur 6 types (connectance 12.0%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
108
Connectance
0.120
Patrimoniales
2
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

18km

Max discharge

2,7m³/s

Max Strahler

3

Segments matched

6

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