Ontologia

Ruisseau· 15 segments

Octoraro Creek

Crosses 4 administrative regions : Cecil, Chester, Harford, Lancaster

ruisseau

Total length

36km

Max discharge

9,4m³/s

Max Strahler

3

Segments matched

15

River geography4 admin regions · 0 communes

Parent watershed

hybas-70800410502365 km²

4 administrative regions crossed (GADM L2)

  • Cecil
    Maryland · United States
    24.4 km
    in this dpt
  • Lancaster
    Pennsylvania · United States
    11.1 km
    in this dpt
  • Chester
    Pennsylvania · United States
    9.9 km
    in this dpt
  • Harford
    Maryland · United States
    0.0 km
    in this dpt

8 intersecting protected areas

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

Species present

821 distinct species · 10 907 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Octoraro Creek : 30 espèces reliées par 114 interactions GloBI sur 5 types (connectance 11.5%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
45
Interactions affichées
114
Connectance
0.115
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

36km

Max discharge

9,4m³/s

Max Strahler

3

Segments matched

15

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