Plotting aggregated points over Google Earth satellite images

Olly has created a web interface that plots our data on to Google Earth satellite images. Our data is aggregated to the centre of BNG 1km squares to preserve confidentiality and to standardise the resolution of our database as there are several different data sources to compare. I am concerned that end users may forget / not read the project documentation and think that a point marks the exact location of data when in reality it could be anywhere in a km square around the point.  Does anyone else share these concerns - or have a way of reminding an end user of this?

Andrew.

Project Plan Post 3 of 7: Risk Analysis and Success Plan

The initial risk analysis is detailed below.

No	Risk	Probability	Impact	Mitigation
1	Staffing not in place at project start	low	low	· Key project directing/managing staff already in post. · GIS specialist available as required to support project. · No recruitment is necessary for project start up.
2	Absence, illness or loss of key staff during the project	low	low	· A ‘pool’ of analysts and technical resource exists within IT Services the workload of these could be reprioritised to support this initiative. · Team-based culture with collaborative practice to share learning and knowledge amongst team members.
3	Scope of project over-ambitious	low	medium	· Strong Project Board involvement to provide realistic and pragmatic project guidance. · Early refinement of detailed work packages in consultation with stakeholders represented on Project Board. · Approach to project has been to identify a mix of deliverables covering working enhancements, feasibility studies and designs to support future work.
4	Lack of buy-in, engagement or commitment from internal stakeholders	low	high	· Very high level commitment at senior levels in Genetics and IT Services. · Issues with and priority of addressing research requirements well understood within UoL. · Strategic importance of developing integrated HALOGEN database well recognised.
5	Technology-related failures	low	low	· Experienced in-house technical resource available to help with design and implementation of technical solutions. · Objective is to exploit existing data management infrastructure within IT Services and UoL. The technical solution will be aligned with the UoL IT Strategy. · The evaluation criteria for any new infrastructure components will be weighted to reflect the need for ‘well proven’ and ‘robust’ solutions wherever possible.
6	Lack of relevance of lessons learned to wider JISC/UK RDS Community	medium	medium	· Involvement of JISC and UKRDS on Project Board to align initiatives with broader requirements of the HE community.