Ontologia

Ruisseau· 4 segments

Perch River

Crosses 5 administrative regions : Baraga, Houghton, Iron, Jefferson, Lake Ontario

ruisseau

Total length

134km

Max discharge

5,2m³/s

Max Strahler

3

Segments matched

4

River geography5 admin regions · 0 communes

Parent watershed

hybas-70804417701308 km²

5 administrative regions crossed (GADM L2)

  • Jefferson
    New York · United States
    24.7 km
    in this dpt
  • Baraga
    Michigan · United States
    20.6 km
    in this dpt
  • Iron
    Michigan · United States
    2.5 km
    in this dpt
  • Lake Ontario
    New York · United States
    0.7 km
    in this dpt
  • Houghton
    Michigan · United States
    0.0 km
    in this dpt

7 intersecting protected areas

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

Species present

5 distinct species · 5 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 3 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 Perch River : 3 espèces reliées par 2 interactions GloBI sur 1 type (connectance 66.7%, filtre Serrano α=0.2).

Espèces affichées
3
Interactions affichées
2
Connectance
0.667
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

134km

Max discharge

5,2m³/s

Max Strahler

3

Segments matched

4

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