Ontologia

Ruisseau· 22 segments

Deer Creek

Crosses 4 administrative regions : Baltimore, Clearfield, Harford, York

ruisseau

Total length

3 861km

Max discharge

7,1m³/s

Max Strahler

3

Segments matched

22

River geography4 admin regions · 0 communes

Parent watershed

hybas-70800410502365 km²

4 administrative regions crossed (GADM L2)

  • Harford
    Maryland · United States
    53.2 km
    in this dpt
  • York
    Pennsylvania · United States
    8.2 km
    in this dpt
  • Clearfield
    Pennsylvania · United States
    5.5 km
    in this dpt
  • Baltimore
    Maryland · United States
    1.3 km
    in this dpt

6 intersecting protected areas

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

Species present

174 distinct species · 1 223 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 Deer Creek : 28 espèces reliées par 117 interactions GloBI sur 4 types (connectance 11.8%, filtre Serrano α=0.2). 17 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

3 861km

Max discharge

7,1m³/s

Max Strahler

3

Segments matched

22

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