An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2005 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2006 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is a fixed-width YYYYMMDDHHMMSS string, preserved as a calendar date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2007 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2008 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2009 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2010 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2011 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2012 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2013 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2014 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2015 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2016 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2017 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2018 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2019 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2020 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
These archives encode Eastern local call time as UTC epochs; calendar dates are normalized to America/New_York.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2021 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
These archives encode Eastern local call time as UTC epochs; calendar dates are normalized to America/New_York.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2022 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
These archives encode Eastern local call time as UTC epochs; calendar dates are normalized to America/New_York.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2023 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2024 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
An import date is not an incident date or a promise of a live feed. call records are counted using this source’s definitions.
Source coverage notes
Asheville Police calls assigned a 2025 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police calls assigned a 2026 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
Publisher documents a 90-day public-release delay. Latest call verified June 28, 2026 on September 27, 2026; this is not a live emergency feed.
An import date is not an incident date or a promise of a live feed. offense records are counted using this source’s definitions.
Source coverage notes
Asheville's public dashboard offense view only, not all Buncombe County or North Carolina. Reported date, not occurrence date.
The overlapping Crimes_public and APD Public Incidents mirrors are deliberately not appended.
Police classifications and public-release filters can change. Long historical counts should not be treated as a consistent measure of all crime.
Exact address, geometry, officer, narrative, and relationship fields are excluded. Offense IDs are published offense references, not unique case counts.
Official public city source; attribute Asheville Police. No specific license is asserted for this offense layer.
Cary only, not all Wake County or North Carolina. Selected published offense classes; sexual assaults, crimes involving juveniles, and some active investigations are omitted by the publisher.
Catalog refreshed September 27, 2026, but latest occurrence verified July 26, 2026. Catalog refresh is not record freshness.
Mandatory upstream grouping uses only the allowed incident/date/offense/district fields; duplicate person-expanded rows are not fetched. Group multiplicities are checked against the source row count, not labeled as additional offenses.
No coordinates are published in this schema. Apartment/subdivision data and other person-sensitive or unnecessary fields are excluded.
Undated records are excluded from the dated series. CC0 1.0 public-domain dedication; source attribution is retained.
Contains information from Town of Chapel Hill Police Department, made available under the Open Database License (ODbL) 1.0. Keep this component attributed and separately identifiable; redistribution of a derived database must retain ODbL requirements.
Mandatory upstream DISTINCT over only incident ID, occurrence date, offense and city. Victim demographics, person-level fields, exact addresses, and coordinates are excluded from every request. Raw source row IDs are not selected.
One row represents a distinct published incident/date/offense/city combination, not one person or necessarily one unique incident.
Latest occurrence verified May 31, 2026; do not label this a current September feed. Earliest legacy records date to 1991 and do not establish continuous coverage since then.
Metadata has conflicting local-time and UTC conventions. Preserve publisher-encoded calendar dates and do not infer local-hour patterns. Chapel Hill coverage only, not the entire county or state.
An import date is not an incident date or a promise of a live feed. incident records are counted using this source’s definitions.
Source coverage notes
One published incident with its highest NIBRS offense, not every offense in each case. Reported-date basis. Charlotte-Mecklenburg contribution only, not statewide coverage.
Includes non-criminal and unfounded reports; incident records are not confirmed crimes. The publisher excludes 800-series NIBRS codes from criminal-incident analysis.
Only explicitly public coordinates retained. Exact LOCATION field is excluded.
The public server intermittently rejects valid identical queries. Only verified transient application errors receive bounded retries; source counts and unique IDs must still reconcile before publication.
An import date is not an incident date or a promise of a live feed. offense records are counted using this source’s definitions.
Source coverage notes
This is a nonspatial table. No coordinates may be inferred from ADDRESS2. Reported-date window, not occurrence date. State page covers Durham only for this source.
An import date is not an incident date or a promise of a live feed. offense records are counted using this source’s definitions.
Source coverage notes
Fayetteville Police offense records, not victim or person records. Multiple offenses can share a case number; this is not all Cumberland County or North Carolina.
Dates use Eastern local calendar days. Query bounds are publisher-local; feature epochs are UTC. Verified winter and summer boundary tests reconcile the source's missing timezone metadata.
Exact address, apartment, premise, and all person-level records are excluded. Published coordinates are further rounded.
Official city open-data source; attribute Fayetteville Police. No specific machine-readable reuse license was provided.
An import date is not an incident date or a promise of a live feed. offense records are counted using this source’s definitions.
Source coverage notes
Fayetteville Police property-offense records only, not all Cumberland County or North Carolina. Several offenses may share a case number.
Dates use Eastern local calendar days. Query bounds are publisher-local; feature epochs are UTC. Verified winter and summer boundary tests reconcile the source's missing timezone metadata.
Exact address, apartment, premise, and all person-level records are excluded. Published coordinates are further rounded.
Official city open-data source; attribute Fayetteville Police. No specific machine-readable reuse license was provided.
Fayetteville public-order and other society offenses
Fayetteville Police Department
Stored records
33,319 offense records
Published dates in this snapshot
Jan 1, 2010 – Sep 26, 2026
Date basis
Occurrence date
Imported
Sep 27, 2026
An import date is not an incident date or a promise of a live feed. offense records are counted using this source’s definitions.
Source coverage notes
Fayetteville Police crimes-against-society offense records only, not all Cumberland County or North Carolina. Multiple offenses may share a case number.
Dates use Eastern local calendar days. Query bounds are publisher-local; feature epochs are UTC. Verified winter and summer boundary tests reconcile the source's missing timezone metadata.
Exact address, apartment, premise, and all person-level records are excluded. Published coordinates are further rounded.
Official city open-data source; attribute Fayetteville Police. No specific machine-readable reuse license was provided.
An import date is not an incident date or a promise of a live feed. offense records are counted using this source’s definitions.
Source coverage notes
Historical Greensboro city offense archive, not all Guilford County or North Carolina. Latest report date verified October 6, 2025; not a live current feed.
Reported date is used. Offense records may share an incident ID and are not unique incidents or convictions.
Exact addresses, unverified coordinates, victim counts, and person-level datasets are excluded.
Official Open Gate City source; attribute Greensboro Police. No specific machine-readable license was supplied.