Ontologia

Rivière· 15 segments

갑천

Crosses 4 administrative regions : Daedeok, Nonsan, Seo, Yuseong

rivière

Total length

57km

Max discharge

13,9m³/s

Max Strahler

4

Segments matched

15

River geography4 admin regions · 0 communes

Parent watershed

hybas-4080568130646 km²

4 administrative regions crossed (GADM L2)

  • Seo
    Daejeon · South Korea
    18.8 km
    in this dpt
  • Nonsan
    Chungcheongnam-do · South Korea
    16.2 km
    in this dpt
  • Yuseong
    Daejeon · South Korea
    15.8 km
    in this dpt
  • Daedeok
    Daejeon · South Korea
    2.4 km
    in this dpt

9 intersecting protected areas

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

Species present

577 distinct species · 4 627 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 32 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 46 interactions GloBI sur 4 types (connectance 8.7%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
33
Interactions affichées
46
Connectance
0.087
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

57km

Max discharge

13,9m³/s

Max Strahler

4

Segments matched

15

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