Ontologia

Rivière

Loving Creek

⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 6 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.

Crosses 1 administrative regions : Palo Pinto

rivière

Max discharge

22m³/s

Max Strahler

6

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-7080704890750 km²

1 administrative regions crossed (GADM L2)

  • Palo Pinto
    Texas · United States
    13.5 km
    in this dpt

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

Species present

352 distinct species · 1 845 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
40
Interactions affichées
113
Connectance
0.145
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)

Matched len.

13,5km

Max discharge

22,0m³/s

Max Strahler

6

Segments matched

1

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