FBI Crime Baseline Data for Venue Security
Canonical URL: https://signalguard.live/docs/signals/crime Meta description: SignalGuard pulls FBI UCR/NIBRS crime baselines through the Crime Data Explorer API and contextualizes every event with the venue jurisdiction's violent and property crime rates versus the U.S. national average. The static risk profile that gives live alerts meaning.
What this signal monitors
The Crime signal establishes a baseline risk profile for the venue's jurisdiction — not a real-time crime feed. Live signals (X chatter, weather, news) tell you what's happening right now; the crime baseline tells you what the static risk environment looks like, which is what makes a "medium" alert in a low-crime suburb mean something different from the same alert in a high-crime urban core. SignalGuard reports per-100k violent and property crime rates for the venue's state, the per-offense breakdown (homicide, rape, robbery, aggravated assault, burglary, larceny, motor vehicle theft, arson), and how each rate compares to the national reference figure.
Data sources
- Primary: FBI Crime Data Explorer (CDE) API at
https://api.usa.gov/crime/fbi/cde/summarized/state/{state}/{offense}— the public surface for the FBI's Uniform Crime Reporting (UCR) and National Incident-Based Reporting System (NIBRS) programs. - Geocoding: OpenStreetMap Nominatim is used to resolve the venue address to an ISO 3166-2 state code (e.g.,
US-CA) that the CDE accepts. - API key: Reads
FBI_API_KEYfrom environment; falls back toDEMO_KEYwith very low rate limits. Real keys are free athttps://api.data.gov/signup/. - National reference rates: Violent crime 380 / 100k, property crime 1,900 / 100k (2022–2023 FBI UCR). The API also returns United States rates per response, which override the constants when present.
- Coverage: US jurisdictions only — non-US venues return
{ ok: false, reason: 'not_us' }. - Publication lag: FBI CDE typically runs 1–2 years behind. If the requested year isn't published yet, SignalGuard walks back up to two years to find data and flags
fellBack: trueso the UI can show "Latest available: 2023."
How SignalGuard scores severity
Each offense's monthly per-100k rates are summed into a yearly figure, then classified against the national reference rate:
| Ratio (state / national) | Severity |
|---|---|
| ≤ 0.7× | low |
| 0.7×–1.2× | medium |
| 1.2×–1.6× | high |
| > 1.6× | critical |
The overall threat level is the higher of the violent and property classifications, with one nuance: a critical property level is capped at high for the overall — property crime alone shouldn't push an event into critical territory. The cache TTL is 24 hours since CDE data only updates annually.
Use cases for event security
- Venue jurisdiction baseline elevated → adjust perimeter staffing. If the venue sits in a state with violent crime running 1.4× the national average, the crime card surfaces
highseverity and your event-security plan can pre-allocate additional perimeter coverage rather than discovering the gap mid-event. Pair with POI density (below) to refine the picture from state-level down to block-level. - Contextualize a "medium" live alert. A medium X-chatter alert hits very differently in a low-crime suburb than in a high-crime downtown. The crime baseline gives operations directors a calibrated read on whether to escalate or wait.
- Compare across a national tour. Touring acts and championship series pass through 30+ jurisdictions. The crime signal lets corporate security normalize staffing decisions to a common scale instead of relying on local intuition that varies by region.
Pairs well with
- POI density signal — pairs state-level rates with block-level urban context
- News signal — local reporting often surfaces incident patterns that the CDE captures only in aggregate
- NTAS signal — federal posture × local baseline = your full static risk picture
Premium upgrade path
The FBI CDE is free but jurisdictionally coarse (state-level) and lagging (1–2 years). For richer baselines:
- LexisNexis Risk Solutions / CAP Index — block-level crime risk scoring used by retail and corporate security
- Placer.ai — anonymized mobility patterns that correlate with crime hotspots (link:
/integrations) - Veraset — raw mobility data feeds for analysts who build their own models
- Local PD data portals — many large city departments publish incident-level data; the SignalGuard team can integrate on request
FAQ
Is FBI crime data real-time? No. The FBI CDE is updated annually with a 1–2 year publication lag. Treat it as a baseline that gives live alerts context, not a live feed. For real-time crime, you need to integrate local PD data portals or commercial feeds.
Why does SignalGuard report state-level data, not city-level? The CDE API exposes summarized data at state and agency granularity. Agency-level (i.e., individual police department) coverage varies by participation in NIBRS — many smaller departments don't report consistently. State rolls up everyone and is the most defensible baseline for comparisons across venues. Block-level resolution is a premium upgrade path.
What's the difference between UCR and NIBRS? UCR (Uniform Crime Reporting) is the legacy program, summary-based. NIBRS (National Incident-Based Reporting System) is the modern replacement that captures incident-level detail. The FBI completed the UCR → NIBRS transition in 2021, so CDE data from 2021 onward is NIBRS-native.
How does SignalGuard handle states with low NIBRS participation?
The CDE returns whatever is published; SignalGuard reports the figure and flags coverage in the UI. For states with persistent gaps, expect the breakdown array to be shorter (fewer per-offense rows).
Can I trust the year-over-year trend? The CDE definition changes (UCR → NIBRS) and agency participation shifts make naive YoY comparisons fragile. SignalGuard reports rates per year but does not compute trend deltas by default — see the FBI's own published cautions on cross-system comparisons.