Ontologia

Rivière· 5 segments

Contre-Canal

Crosses 2 administrative regions : Gard, Vaucluse

rivière

Total length

81km

Max discharge

37,3m³/s

Max Strahler

4

Segments matched

5

River geography2 admin regions · 20 communes

Parent watershed

hybas-2080571240266 km²

2 administrative regions crossed (GADM L2)

  • Gard
    Occitanie · France
    26.8 km
    in this dpt
  • Vaucluse
    Provence-Alpes-Côte d'Azur · France
    0.7 km
    in this dpt
20 communes (L5)

1 intersecting protected areas

  • Le Rhône aval

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

1 496 distinct species · 11 451 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 39 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 Contre-Canal : 33 espèces + 6 bulles famille, 59 interactions GloBI documentées sur 5 types (connectance 8.0%, filtre Serrano α=0.2). Les 6 bulles regroupent des espèces visuellement absorbées par famille (≥3 espèces visibles).

Espèces affichées
39
Interactions affichées
59
Connectance
0.080
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

81km

Max discharge

37,3m³/s

Max Strahler

4

Segments matched

5

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