Ontologia

Rivière· 15 segments

L'Armance

Crosses 3 administrative regions : Aube, Nièvre, Yonne

rivière

Total length

69km

Max discharge

22,7m³/s

Max Strahler

4

Segments matched

15

River geography3 admin regions · 37 communes

Parent watershed

hybas-2080481940606 km²

3 administrative regions crossed (GADM L2)

  • Aube
    Grand Est · France
    34.9 km
    in this dpt
  • Nièvre
    Bourgogne-Franche-Comté · France
    20.1 km
    in this dpt
  • Yonne
    Bourgogne-Franche-Comté · France
    13.7 km
    in this dpt
37 communes (L5)

2 intersecting protected areas

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

Species present

564 distinct species · 3 299 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 L'Armance : 29 espèces + 3 bulles famille, 56 interactions GloBI documentées sur 3 types (connectance 11.3%, filtre Serrano α=0.2). Les 3 bulles regroupent des espèces visuellement absorbées par famille (≥3 espèces visibles).

Espèces affichées
32
Interactions affichées
56
Connectance
0.113
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

69km

Max discharge

22,7m³/s

Max Strahler

4

Segments matched

15

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