Ontologia

Ruisseau· 15 segments

고막원천

Crosses 4 administrative regions : Gwangsan, Hampyeong, Jangseong, Naju

ruisseau

Total length

34km

Max discharge

4,1m³/s

Max Strahler

3

Segments matched

15

River geography4 admin regions · 0 communes

Parent watershed

hybas-4080615180226 km²

4 administrative regions crossed (GADM L2)

  • Hampyeong
    Jeollanam-do · South Korea
    23.1 km
    in this dpt
  • Naju
    Jeollanam-do · South Korea
    7.1 km
    in this dpt
  • Jangseong
    Jeollanam-do · South Korea
    1.3 km
    in this dpt
  • Gwangsan
    Gwangju · South Korea
    0.3 km
    in this dpt

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

Species present

280 distinct species · 651 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 45 interactions GloBI sur 3 types (connectance 10.3%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
30
Interactions affichées
45
Connectance
0.103
Patrimoniales
1
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

34km

Max discharge

4,1m³/s

Max Strahler

3

Segments matched

15

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