Geometry First
v1 prioritizes point + radius for predictable, fast API queries.
Default radii: 150m (block-ish) and 400m (nearby).
Methodology
How the block brief is calculated
The brief is designed to be useful in about 10 seconds and transparent in under a minute. This page shows the exact logic behind each module, where fallback matching is used, and how severity labels are assigned.
Transparent Severity
Every module includes Low/Medium/High plus threshold copy and impact framing.
No hidden scoring model.
Resilient By Design
Dataset failures degrade a module, not the whole page.
Partial rendering + per-dataset caching.
Interactive Explorer
Use these controls to see how scoring, locality filtering, and data scope work behind the scenes.
Geometry Scope
Adjust radius to see how much area each query can cover.
Approx area: 0.50 km² (7.1x of 150m baseline)
Severity Simulator
Preview the impact sentence and severity chip logic for each module.
No active disruption signals.
Low severity. No immediate disruption signal. Typical travel and curb access conditions are likely right now.
Low: 0 active disruptions. Medium: 1-2. High: 3+.
Event Relevance Logic
Simulate how event rows are ranked to avoid borough-wide noise.
Score: 5 (High relevance)
Dataset Browser
Search datasets and filter by module to inspect source coverage quickly.
- DOB Permit Issuance(ipu4-2q9a) • modules: Construction (DOB)
- DOB NOW: Build – Approved Permits(rbx6-tga4) • modules: Construction (DOB)
- DOB Complaints Received(eabe-havv) • modules: Construction (DOB)
- DOB ECB Violations(6bgk-3dad) • modules: Construction (DOB)
- Street Construction Permits (2022-Present)(tqtj-sjs8) • modules: Right now, Street disruption (DOT)
- Street Opening Permits(9jic-byiu) • modules: Street disruption (DOT)
- Street Closures due to construction activities by Block(i6b5-j7bu) • modules: Right now, Street disruption (DOT)
- Motor Vehicle Collisions - Crashes(h9gi-nx95) • modules: Safety (collisions)
- 311 Service Requests from 2020 to Present(erm2-nwe9) • modules: 311 pulse
- Garbage Collection Schedule(p7k6-2pm8) • modules: Sanitation
- DSNY Frequencies(rv63-53db) • modules: Sanitation
- NYC Permitted Event Information(tvpp-9vvx) • modules: Upcoming events
- Community Districts(5crt-au7u) • modules: Upcoming events
- Film Permits(tg4x-b46p) • modules: Right now, Film permits
Scoring and ranking rules
- 311 pulse ranks complaint types by count in the current 30-day window, then compares to prior 30 days.
- Street works ranks active-now first, then longer duration, then proximity.
- Collisions clusters records within 75m and labels hotspot by frequent intersection text.
- Right now strip combines active closures, active street works, and active film permits.
- Events are ranked for locality using community district, closure signal, and nearby street-text signal.
Reliability and caching model
- Each module queries independently so one outage does not blank the full brief.
- Per-block and per-dataset cache keys reduce latency and API load.
- High-churn datasets refresh frequently while stable layers cache longer.
- User-visible warnings appear when partial data is shown.
Known limitations and current fallbacks
- Some datasets lack stable geometry and require BIN/BBL, borough, ZIP, or text-based matching.
- Sanitation uses DSNY Frequencies (rv63-53db) while the preferred schedule source (p7k6-2pm8) remains sparse through this API path.
- v1 uses radius consistency over full blockface precision for speed and reliability.
Source code
Live app: whats-happening-on-my-block.vercel.app