Ontologia

Rivière· 16 segments

Sandy Creek

Crosses 4 administrative regions : Colorado, Jackson, Lavaca, Wharton

rivière

Total length

8 225km

Max discharge

14,9m³/s

Max Strahler

4

Segments matched

16

River geography4 admin regions · 0 communes

Parent watershed

hybas-70807699301250 km²

4 administrative regions crossed (GADM L2)

  • Jackson
    Texas · United States
    38.0 km
    in this dpt
  • Colorado
    Texas · United States
    34.3 km
    in this dpt
  • Wharton
    Texas · United States
    33.8 km
    in this dpt
  • Lavaca
    Texas · United States
    5.2 km
    in this dpt

1 intersecting protected areas

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

Species present

62 distinct species · 122 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

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

8 225km

Max discharge

14,9m³/s

Max Strahler

4

Segments matched

16

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