Ontologia

Rivière· 47 segments

Nepisiguit River

Crosses 2 administrative regions : Gloucester, Northumberland

rivière

Total length

133km

Max discharge

48,9m³/s

Max Strahler

4

Segments matched

47

River geography2 admin regions · 0 communes

Parent watershed

hybas-70800356602284 km²

2 administrative regions crossed (GADM L2)

13 intersecting protected areas

4 more protected areas
  • 4022200

    IUCN II

    Nature Legacy protected area

  • 4021800

    IUCN II

    Nature Legacy protected area

  • 4022000

    IUCN II

    Nature Legacy protected area

  • 4010301

    IUCN II

    Nature Legacy protected area

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

Species present

45 distinct species · 64 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 21 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 Nepisiguit River : 17 espèces reliées par 22 interactions GloBI sur 3 types (connectance 10.5%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
21
Interactions affichées
22
Connectance
0.105
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

133km

Max discharge

48,9m³/s

Max Strahler

4

Segments matched

47

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