Ontologia

Ruisseau· 15 segments

Jumping Pound Creek

Crosses 2 administrative regions : Division No. 15, Division No. 6

ruisseau

Total length

72km

Max discharge

5m³/s

Max Strahler

3

Segments matched

15

River geography2 admin regions · 0 communes

Parent watershed

hybas-70802531301449 km²

2 administrative regions crossed (GADM L2)

4 intersecting protected areas

  • SALTS 063

    IUCN Not Applicable

    Conservation easement

  • SALTS 043

    IUCN Not Applicable

    Conservation easement

  • SALTS 064

    IUCN Not Applicable

    Conservation easement

  • SALTS 065

    IUCN Not Applicable

    Conservation easement

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

Species present

232 distinct species · 2 323 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Jumping Pound Creek : 21 espèces reliées par 82 interactions GloBI sur 4 types (connectance 14.6%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
34
Interactions affichées
82
Connectance
0.146
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

72km

Max discharge

5,0m³/s

Max Strahler

3

Segments matched

15

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