Ontologia

Ruisseau· 6 segments

Mineral Creek

Crosses 4 administrative regions : Buncombe, Henry, Jackson, Jones

ruisseau

Total length

364km

Max discharge

1,1m³/s

Max Strahler

2

Segments matched

6

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080503510335 km²

4 administrative regions crossed (GADM L2)

  • Jones
    Iowa · United States
    25.0 km
    in this dpt
  • Henry
    Illinois · United States
    14.7 km
    in this dpt
  • Jackson
    Iowa · United States
    4.1 km
    in this dpt
  • Buncombe
    North Carolina · United States
    2.7 km
    in this dpt

2 intersecting protected areas

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

Species present

974 distinct species · 11 479 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 43 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 Mineral Creek : 33 espèces reliées par 98 interactions GloBI sur 4 types (connectance 10.9%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
98
Connectance
0.108
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

364km

Max discharge

1,1m³/s

Max Strahler

2

Segments matched

6

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