Beat boundaries are frequently changing due to operational priorities.
We enable forces to update multiple datasets.
Ensuring all data is linked to the correct beat code and officers are consistently able to access all of the related datasets.
Automatically connect to beat boundary data via the Web Feature Service API for a fully automated solution
Drag and drop beat boundary data to run automated beat code update workflow
No code solution
High speed processing (c. 91,000 records in 10 minutes)
Any update is audited on the data
Certificate of transaction for full transparency of the process applied
Police officers are able to instantly obtain a full understanding of what has happened at a location, as each boundary change will be automatically updated across multiple datasets, both for incident response and case investigation.
Having the correct beat code on police records is important, however keeping the beat code on record current and correct can be a lengthy process with multiple datasets needing updating. This lengthy and often manual process puts risk to police officers having the correct beat code in their data, and the ability to use data to link multiple datasets and instantly get a full understanding of what has happened at a location.
How it works
This application takes a no-code, rules-based approach to ensure that each police record has the correct beat code, ensuring that police officers are able to instantly get a full understanding of what has happened at a location by linking multiple datasets. The app can be activated either through a drag and drop process or automatically via the Web Feature Service API.
After an update of the beat boundaries is submitted to the application, the application will check each police record against the new boundaries to ensure the record has the correct beat code for the area it is within. If the police record does not have the correct beat code, the application will automatically update the police record’s beat code with the new area it is within and audit the change.