Ontologia

Rivière· 6 segments

Palmer Creek

Crosses 4 administrative regions : Butler, Chippewa, Haywood, Yellow Medicine

rivière

Total length

335km

Max discharge

69,6m³/s

Max Strahler

6

Segments matched

6

River geography4 admin regions · 0 communes

Parent watershed

hybas-70804744801412 km²

4 administrative regions crossed (GADM L2)

  • Chippewa
    Minnesota · United States
    16.9 km
    in this dpt
  • Haywood
    North Carolina · United States
    3.8 km
    in this dpt
  • Butler
    Iowa · United States
    2.4 km
    in this dpt
  • Yellow Medicine
    Minnesota · United States
    1.7 km
    in this dpt

5 intersecting protected areas

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

Species present

106 distinct species · 514 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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 Palmer Creek : 32 espèces reliées par 95 interactions GloBI sur 4 types (connectance 11.6%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
95
Connectance
0.116
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

335km

Max discharge

69,6m³/s

Max Strahler

6

Segments matched

6

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