Ontologia

Rivière· 90 segments

Salt Fork Brazos River

Crosses 4 administrative regions : Crosby, Garza, Kent, Stonewall

rivière

Total length

295km

Max discharge

2,8m³/s

Max Strahler

5

Segments matched

90

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080697570655 km²

4 administrative regions crossed (GADM L2)

  • Stonewall
    Texas · United States
    136.9 km
    in this dpt
  • Kent
    Texas · United States
    134.8 km
    in this dpt
  • Garza
    Texas · United States
    79.3 km
    in this dpt
  • Crosby
    Texas · United States
    16.2 km
    in this dpt

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

Species present

95 distinct species · 213 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 32 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 Salt Fork Brazos River : 24 espèces reliées par 80 interactions GloBI sur 3 types (connectance 14.3%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
34
Interactions affichées
80
Connectance
0.143
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

295km

Max discharge

2,8m³/s

Max Strahler

5

Segments matched

90

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