Ontologia

Rivière· 19 segments

Choptank River

Crosses 3 administrative regions : Caroline, Kent, Talbot

rivière

Total length

137km

Max discharge

23,1m³/s

Max Strahler

4

Segments matched

19

River geography3 admin regions · 0 communes

Parent watershed

hybas-70800409001215 km²

3 administrative regions crossed (GADM L2)

  • Caroline
    Maryland · United States
    49.1 km
    in this dpt
  • Talbot
    Maryland · United States
    3.8 km
    in this dpt
  • Kent
    Delaware · United States
    0.9 km
    in this dpt

7 intersecting protected areas

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

Species present

481 distinct species · 5 999 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Choptank River : 30 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 111 interactions GloBI sur 5 types (connectance 12.3%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
111
Connectance
0.123
Patrimoniales
1
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

137km

Max discharge

23,1m³/s

Max Strahler

4

Segments matched

19

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