UK Street-Level Crime Data - Categories and Outcomes avatar

UK Street-Level Crime Data - Categories and Outcomes

Pricing

from $1.00 / 1,000 results

Go to Apify Store
UK Street-Level Crime Data - Categories and Outcomes

UK Street-Level Crime Data - Categories and Outcomes

Recorded street-level crime for a location and month as flat rows - category, street, coordinates and outcome - from the official UK police open data API.

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

alaudin burki

alaudin burki

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

20 days ago

Last modified

Categories

Features

Limited permissions

Share

UK Street-Level Crime Data — Categories and Outcomes

Street-level crime recorded by police in England, Wales and Northern Ireland, returned as one flat row per crime. Give the Actor a latitude, a longitude and a month, and it reads the recorded crimes near that point from the UK police open data API and flattens each one — category, street, coordinates, location type and outcome — into a row you can open in a spreadsheet or load into a database. There is no API key, no account and no browser involved.

How to use

  1. Enter the latitude and longitude of the area you care about (decimal degrees) and the month as YYYY-MM.
  2. Leave Max rows at 500, or raise it if the month and area are busy.
  3. Run the Actor. Rows appear in the dataset's Overview tab; a SUMMARY record in the key-value store reports how many rows were fetched and whether the cap truncated the run.
{
"latitude": 52.629729,
"longitude": -1.131592,
"date": "2024-01",
"maxItems": 500
}

Inputs

InputPurposeDefault
latitudeLatitude of the point to search around, in decimal degrees, WGS 84.52.629729 when left blank
longitudeLongitude of the same point, in decimal degrees, WGS 84.-1.131592 when left blank
dateThe month to fetch, as YYYY-MM. This is a month, not a day.2024-01 when left blank
maxItemsHard ceiling on rows. The runner stops taking rows at this number.500
maxPagesKept for consistency with other Actors. This source answers one location-month in a single response, so the Actor makes one request per run and this setting does not change the result.5

Output

One row per recorded crime, de-duplicated on the crime's own id and sorted, so the same month always comes back in the same order.

FieldMeaning
categoryThe crime category as the police record it, for example burglary or anti-social-behaviour.
monthThe month the crime belongs to, as the source writes it, YYYY-MM. A period, not a timestamp.
streetStreet name from the source, which prefixes it, e.g. On or near High Road. No house number and no exact address.
latitudeLatitude of the anonymised map point. Passed through as the API sends it, which is a string — cast it before doing arithmetic.
longitudeLongitude of the same anonymised point, also a string.
locationTypeThe source's location classification, e.g. Force or Residential Building/House.
outcomeThe outcome category recorded for the case (Under investigation, Unable to prosecute suspect, …). The field is omitted when the case has no outcome record yet.
outcomeDateThe month the outcome was recorded, when there is one. Omitted alongside outcome.

Each row also carries id (the source's persistent_id, or a fallback built from month, category and coordinates), source, firstSeenAt and scrapedAt, so a row stays identifiable after export.

Why this is different

The Police API returns deeply nested records — the street is at location.street.name, the outcome at outcome_status.category. This Actor delivers one standalone flat row per crime with those paths already resolved, which is what a spreadsheet, a CSV export or a SQL load actually needs. Rows are sorted deterministically and de-duplicated before they are pushed, so two runs over the same month do not disagree. And when the row cap stops the run early, the dataset says so through SUMMARY.truncated and stopReason instead of silently looking complete.

Limitations

  • Snap points, not addresses. The published coordinates are moved to a nearby anonymised point. That is the API's privacy design; do not treat the coordinate as the scene of the crime.
  • Outcomes are often missing. A crime with no outcome record omits outcome and outcomeDate entirely — that is an open or unresolved case, not a parsing failure.
  • Past months get revised. Forces reclassify and remove records, so the same month fetched twice can differ.
  • One point, one month, per run. The API returns crimes near the coordinate, not a whole force area. For a city, run several points or several months.
  • Coordinates arrive as strings, because that is how the source sends them, even though the dataset schema declares numbers.
  • No personal data. No names, ages or identities are present, and none can be derived here.

FAQ

Do I need an API key? No. The request carries no key or token, and no account is required.

Why is the dataset empty for my month? Either the month has no records near that point, or the month string is not YYYY-MM. The run log distinguishes an empty source from an unreachable one.

Can I get a whole year in one run? No. Each run is one month; schedule twelve runs, or run it on a schedule and let each run write its own dataset.

Why is outcome missing on some rows? The case has no outcome recorded yet. The field is left out rather than filled with a guess.

Are the coordinates exact? No. They are deliberately offset by the publisher, so they locate a street, not a building.

Pricing and limits

The price is shown on the Actor's Apify pricing panel before you run it. Limits are enforced in code: maxItems is a hard ceiling, de-duplication happens before the push, and the run records why it stopped in SUMMARY. Raising maxItems is the only setting that changes how much data a run can return.