Ontologia

Ruisseau· 4 segments

Sycamore Creek

Crosses 4 administrative regions : Blanco, Burnet, Hays, Kimble

ruisseau

Total length

822km

Max discharge

0,2m³/s

Max Strahler

2

Segments matched

4

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080751280928 km²

4 administrative regions crossed (GADM L2)

  • Burnet
    Texas · United States
    7.8 km
    in this dpt
  • Kimble
    Texas · United States
    5.3 km
    in this dpt
  • Hays
    Texas · United States
    3.2 km
    in this dpt
  • Blanco
    Texas · United States
    0.4 km
    in this dpt

1 intersecting protected areas

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

Species present

297 distinct species · 952 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
47
Interactions affichées
118
Connectance
0.109
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

822km

Max discharge

0,2m³/s

Max Strahler

2

Segments matched

4

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