Ontologia

Fleuve

Boire du Cellier

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

Crosses 2 administrative regions : Loire-Atlantique, Maine-et-Loire

fleuve

Max discharge

953,3m³/s

Max Strahler

7

Segments matched

1

River geography2 admin regions · 6 communes

Parent watershed

hybas-20805031202003 km²

2 administrative regions crossed (GADM L2)

6 communes (L5)

2 intersecting protected areas

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

Species present

1 449 distinct species · 12 222 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 37 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 Boire du Cellier : 32 espèces + 5 bulles famille, 88 interactions GloBI documentées sur 4 types (connectance 13.2%, filtre Serrano α=0.2). Les 5 bulles regroupent des espèces visuellement absorbées par famille (≥3 espèces visibles).

Espèces affichées
37
Interactions affichées
88
Connectance
0.132
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.

3,4km

Max discharge

953,3m³/s

Max Strahler

7

Segments matched

1

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