Ontologia

Ruisseau· 21 segments

Plover River

Crosses 4 administrative regions : Langlade, Marathon, Portage, Shawano

ruisseau

Total length

103km

Max discharge

5,3m³/s

Max Strahler

2

Segments matched

21

River geography4 admin regions · 0 communes

Parent watershed

hybas-70804426104903 km²

4 administrative regions crossed (GADM L2)

  • Marathon
    Wisconsin · United States
    65.2 km
    in this dpt
  • Portage
    Wisconsin · United States
    41.2 km
    in this dpt
  • Langlade
    Wisconsin · United States
    1.5 km
    in this dpt
  • Shawano
    Wisconsin · United States
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

226 distinct species · 3 348 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 Plover River : 18 espèces reliées par 65 interactions GloBI sur 4 types (connectance 12.3%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
33
Interactions affichées
65
Connectance
0.123
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

103km

Max discharge

5,3m³/s

Max Strahler

2

Segments matched

21

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