Ontologia

Ruisseau· 12 segments

Oswego River

Crosses 2 administrative regions : Burlington, Ocean

ruisseau

Total length

79km

Max discharge

2,8m³/s

Max Strahler

2

Segments matched

12

River geography2 admin regions · 0 communes

Parent watershed

hybas-70800401601481 km²

2 administrative regions crossed (GADM L2)

  • Burlington
    New Jersey · United States
    25.6 km
    in this dpt
  • Ocean
    New Jersey · United States
    11.9 km
    in this dpt

11 intersecting protected areas

2 more protected areas
  • Ex

    IUCN V

    Federal Aviation Administration

  • Barnegat

    IUCN V

    Preserve

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

Species present

587 distinct species · 2 663 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 49 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 Oswego River : 32 espèces reliées par 137 interactions GloBI sur 5 types (connectance 11.6%, filtre Serrano α=0.2). 17 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
49
Interactions affichées
137
Connectance
0.117
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

79km

Max discharge

2,8m³/s

Max Strahler

2

Segments matched

12

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