Ontologia

Rivière· 11 segments

Roaring Creek

Crosses 3 administrative regions : Columbia, Montour, Northumberland

rivière

Total length

397km

Max discharge

474,9m³/s

Max Strahler

6

Segments matched

11

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080519280946 km²

3 administrative regions crossed (GADM L2)

  • Columbia
    Pennsylvania · United States
    24.9 km
    in this dpt
  • Montour
    Pennsylvania · United States
    2.8 km
    in this dpt
  • Northumberland
    Pennsylvania · United States
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

181 distinct species · 10 811 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 39 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 Roaring Creek : 25 espèces reliées par 88 interactions GloBI sur 4 types (connectance 11.9%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
88
Connectance
0.119
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

397km

Max discharge

474,9m³/s

Max Strahler

6

Segments matched

11

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