Ontologia

Ruisseau· 10 segments

Brown Creek

Crosses 3 administrative regions : Anson, Richmond, Union

ruisseau

Total length

747km

Max discharge

5,6m³/s

Max Strahler

3

Segments matched

10

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080657520641 km²

3 administrative regions crossed (GADM L2)

  • Anson
    North Carolina · United States
    48.5 km
    in this dpt
  • Union
    North Carolina · United States
    5.2 km
    in this dpt
  • Richmond
    North Carolina · United States
    0.2 km
    in this dpt

1 intersecting protected areas

  • Pee Dee

    IUCN IV

    National Wildlife Refuge

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

Species present

733 distinct species · 2 018 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
35
Interactions affichées
58
Connectance
0.098
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

747km

Max discharge

5,6m³/s

Max Strahler

3

Segments matched

10

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