Elijah Park
Corridor / Linear Park, one of the city's strongest overall (score 50, rank ~96th percentile). Strongest: edge activation; weakest: natural comfort.
Photo by Zale Tabakman via Google Places · cached 5/9/2026
Elijah Park scores 50.4 / 100. Strongest dimensions: enclosure / eyes on park and connectivity. Weakest: amenity diversity (11.9). Border-vacuum risk is low. This score is a transparent reading of Jane Jacobs-style vitality factors — not a definitive judgment.
Area · 0.72 ha
Weighted across six dimensions · confidence 70%
Scores are not bell-curved. Percentiles and expected scores provide context without changing the underlying model.
Street context
Park polygon highlighted on the citywide map. Connectivity, transit, and edge conditions read at a glance.
Top-down view
City of Toronto orthophoto, ~8 cm/px. Reads the park’s footprint, paths, treed area, and edge conditions from above.
City of Toronto Orthophoto · cot_ortho most-current MapServer
Explain this score
Where did the 50 come from? Each weighted contribution against a neutral 50 baseline. Green = pushed up; red = pulled down.
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
What limits this park
Most distinctive characteristic
Jacobs reading
Performance in context
- This park is a strong overperformer for its cohort — raw 50 versus an expected 32 for similar parks (small Corridor / Linear Park) (gap +18).
Typology classification
Classified as Corridor / Linear Park: shape elongation 2.0× a circle of equal area
Edge Activation
Within 100 m of the park edge: 6 active uses (transit_stop) and 0 dead/hostile uses (none). 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
Connectivity blends paths, intersections, transit, entrances, and edge density. This park has 11 mapped paths/walkways and 2 sidewalk segments within 50 m; 5 street intersections within 100 m; 26 transit stops within a 400 m walk; 2 estimated access points across ~602 m of perimeter. moderate edge density — small superblock penalty applied. Source coverage: centreline, pedestrian_network, transit_osm.
Source: Toronto Centreline V2 + Pedestrian Network + OSM transit stops
Amenity Diversity
1 distinct amenity types in the park (playground). 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
Natural-comfort components for this park: 10.0% estimated tree canopy; 1 city-mapped trees inside the polygon (1.0/ha). Reading: exposed. Source coverage: treed_area, street_trees. Impervious surface is approximated (Toronto's authoritative layer ships only as a raster GeoTIFF).
Source: Toronto Treed Area + Ravine + Waterbodies + Street Tree Inventory
Enclosure / Eyes on Park
47 buildings within 25 m of the park edge (7 mid-rise, 40 low-rise, 0 tower); avg edge height 7.7 m (~3 floors); 7.8 buildings per 100 m of 602 m perimeter — strong frontage density; edges are low-rise (mostly 2–3 floors); no towers immediately adjacent. "Eyes on the park" come strongest from the 7 mid-rise edge buildings.
Source: Toronto 3D Massing (building footprints + heights)
Border Vacuum Risk
Park edges face the city — no significant border vacuum detected.
Source: Toronto Street Centreline (highways) + rail layer + OSM landuse + building footprints
Equity Context
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 (1 types · 1 records)
- playground
Nearby active-edge features (17)
- transit stop — Wasdale Crescent at Neptune Drive73 m
- transit stop — 45 Wasdale Crescent73 m
- transit stop — Wasdale Crescent at Rajah Street74 m
- transit stop — 86 Neptune Drive79 m
- transit stop — Neptune Drive at Rajah Street87 m
- transit stop — Hotspur Road at Neptune Drive92 m
- transit stop — Neptune Drive at Rajah Street107 m
- transit stop — 125 Neptune Drive129 m
- parking lot143 m
- transit stop — Neptune Drive at Bathurst Street149 m
- transit stop — 122 Neptune Drive149 m
- parking lot156 m
- parking lot162 m
- parking lot168 m
- highway — Highway 401 Collector179 m
- parking lot190 m
- parking lot197 m
Park profile
Five-axis radar across the structural dimensions.
Citywide percentile ranks
Across all Toronto parks in the dataset.
- Overall vitality96th
- Edge activation96th
- Connectivity66th
- Amenity diversity83th
- Natural comfort54th
- Enclosure74th
Most similar parks
Closest in metric space across the five structural dimensions.
- HOLY CROSS CATHOLIC SECONDARY SCHOOL - Building GroundsParkette51
- FRANK OKE SECONDARY SCHOOL - Building GroundsNeighbourhood Park49
- Elm Park - YorkUrban Plaza47
- S.H. ARMSTRONG COMMUNITY CENTRE - Building GroundsNeighbourhood Park49
- Maple Claire ParkUrban Plaza48
Most opposite parks
Furthest in metric space — useful for recognising what kind of park this isn’t.
- Trca Lands ( 26)Ravine / Naturalized Park27
- Toronto Islands - Muggs Island ParkRavine / Naturalized Park25
- Rouge ParkRavine / Naturalized Park28
- Rouge ParkWaterfront Park25
- Rouge ParkRavine / Naturalized Park26
Visitor signals
Public attention measured by Google Places aggregates. This proxies attention, not occupancy. Aggregate-only — no usernames, no review text, no extra photos beyond the cached hero.
p28 citywide · p50 within Corridor / Linear Park
Source: Google Places API · match high (0.97 composite confidence) · last refreshed 5/9/2026. Privacy contract. Measures public attention, not occupancy.
Human activity signals
Programming, social attention, temporal rhythm, and nearby pedestrian / cycling flow. An experimental aggregate layer that complements the spatial scores — partial coverage, partial confidence.
Activity reading: no inputs available. The strongest signal is consistent rhythm across the day. Source coverage: google-places.
Does this score feel accurate?
Your read of Elijah Parkmatters. 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.
What would improve this park?
Generated from the weakest measured dimensions — a starting point, not a prescription.
- 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.
Data sources
- City of Toronto Open Data — Parks (Green Space)Polygon boundaries, official names, types.
- Parks & Recreation FacilitiesInventory of in-park amenities (washrooms, fields, rinks…).
- Toronto Pedestrian NetworkSidewalk segments around and through parks; estimated park entrances.
- Toronto Centreline V2Street segments + intersection nodes near park edges; trails and walkways.
- Toronto 3D MassingBuilding footprints + heights for edge-building counts, frontage density, and tower-in-the-park risk.
- Toronto Treed AreaTree canopy share inside park polygons via stratified-grid sampling.
- Toronto Waterbodies & RiversWater surface inside parks + nearest-water distance for cooling.
- Ravine & Natural Feature ProtectionRavine overlap as a cooling / natural-comfort signal.
- Toronto Street Tree InventoryTree count + density inside park polygons.
- Neighbourhood Profiles(Pending) Equity context proxy.
- OpenStreetMap (Overpass API)Cafés, restaurants, retail, transit stops, parking, highways, rail.