UK Police Data - Ismena website

info@ismena.com

UK Police Data Connector

Connector Details

Type

Virtual machines, Single VM , BYOL

Runs on

Google Compute Engine

Last Update

24 October, 2024

Category

Overview

The UK Police Data Connector facilitates seamless integration with the UK Police Data API, providing access to police-related data including neighbourhood team members, upcoming events, street-level crime and outcome data, and nearest police stations for UK police forces. This connector acts as a proxy to streamline data retrieval, supporting actions for force details, crime data, neighbourhood information, and stop-and-search records.

Integration Overview

This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the UK Police Data Connector on Google Cloud Platform (GCP).

Supported Integration Action Points

listForces: Retrieves a list of all UK police forces.
getForce: Retrieves details for a specific police force.
getForceSeniorOfficers: Retrieves senior officers for a specific police force.
getStreetLevelCrimes: Retrieves street-level crime data for a specified area or polygon.
getCrimesStreetDates: Retrieves available dates for street-level crime data.
getStreetLevelOutcomes: Retrieves street-level crime outcomes for a specified location.
getCrimesAtLocation: Retrieves crimes at a specific location.
getCrimesNoLocation: Retrieves crimes without specific location data.
getCrimeCategories: Retrieves available crime categories.
getCrimeLastUpdated: Retrieves the last updated date for crime data.
getOutcomesForCrime: Retrieves outcomes for a specific crime.
listNeighbourhoods: Retrieves neighbourhoods for a specific police force.
getNeighbourhood: Retrieves details for a specific neighbourhood.
getNeighbourhoodBoundary: Retrieves the geographic boundary for a neighbourhood.
getNeighbourhoodTeam: Retrieves team members for a neighbourhood.
getNeighbourhoodEvents: Retrieves upcoming events for a neighbourhood.
getNeighbourhoodPriorities: Retrieves policing priorities for a neighbourhood.
locateNeighbourhood: Locates a neighbourhood by geographic coordinates.
getStopAndSearchesByArea: Retrieves stop-and-search records for a specified area.
getStopAndSearchesAtLocation: Retrieves stop-and-search records at a specific location.
getStopAndSearchesNoLocation: Retrieves stop-and-search records without specific location data.
get止AndSearchesByForce: Retrieves stop-and-search records for a specific police force.

Detailed Integration Documentation

List All Police Forces

Action	listForces
Purpose	Retrieves a comprehensive list of all UK police forces. This serves as the primary entry point for accessing police force data.
Parameters	Required: None. Optional: None.
Configuration	Ensure the connector is configured with the base URL via the CONNECTOR_ENV_UKPOLICEDATA_BASE_URL environment variable in GCP (e.g., https://data.police.uk/api).
Output	Successful: Returns a JSON array of objects with: id: Police force ID (string, e.g., "metropolitan"). name: Police force name (string, e.g., "Metropolitan Police Service"). Failure: Returns error details (e.g., HTTP 404 or 500 with error message).
Workflow Example	Configure the connector with the base URL in GCP (e.g., Cloud Functions environment variable). Execute the listForces action. Process the response to identify police forces for further actions (e.g., selecting a force for crime data queries).

Get Specific Police Force

Action	getForce
Purpose	Retrieves details for a specific UK police force, useful for understanding force-specific information.
Parameters	Required: id: Police force ID (string, e.g., "metropolitan"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON object with: id: Police force ID (string, e.g., "metropolitan"). name: Police force name (string, e.g., "Metropolitan Police Service"). Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example	Execute the getForce action with id=metropolitan. Review the response to obtain force details. Use the details for reporting or integration with other actions.

Get Senior Officers

Action	getForceSeniorOfficers
Purpose	Retrieves a list of senior officers for a specific police force, enabling access to leadership information.
Parameters	Required: id: Police force ID (string, e.g., "metropolitan"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: name: Officer name (string, e.g., "John Smith"). rank: Officer rank (string, e.g., "Chief Constable"). bio: Officer biography (string). Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example	Execute the getForceSeniorOfficers action with id=metropolitan. Process the response to display senior officer information in a dashboard. Use the data for organizational analysis or public reporting.

Get Street-Level Crimes

Action	getStreetLevelCrimes
Purpose	Retrieves street-level crime data for a specified area or polygon, useful for crime mapping and analysis.
Parameters	Required: None (at least one of lat/lng or poly must be provided). Optional: lat: Latitude of area center (double, e.g., 51.5074). lng: Longitude of area center (double, e.g., -0.1278). poly: Polygon boundary (string, e.g., "lat,lng:lat,lng:..."). date: Year and month of crime data (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: id: Crime ID (string, e.g., "abc123"). category: Crime category (string, e.g., "burglary"). location: Location details (object with latitude, longitude, street). date: Crime date (string, e.g., "2023-01"). Failure: Returns error details (e.g., error-type: invalid-parameters).
Workflow Example	Execute the getStreetLevelCrimes action with lat=51.5074, lng=-0.1278, and date=2023-01. Process the response to map crime locations in a GCP-hosted application. Use the data for crime trend analysis or public safety reporting.

Get Available Crime Dates

Action	getCrimesStreetDates
Purpose	Retrieves available dates for street-level crime data, enabling users to select valid time periods for queries.
Parameters	Required: None. Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of strings (e.g., ["2023-01", "2023-02"]). Failure: Returns error details (e.g., HTTP 500).
Workflow Example	Execute the getCrimesStreetDates action. Review the response to select a valid date for crime queries. Use the date in subsequent actions like getStreetLevelCrimes.

Get Street-Level Outcomes

Action	getStreetLevelOutcomes
Purpose	Retrieves street-level crime outcomes for a specified location, useful for understanding case resolutions.
Parameters	Required: None (at least one of location_id, lat/lng, or poly must be provided). Optional: location_id: Location ID (string). lat: Latitude (double, e.g., 51.5074). lng: Longitude (double, e.g., -0.1278). poly: Polygon boundary (string, e.g., "lat,lng:lat,lng:..."). date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: crime_id: Crime ID (string, e.g., "abc123"). outcome: Outcome description (string, e.g., "Investigation complete; no suspect identified"). date: Outcome date (string, e.g., "2023-01"). Failure: Returns error details (e.g., error-type: invalid-parameters).
Workflow Example	Execute the getStreetLevelOutcomes action with lat=51.5074, lng=-0.1278, and date=2023-01. Process the response to analyze crime outcomes. Integrate with GCP BigQuery for outcome trend analysis.

Get Crimes at Location

Action	getCrimesAtLocation
Purpose	Retrieves crimes at a specific location, enabling precise crime data analysis.
Parameters	Required: None (at least one of location_id or lat/lng must be provided). Optional: location_id: Location ID (string). lat: Latitude (double, e.g., 51.5074). lng: Longitude (double, e.g., -0.1278). date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: id: Crime ID (string, e.g., "abc123"). category: Crime category (string, e.g., "burglary"). location: Location details (object with latitude, longitude, street). date: Crime date (string, e.g., "2023-01"). Failure: Returns error details (e.g., error-type: invalid-location).
Workflow Example	Execute the getCrimesAtLocation action with location_id=12345 and date=2023-01. Save the crime data for location-specific analysis. Visualize results in a GCP-hosted dashboard.

Get Crimes with No Location

Action	getCrimesNoLocation
Purpose	Retrieves crimes without specific location data, useful for force-wide crime analysis.
Parameters	Required: category: Crime category (string, e.g., "burglary"). force: Police force ID (string, e.g., "metropolitan"). Optional: date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: id: Crime ID (string, e.g., "abc123"). category: Crime category (string, e.g., "burglary"). date: Crime date (string, e.g., "2023-01"). Failure: Returns error details (e.g., error-type: invalid-category).
Workflow Example	Execute the getCrimesNoLocation action with category=burglary, force=metropolitan, and date=2023-01. Analyze the response for force-wide crime trends. Store results in GCP Cloud Storage for further processing.

Get Crime Categories

Action	getCrimeCategories
Purpose	Retrieves available crime categories, enabling users to validate or select categories for queries.
Parameters	Required: None. Optional: date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: url: Category URL (string, e.g., "burglary"). name: Category name (string, e.g., "Burglary"). Failure: Returns error details (e.g., HTTP 500).
Workflow Example	Execute the getCrimeCategories action with date=2023-01. Use the response to populate a crime category selection interface. Integrate with GCP App Engine for dynamic UI updates.

Get Last Updated Date

Action	getCrimeLastUpdated
Purpose	Retrieves the last updated date for crime data, ensuring users query the most recent data.
Parameters	Required: None. Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON object with: date: Last updated date (string, e.g., "2023-01"). Failure: Returns error details (e.g., HTTP 500).
Workflow Example	Execute the getCrimeLastUpdated action. Use the response to verify data freshness. Schedule GCP Cloud Scheduler tasks based on the update frequency.

Get Outcomes for Crime

Action	getOutcomesForCrime
Purpose	Retrieves outcomes for a specific crime, providing resolution details.
Parameters	Required: persistent_id: Crime ID (string, e.g., "abc123"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: crime_id: Crime ID (string, e.g., "abc123"). outcome: Outcome description (string, e.g., "Investigation complete; no suspect identified"). date: Outcome date (string, e.g., "2023-01"). Failure: Returns error details (e.g., error-type: invalid-crime-id).
Workflow Example	Execute the getOutcomesForCrime action with persistent_id=abc123. Process the response to display crime resolution details. Integrate with GCP Pub/Sub for real-time notifications.

List Neighbourhoods

Action	listNeighbourhoods
Purpose	Retrieves a list of neighbourhoods for a specific police force, enabling area-specific analysis.
Parameters	Required: force: Police force ID (string, e.g., "leicestershire"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: id: Neighbourhood ID (string, e.g., "abc123"). name: Neighbourhood name (string, e.g., "City Centre"). force: Police force ID (string, e.g., "leicestershire"). Failure: Returns error details (e.g., error-type: invalid-force).
Workflow Example	Execute the listNeighbourhoods action with force=leicestershire. Use the response to populate a neighbourhood selection interface. Deploy on GCP App Engine for user interaction.

Get Neighbourhood Details

Action	getNeighbourhood
Purpose	Retrieves details for a specific neighbourhood, useful for community policing insights.
Parameters	Required: force: Police force ID (string, e.g., "leicestershire"). id: Neighbourhood ID (string, e.g., "abc123"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON object with: id: Neighbourhood ID (string, e.g., "abc123"). name: Neighbourhood name (string, e.g., "City Centre"). force: Police force ID (string, e.g., "leicestershire"). Failure: Returns error details (e.g., error-type: invalid-neighbourhood).
Workflow Example	Execute the getNeighbourhood action with force=leicestershire and id=abc123. Display neighbourhood details in a GCP-hosted application. Use for community engagement reporting.

Get Neighbourhood Boundary

Action	getNeighbourhoodBoundary
Purpose	Retrieves the geographic boundary for a neighbourhood, enabling geospatial analysis.
Parameters	Required: force: Police force ID (string, e.g., "leicestershire"). id: Neighbourhood ID (string, e.g., "abc123"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: latitude: Latitude (double, e.g., 51.5074). longitude: Longitude (double, e.g., -0.1278). Failure: Returns error details (e.g., error-type: invalid-neighbourhood).
Workflow Example	Execute the getNeighbourhoodBoundary action with force=leicestershire and id=abc123. Use the boundary data for mapping in GCP Cloud Run. Integrate with Google Maps API for visualization.

Get Neighbourhood Team

Action	getNeighbourhoodTeam
Purpose	Retrieves team members for a neighbourhood, providing community policing contact information.
Parameters	Required: force: Police force ID (string, e.g., "leicestershire"). id: Neighbourhood ID (string, e.g., "abc123"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: name: Team member name (string, e.g., "Jane Doe"). rank: Rank (string, e.g., "Police Constable"). contact_details: Contact information (object with email). Failure: Returns error details (e.g., error-type: invalid-neighbourhood).
Workflow Example	Execute the getNeighbourhoodTeam action with force=leicestershire and id=abc123. Display team member details in a community portal on GCP. Use for public engagement initiatives.

Get Neighbourhood Events

Action	getNeighbourhoodEvents
Purpose	Retrieves upcoming events for a neighbourhood, enabling community engagement.
Parameters	Required: force: Police force ID (string, e.g., "leicestershire"). id: Neighbourhood ID (string, e.g., "abc123"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: title: Event title (string, e.g., "Community Meeting"). date: Event date (string, e.g., "2023-08-10T18:00:00Z"). location: Event location (string, e.g., "Community Centre"). Failure: Returns error details (e.g., error-type: invalid-neighbourhood).
Workflow Example	Execute the getNeighbourhoodEvents action with force=leicestershire and id=abc123. Display events in a GCP-hosted calendar application. Notify users via GCP Cloud Functions and Pub/Sub.

Get Neighbourhood Priorities

Action	getNeighbourhoodPriorities
Purpose	Retrieves policing priorities for a neighbourhood, providing insight into local policing focus.
Parameters	Required: force: Police force ID (string, e.g., "leicestershire"). id: Neighbourhood ID (string, e.g., "abc123"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: issue: Priority issue (string, e.g., "Youth-related anti-social behaviour"). action: Action taken (string, e.g., "Increased patrols during evenings"). Failure: Returns error details (e.g., error-type: invalid-neighbourhood).
Workflow Example	Execute the getNeighbourhoodPriorities action with force=leicestershire and id=abc123. Display priorities in a GCP-hosted public portal. Use for community policing transparency.

Locate Neighbourhood by Coordinates

Action	locateNeighbourhood
Purpose	Locates a neighbourhood by geographic coordinates, enabling location-based services.
Parameters	Required: q: Latitude and longitude (string, e.g., "51.500617,-0.124629"). Optional: None.
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON object with: id: Neighbourhood ID (string, e.g., "abc123"). name: Neighbourhood name (string, e.g., "City Centre"). force: Police force ID (string, e.g., "leicestershire"). Failure: Returns error details (e.g., error-type: invalid-coordinates).
Workflow Example	Execute the locateNeighbourhood action with q=51.500617,-0.124629. Use the response to identify the neighbourhood for further queries. Integrate with GCP Cloud Run for location-based applications.

Get Stop and Searches by Area

Action	getStopAndSearchesByArea
Purpose	Retrieves stop-and-search records for a specified area, useful for transparency and analysis.
Parameters	Required: None (at least one of lat/lng or poly must be provided). Optional: lat: Latitude (double, e.g., 51.5074). lng: Longitude (double, e.g., -0.1278). poly: Polygon boundary (string, e.g., "lat,lng:lat,lng:..."). date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: type: Search type (string, e.g., "Person search"). datetime: Search date (string, e.g., "2023-01-01T12:00:00Z"). location: Location details (object with latitude, longitude, street). outcome: Search outcome (string, e.g., "Arrest"). Failure: Returns error details (e.g., error-type: invalid-parameters).
Workflow Example	Execute the getStopAndSearchesByArea action with lat=51.5074, lng=-0.1278, and date=2023-01. Analyze stop-and-search data in a GCP BigQuery dataset. Visualize trends using Google Data Studio.

Get Stop and Searches at Location

Action	getStopAndSearchesAtLocation
Purpose	Retrieves stop-and-search records at a specific location, enabling precise analysis.
Parameters	Required: None (at least location_id must be provided). Optional: location_id: Location ID (string). date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: type: Search type (string, e.g., "Person search"). datetime: Search date (string, e.g., "2023-01-01T12:00:00Z"). location: Location details (object with latitude, longitude, street). outcome: Search outcome (string, e.g., "Arrest"). Failure: Returns error details (e.g., error-type: invalid-location).
Workflow Example	Execute the getStopAndSearchesAtLocation action with location_id=12345 and date=2023-01. Process the response for location-specific analysis. Store results in GCP Cloud Storage for reporting.

Get Stop and Searches with No Location

Action	getStopAndSearchesNoLocation
Purpose	Retrieves stop-and-search records without specific location data, useful for force-wide analysis.
Parameters	Required: force: Police force ID (string, e.g., "metropolitan"). Optional: date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: type: Search type (string, e.g., "Person search"). datetime: Search date (string, e.g., "2023-01-01T12:00:00Z"). outcome: Search outcome (string, e.g., "Arrest"). Failure: Returns error details (e.g., error-type: invalid-force).
Workflow Example	Execute the getStopAndSearchesNoLocation action with force=metropolitan and date=2023-01. Analyze force-wide stop-and-search trends. Use GCP BigQuery for data aggregation.

Get Stop and Searches by Force

Action	getStopAndSearchesByForce
Purpose	Retrieves stop-and-search records for a specific police force, enabling force-level transparency.
Parameters	Required: force: Police force ID (string, e.g., "metropolitan"). Optional: date: Year and month (string, e.g., "2023-01").
Configuration	Ensure the connector is configured with the correct base URL.
Output	Successful: Returns a JSON array of objects with: type: Search type (string, e.g., "Person search"). datetime: Search date (string, e.g., "2023-01-01T12:00:00Z"). location: Location details (object with latitude, longitude, street, if available). outcome: Search outcome (string, e.g., "Arrest"). Failure: Returns error details (e.g., error-type: invalid-force).
Workflow Example	Execute the getStopAndSearchesByForce action with force=metropolitan and date=2023-01. Process the response for force-level reporting. Visualize in a GCP-hosted dashboard using Google Data Studio.

Workflow Creation with the Connector

Example Workflow: Crime and Neighbourhood Analysis on GCP

Retrieve Police Forces	Use the `listForces` action to fetch a list of available police forces. Identify a target force (e.g., metropolitan).
Query Neighbourhoods	Execute the `listNeighbourhoods` action with `force=metropolitan` to fetch neighbourhoods. Select a neighbourhood (e.g., `id=abc123`) for further analysis.
Fetch Crime Data	Use the `getStreetLevelCrimes` action with `lat=51.5074`, `lng=-0.1278`, and `date=2023-01` to retrieve crime data. Process the response to map crimes in a GCP Cloud Run application.
Analyze Outcomes	Execute the `getStreetLevelOutcomes` action with `lat=51.5074`, `lng=-0.1278`, and `date=2023-01` to fetch crime outcomes. Store results in GCP BigQuery for trend analysis.
Enhance UI with Neighbourhood Data	Execute the `getNeighbourhoodEvents` and `getNeighbourhoodPriorities` actions with `force=metropolitan` and `id=abc123` to fetch events and priorities. Integrate data into a GCP App Engine-hosted UI for community engagement.

This workflow enables applications to provide users with accurate time zone data and conversions, enhancing global time management and scheduling capabilities.

Pricing

bill-and-calculator-2023-11-27-05-25-06-utc 1

Request a Quote

Support

For Technical support please contact us on

custom-connectors-support@isolutions.sa

A tech solution company dedicated to providing innovation thus empowering businesses to thrive in the digital age.

Register to IBM x iSolution Event