Toronto areas in the publish set
Static Toronto Crime Pages
Fast neighborhood pages with custom Toronto boundaries
Breakmap turns official city neighborhoods and hand-drawn custom areas into precomputed public pages with edge-fast charts, summaries, and recent incident detail.
Fits modern data and AI workflows
OpenAI 
Anthropic 
Gemini 
DeepSeek 
Grok Cloudflare
Local cron
planned local refresh cadence
pre-rendered detail pages
served from one Cloudflare Worker
Daily Publish Loop
How It Works
From TPS export
From TPS export
to fresh edge deploy.
Refresh the Source Data
Run the local TPS loader flow on this machine so the generated site reflects the latest incidents.
Generate Static Pages
Build the Astro app once so each neighborhood page, chart series, and index payload is precomputed.
Review It Locally
Use Astro dev for fast iteration or run the Worker preview when you want the edge-served shape.
Deploy the Bundle
Push the generated static output to the existing Cloudflare Worker and keep the landing page on Pages.
Included Surface Area
Keep the public site fast
Keep the public site fast
add islands only when they earn it.
The public product stays static and indexed well, while future logged-in features can be layered back in without slowing the default experience.
Official + Custom Areas
The city file stays intact while custom areas like North Rosedale and Moore Park can overlap it freely.
Precomputed Charts
Trend lines, monthly bars, and breakdown panels are generated ahead of time so public pages stay fast.
Local Cron Friendly
The refresh flow is scriptable on one machine, which makes the daily publish job simple and transparent.
Astro Islands Later
The public surface stays static today, while future login or email capture features can return as islands.
FAQ
Frequently asked questions
What is generated ahead of time?
The neighborhood index, each neighborhood detail page payload, and the chart series rendered on those public pages.
Where do the official boundaries come from?
They come from the checked-in Toronto official neighborhoods GeoJSON, which is treated as the base layer.
How do custom neighborhoods work?
Custom areas live in their own JSON file and can overlap multiple official neighborhoods or sit inside just one.
Do I need a database for the public site?
No. The public site is static after generation, so the deploy itself only needs the built assets served by the Worker.
How often can I refresh the site?
As often as you want, but the intended flow is a daily cron job on this PC that reruns the loader, build, and deploy steps.
Can login features come back later?
Yes. Astro islands are still available if you want subscriptions, alerts, or account-only tools after the public site is solid.
Ship the public map first
layer in interactivity later.
Start from a clean repo with the Astro app, landing page, data loaders, and Worker deploy flow already aimed at fast public pages.
Open the Map