Skip to content
Toronto Park Atlas
Lakeshore Boulevard Parklands — site photograph
Back to map
Corridor / Linear Parkcluster ·Walkable Mid-Rise Neighbourhood Parks (large-scale)confidence moderatereal Toronto data

Lakeshore Boulevard Parklands

Corridor / Linear Park, below average overall (score 28, rank ~23th percentile). Strongest: connectivity; weakest: enclosure.

Aerial — City of Toronto orthophoto, ~8 cm/px source · cached 5/9/2026

Lakeshore Boulevard Parklands scores 28.3 / 100. Strongest dimensions: connectivity and natural comfort. Weakest: edge activation (0). Border-vacuum risk is elevated (100). This score is a transparent reading of Jane Jacobs-style vitality factors — not a definitive judgment.

Best for:walking + cycling routeslinear social use

Area · 9.05 ha

Vitality Score
28/100

Weighted across six dimensions · confidence 72%

Data Confidence
28.3 / 100
Citywide
23rd
of all 3,273 parks
Among Corridor / Linear Park
30th
same primary typology
Expected for similar parks
35
median in large Corridor / Linear Park (n=19)
Performance gap
-7
raw − expected · context confidence medium
modest underperformer

Scores are not bell-curved. Percentiles and expected scores provide context without changing the underlying model.

Explain this score

Where did the 28 come from? Each weighted contribution against a neutral 50 baseline. Green = pushed up; red = pulled down.

Download JSON
What pushed this score up or down vs a neutral 50weight × score
Edge Activation0 · p38
-12.5
Amenity Diversity20 · p85
-6.0
Connectivity78 · p98
+5.6
Border Vacuum Risk100 (risk)
-5.0
Enclosure / Eyes on Park28 · p3
-2.2
Natural Comfort40 · p36
-1.5

Sum of contributions = the headline score. A negative bar means that dimension dragged the park below the city-wide neutral baseline.

Why this park works

Lakeshore Boulevard Parklands works because its connectivity score (78) is one of the city's strongest and its amenity diversity (20) is also top quartile (29 transit stops sit within a 400 m walk; 39 intersections fall within 100 m of the edge).

What limits this park

Lakeshore Boulevard Parklands is held back by enclosure (28, bottom quartile); border-vacuum risk is also elevated (100).

Most distinctive characteristic

Most distinctive feature: exceptionally high connectivity (78, top decile).

Jacobs reading

Lakeshore Boulevard Parklands is currently underperforming on both axes — neither integrated into the city nor offering deep natural respite. A candidate for design intervention.

Tradeoffs

  • Connectivity (78) significantly outpaces natural comfort (40) — well placed in the city but offers little shade or ecological respite.
  • High connectivity coexists with high border-vacuum risk (100) — much of that connectivity is to highways, rail, or parking lots, not to neighbourhoods.

Performance in context

  • Reads as a modest underperformer relative to comparable parks (gap -7; cohort: large Corridor / Linear Park).

Typology classification

confidence 75%
Corridor / Linear Parkalso reads as Waterfront Park

Classified as Corridor / Linear Park: shape elongation 4.8× a circle of equal area. Secondary read: Waterfront Park (nearest waterbody within ~0 m).

Edge Activation

25% weightpartial 60%
0.0 / 100

Within 100 m of the park edge: 4 active uses (transit_stop, restaurant) and 58 dead/hostile uses (highway, rail, parking_lot). Active edges keep "eyes on the park" through the day; parking lots, blank institutional walls, rail and highway frontages drain street life.

Source: OSM POIs (amenity/shop) + Toronto Building Footprints + land use

Connectivity

20% weightmeasured 85%
77.9 / 100

Connectivity blends paths, intersections, transit, entrances, and edge density. This park has 44 mapped paths/walkways and 83 sidewalk segments within 50 m; 39 street intersections within 100 m; 29 transit stops within a 400 m walk; 16 estimated access points across ~5,117 m of perimeter. moderate edge density — small superblock penalty applied. Source coverage: centreline, pedestrian_network, transit_osm.

Streets within 25 m34
Intersections within 100 m39
Paths/walkways (50 m)44
Sidewalk segments (50 m)83
Transit stops (400 m)29
Estimated entrances16
Edge connections / 100 m perimeter0.66
Park perimeter5,117 m

Source: Toronto Centreline V2 + Pedestrian Network + OSM transit stops

Amenity Diversity

20% weightmeasured 75%
19.9 / 100

2 distinct amenity types in the park (fitness, tennis). Diversity, not raw count, drives the score so a park with many distinct activity types can outrank a larger park that repeats the same use.

Source: Toronto Parks & Recreation Facilities + OSM amenity tags

Natural Comfort

15% weightmeasured 75%
39.7 / 100

Natural-comfort components for this park: ~6.0% effective canopy (1.0% from contiguous tree polygons + scattered tree density); 1.9% water surface; 77 city-mapped trees inside the polygon (8.5/ha). Reading: water-cooled. Source coverage: treed_area, waterbodies, street_trees. Impervious surface is approximated (Toronto's authoritative layer ships only as a raster GeoTIFF).

Canopy coverage1.0%
Canopy area0.09 ha
Inside ravine system0.0%
Water surface inside park1.9%
Nearest water (if outside park)0 m (inside)
Estimated green98.1%
City-mapped trees inside polygon77
Tree density8.5 / ha
Cover diversity (Shannon, 0–100)13.7
Sample points used103

Source: Toronto Treed Area + Ravine + Waterbodies + Street Tree Inventory

Enclosure / Eyes on Park

10% weightmeasured 80%
27.7 / 100

18 buildings within 25 m of the park edge (3 mid-rise, 15 low-rise, 0 tower); avg edge height 5.5 m (~2 floors); 0.4 buildings per 100 m of 5,117 m perimeter — thin frontage — significant blank-edge share; edges are barely there or single-storey; no towers immediately adjacent. "Eyes on the park" come strongest from the 3 mid-rise edge buildings.

Buildings within 25 m18
Buildings within 50 m18
Avg edge height5.5 m (~2 floors)
Tallest edge building11.9 m
Mid-rise (3–7 floors)3
Low-rise (< 3 floors)15
Towers (≥ 13 floors)0
Frontage density0.35 per 100 m perimeter
Mid-rise share of edge17%
Tower share of edge0%
Blank-edge share (proxy)88%
Park perimeter5,117 m

Source: Toronto 3D Massing (building footprints + heights)

Border Vacuum Risk

10% weightpartial 60%
100.0 risk

Border-vacuum factors within 50 m of the park: Lake Shore Boulevard West, Gardiner Expressway, Gardiner Expressway, Lake Shore Boulevard West, Gardiner Expressway, Gardiner Expressway, Gardiner Expressway, Gardiner Expressway, Oakville Subdivision, Lake Shore Boulevard West, Lake Shore Boulevard West, Lake Shore Boulevard West, Lake Shore Boulevard West, Lake Shore Boulevard West, Lake Shore Boulevard West, parking_lot, Lake Shore Boulevard West, Lake Shore Boulevard West, Palais Royale Guest Parking, Palais Royale Guest Parking, Lake Shore Boulevard West, Lake Shore Boulevard West, Lake Shore Boulevard West, Oakville Subdivision, Oakville Subdivision, Oakville Subdivision, Oakville Subdivision, Lake Shore Boulevard West, Lake Shore Boulevard West, Carpark 210, Lake Shore Boulevard West, Lake Shore Boulevard West, parking_lot, parking_lot, Lake Shore Boulevard West, Argonaut Rowing Club parking. Jacobs warned that highways, rail, parking lots and blank institutional edges act as "vacuums" — they suppress foot traffic and isolate the park from its neighbourhood.

Source: Toronto Street Centreline (highways) + rail layer + OSM landuse + building footprints

Equity Context

contextinferred 15%
50.0 / 100

Equity Context requires inputs not yet loaded for this park (Toronto Neighbourhood Profiles). Score is held at a neutral 50 with low confidence — read with caution.

Source: Toronto Neighbourhood Profiles

Amenities (2 types · 2 records)

  • fitness
  • tennis

Nearby active-edge features (80)

  • parking lot — Palais Royale Guest Parking0 m
  • parking lot — Palais Royale Guest Parking0 m
  • parking lot — Carpark 2100 m
  • parking lot0 m
  • parking lot — Argonaut Rowing Club parking0 m
  • highway — Lake Shore Boulevard West4 m
  • rail — Oakville Subdivision5 m
  • highway — Lake Shore Boulevard West6 m
  • restaurant7 m
  • highway — Lake Shore Boulevard West8 m
  • rail — Oakville Subdivision9 m
  • highway — Lake Shore Boulevard West9 m
  • rail — Oakville Subdivision13 m
  • parking lot13 m
  • highway — Lake Shore Boulevard West14 m
  • highway — Gardiner Expressway14 m
  • highway — Lake Shore Boulevard West14 m
  • highway — Lake Shore Boulevard West15 m
  • rail — Oakville Subdivision17 m
  • highway — Lake Shore Boulevard West18 m
  • highway — Lake Shore Boulevard West18 m
  • highway — Lake Shore Boulevard West18 m
  • highway — Lake Shore Boulevard West19 m
  • highway — Lake Shore Boulevard West24 m
  • highway — Lake Shore Boulevard West26 m
  • highway — Lake Shore Boulevard West26 m
  • highway — Lake Shore Boulevard West27 m
  • highway — Gardiner Expressway28 m
  • highway — Gardiner Expressway28 m
  • highway — Gardiner Expressway28 m
  • highway — Lake Shore Boulevard West32 m
  • highway — Gardiner Expressway38 m
  • parking lot39 m
  • highway — Gardiner Expressway41 m
  • restaurant — Fruit & Bean Co.42 m
  • highway — Lake Shore Boulevard West48 m
  • rail — Oakville Subdivision48 m
  • highway — Lake Shore Boulevard West48 m
  • transit stop — Lakeshore Blvd W at Colborne Lodge Dr51 m
  • highway — Lake Shore Boulevard West51 m
  • rail — Oakville Subdivision52 m
  • highway — Lake Shore Boulevard West53 m
  • highway — Gardiner Expressway55 m
  • parking lot56 m
  • rail — Oakville Subdivision56 m
  • rail — Oakville Subdivision60 m
  • rail — Oakville Subdivision60 m
  • rail — Oakville Subdivision63 m
  • rail — Oakville Subdivision64 m
  • rail — Oakville Subdivision67 m
  • rail — Oakville Subdivision68 m
  • rail — Oakville Subdivision71 m
  • rail — Oakville Subdivision72 m
  • rail — Oakville Subdivision75 m
  • highway — Gardiner Expressway75 m
  • highway — Lake Shore Boulevard West78 m
  • transit stop — Lakeshore Blvd W at Colborne Lodge Dr82 m
  • highway — Lake Shore Boulevard West85 m
  • highway — Lake Shore Boulevard West92 m
  • highway — Gardiner Expressway93 m
  • highway — Gardiner Expressway94 m
  • highway — Lake Shore Boulevard West96 m
  • highway — Gardiner Expressway111 m
  • parking lot113 m
  • transit stop — Glendale Avenue114 m
  • transit stop — Parkside Drive120 m
  • parking lot121 m
  • transit stop — Colborne Lodge Drive121 m
  • transit stop — Parkside Drive122 m
  • highway — Lake Shore Boulevard West125 m
  • highway — Lake Shore Boulevard West126 m
  • highway — Lake Shore Boulevard West127 m
  • highway — Lake Shore Boulevard West128 m
  • parking lot130 m
  • highway — Lake Shore Boulevard West130 m
  • transit stop — Glendale Avenue133 m
  • parking lot138 m
  • transit stop — Parkside Dr at The Queensway139 m
  • transit stop — 30 The Queensway (St. Joseph's Health Centre)140 m
  • transit stop — Queen Street West141 m

Park profile

Five-axis radar across the structural dimensions.

Edge ActivationConnectivityAmenity DiversityNatural ComfortEnclosureLakeshore Boulevard Parklands

Citywide percentile ranks

Across all Toronto parks in the dataset.

  • Overall vitality
    23th
  • Edge activation
    38th
  • Connectivity
    98th
  • Amenity diversity
    85th
  • Natural comfort
    36th
  • Enclosure
    3th

Most similar parks

Closest in metric space across the five structural dimensions.

Most opposite parks

Furthest in metric space — useful for recognising what kind of park this isn’t.

Human activity signals — not available

No activity signals have landed for this park yet. The model has scored its physical form but it can’t yet say how often it’s programmed, photographed, or walked through. See /data-ethics for what we will and will not collect.

Does this score feel accurate?

Your read of Lakeshore Boulevard Parklandsmatters. We’re testing whether the model lines up with how people actually use the park. Submissions are stored locally; no account needed.

Tell us how this park feels

We measure structure (canopy, edges, connectivity). You measure feeling. Both matter — and disagreement is itself useful civic data.

Rate this park on as many dimensions as you have an opinion about. 1 = not at all · 5 = strongly. Skip the ones you don't feel sure about. Aggregated only — no comments stored at the row level.

feels socially active
feels comfortable
feels safe
feels connected
feels welcoming
feels ecological / natural
feels good for lingering
feels family-friendly
feels culturally important

What would improve this park?

Generated from the weakest measured dimensions — a starting point, not a prescription.

  • Activate the edges: encourage cafés, retail or community uses on the streets that face the park; replace blank or parking-lot edges where possible.
  • Diversify what people can do in the park — playground, washroom, water, shade, performance, sport, garden — even small additions raise this score.
  • Increase canopy and reduce paved area. Shade and water features extend usable hours and seasons.
  • Encourage mid-rise, windowed frontages around the park so residents have direct sightlines onto it.
  • Mitigate border vacuums (highways, rail, parking) with active programming on the still-permeable edges and treat the hostile edge as a design challenge.

Data sources

  • City of Toronto Open Data — Parks (Green Space)
    Polygon boundaries, official names, types.
  • Parks & Recreation Facilities
    Inventory of in-park amenities (washrooms, fields, rinks…).
  • Toronto Pedestrian Network
    Sidewalk segments around and through parks; estimated park entrances.
  • Toronto Centreline V2
    Street segments + intersection nodes near park edges; trails and walkways.
  • Toronto 3D Massing
    Building footprints + heights for edge-building counts, frontage density, and tower-in-the-park risk.
  • Toronto Treed Area
    Tree canopy share inside park polygons via stratified-grid sampling.
  • Toronto Waterbodies & Rivers
    Water surface inside parks + nearest-water distance for cooling.
  • Ravine & Natural Feature Protection
    Ravine overlap as a cooling / natural-comfort signal.
  • Toronto Street Tree Inventory
    Tree count + density inside park polygons.
  • Neighbourhood Profiles
    (Pending) Equity context proxy.
  • OpenStreetMap (Overpass API)
    Cafés, restaurants, retail, transit stops, parking, highways, rail.