Petticoat Creek Conservation Area
Wilderness / Conservation Park, near the bottom of the city overall (score 18, rank ~2th percentile). Strongest: amenity diversity; weakest: natural comfort.
Petticoat Creek Conservation Area scores 18 / 100. Strongest dimensions: enclosure / eyes on park and connectivity. Weakest: edge activation (0). Border-vacuum risk is elevated (96). This score is a transparent reading of Jane Jacobs-style vitality factors, not a definitive judgment.
Area · 64.29 ha
What's here
Weighted across six dimensions · confidence 49%
Scores are not bell-curved. Percentiles and expected scores provide context without changing the underlying model.
Loading map…
The parks map is loading.Boundary: OpenStreetMap contributors (ODbL).
Explain this score
Where did the 18 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
Petticoat Creek Conservation Area works because its amenity diversity score (20) is middle of the pack.
What limits this park
Petticoat Creek Conservation Area is held back by natural comfort (24, bottom quartile): only 0% canopy means little summer shade; border-vacuum risk is also elevated (96).
Most distinctive characteristic
Most distinctive feature: exceptionally low natural comfort (24, bottom quartile).
Jacobs reading
Petticoat Creek Conservation Area is currently underperforming on both axes: neither integrated into the city nor offering deep natural respite. A candidate for design intervention.
Performance in context
- Reads as a modest underperformer relative to comparable parks (gap -8; cohort: Wilderness / Conservation Park).
Typology classification
Classified as Wilderness / Conservation Park: 0% ravine, 0% canopy, 64 ha, connectivity 25, 2 amenity types. Secondary read: Ravine / Naturalized Park (0% ravine overlap, 0% canopy).
Edge Activation
Within 100 m of the park edge: 0 active uses (none) and 10 dead/hostile uses (parking_lot, rail). 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
0 transit stops within 400 m of the park edge (OSM-derived). City Pedestrian Network + Street Centreline returned no nearby segments for this park (common for ravine fragments) so the rest of the connectivity components default to neutral 50.
Source: OSM transit stops only (Centreline + Pedestrian Network not present near this park)
Amenity Diversity
2 distinct amenity types in the park (picnic, pool). 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: 0.0% estimated tree canopy; 1.8% water surface. Reading: water-cooled. Source coverage: waterbodies. 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
No buildings within 50 m of this park edge, typical of ravines, watercourses, and hydro corridors. Enclosure is held at a neutral 50 with low confidence; for natural areas, this metric is essentially not applicable.
Source: Toronto 3D Massing (no nearby buildings detected)
Border Vacuum Risk
Border-vacuum factors within 50 m of the park: parking_lot, parking_lot, parking_lot, parking_lot, parking_lot, Kingston Subdivision, Kingston Subdivision. Jacobs warned that highways, rail, parking lots and blank institutional edges act as "vacuums" that suppress foot traffic and isolate the park from its neighbourhood.
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 (2 types · 2 records)
- picnic
- pool
Nearby active-edge features (11)
- parking lot0 m
- parking lot0 m
- parking lot0 m
- parking lot0 m
- rail: Kingston Subdivision10 m
- rail: Kingston Subdivision14 m
- parking lot30 m
- rail: Kingston Subdivision52 m
- rail: Kingston Subdivision56 m
- parking lot88 m
- parking lot101 m
Park profile
Five-axis radar across the structural dimensions.
Citywide percentile ranks
Across all Toronto parks in the dataset.
- Overall vitality2th
- Edge activation55th
- Connectivity21th
- Amenity diversity68th
- Natural comfort4th
- Enclosure15th
Most similar parks
Closest in metric space across the five structural dimensions.
- Glencrest ParkOther26
- Fred Halliday Memorial ParkOther29
- Jennifer Kateryna Koval'S'Kyj ParkOther26
- John Daniels ParkOther18
- Wade Gate ParkOther23
Most opposite parks
Furthest in metric space. Useful for recognising what kind of park this isn’t.
- Kew GardensNeighbourhood Park75
- Leslie Grove ParkParkette73
- Bellevue Square ParkCivic Square73
- Shaw ParkParkette69
- Market Lane ParkUrban Plaza67
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 Petticoat Creek Conservation Areamatters. 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.
- 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.
- Add or open more entrances and improve sidewalk continuity around the park. More permeability means more spontaneous use.
- 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.
- 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. Boundaries are reconciled against OpenStreetMap (ODbL) for new and updated parks.
- 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.