Ontologia

Ruisseau

김포대수로

Crosses 4 administrative regions : Gimpo, Goyang, Gyeyang, Seo

ruisseau

Total length

23km

Max discharge

0,6m³/s

Max Strahler

1

Segments matched

1

River geography4 admin regions · 0 communes

Parent watershed

hybas-40800049202549 km²

4 administrative regions crossed (GADM L2)

  • Gimpo
    Gyeonggi-do · South Korea
    6.1 km
    in this dpt
  • Gyeyang
    Incheon · South Korea
    0.5 km
    in this dpt
  • Seo
    Incheon · South Korea
    0.4 km
    in this dpt
  • Goyang
    Gyeonggi-do · South Korea
    0.0 km
    in this dpt

2 intersecting protected areas

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

Species present

173 distinct species · 424 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 김포대수로 : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 51 interactions GloBI sur 5 types (connectance 10.3%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
32
Interactions affichées
51
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

23km

Max discharge

0,6m³/s

Max Strahler

1

Segments matched

1

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