The ability to view and filter crime ('read permissions') can be made available to every user (i.e. don't require the user to sign in).

However, the ability to make changes to the information the mapper holds ('write permissions') should be restricted to users that sign in to an account which is assigned these permissions. Users currently without such permissions could be given the option to make a request for them to be given to them).

With these different levels of users each with different extents of privileges/permissions, functionality to control the visibility of the plotted crimes to certain groups of users could be implemented (e.g. 'Global' for which everyone can see the crime or 'Private' for which only specified users or groups of users can see the crime).

Expand the import functionality to accommodate for other file types/data formats:

• XML
• JSON

Import and multiple marker deletion functionality is not currently working due to local deployment paths being used to specify the location of the required background scripts (ImportMarkersDaemon.php and DeleteMarkersDaemon.php).

• Deployment Paths
• Implementation/Configuration

Highlight geographical areas which are likely to see new instances of crime ('crime hotspots').
Identify crime patterns and warn of crime sprees (e.g. keyless cars being stolen in an area).
Crime analysis could also be expanded upon by offering a heatmap visualisation (in addition to the current clustering).

Implement different marker icons for the different categories of crime (e.g. an icon of a car to indicate a crime categorised under 'Vehicle offences'). Imported crimes or markers with imported crime types can be left to use the default marker icon.

A prior development version of the solution is currently hosted at: https://hq017496.webs.act.reading.ac.uk.
The web hosting control panel can no longer be accessed and it is likely the hosting provider will soon no longer host the solution.

Moving forward, the solution is to be hosted and made accessible using Amazon Web Services (AWS).
(When deployed, the HTTP referrers allowed to make use of the implemented API key should be updated).

Configure max_upload_file_size in php.ini (larger files are unable to be imported).

Lighthouse tool reports a performance score of 34.

Implement integration between the solution's map and Google Data Studio.