To begin collecting our data for the drone strike API, we needed a method of implementation so that this could be achieved. A lecture that was most valuable for this was taken by a guest lecturer Guy Garrett who devises methods of data visualization for business. As an example, the lesson was comprised of sorting through data sets in Excel (CSV files), which came from an open source website. In this instance, the group decided to illustrate the link between university students and drunken admissions to hospital, through being intoxicated, on the NHS. Not surprisingly, the evidence showed a direct correlation between the two.
Once the method for collecting data was apparent, we found the API that recorded Drone Strikes in the Middle-East as they occurred (this can be found here). This helped the project take shape as well as referred to the real-time aspect of the brief criterion. The API used wasn’t a CSV file in this instance, but instead, it was a JSON file. The information contained many aspects – the more pertinent being: casualty names and numbers, global location and additional information relating to the strike. Now that the API was collected, a means of displaying the data was needed. The perfect solution seemed to be creating a customized Google map with an overlay, designed to look like the Heads Up Display (hud) of a Predator Drone unit. Below are two image examples of the finished product, highlighting what the hud displayed looks like as an overlay, for the customized Google map.
(Image source: Tailored HUD overlay design)
(Image source: Google Map of strikes)
At this point of the project, the group identified just two technical difficulties. Firstly, the configuration of the hud overlay on the Google Map was not able to be adjusted regarding the zooming in and out; which would have made it more variable, realistic and overall reactive. The other issue was that the information tab that displayed the drone strike information didn’t allow customization and therefore remained plain. The correct information was displayed and updated from the API used – meaning it was a success.
The next area to highlight was that of casualties and compensation/condolence claims collected. Case studies showed approximately 8 people that were killed in thorough detail as a consequence of being in the wrong place at the wrong time. This is where the project comes to its own as it is a testament to collecting the invisible: information about someone who no longer exists, ultimately making them relevant one again. Below are two image examples of case studies and claims collected. The template used was of an official document sent by the US ministry of defense . The website that held this information for the groups documents can be viewed here.
(Image source: Case study example of a specific casualty)
(Image source: Condolence document example by the MoD)
In addition, the website of which the group sourced its case study and compensation claims documents, gave a clear indication of how much life was potentially worth in the eyes of a government driven by war. Below is a image of 3 claims to show the value of ‘life’s worth’.
(Image source: Three compensation claim examples)
My contribution to this project was:
- Gaining information on case studies
- Gaining information on compensation claims
- Providing material for the video presentation
- Applied some ideologies in the fruition of this project and throughout i.e. props for decoration (camouflage netting for the war table and display, pillow cases for participants, sounding for the display)
- Sourcing a location suitable to present the project (providing an immersive experience)
- Contributed to providing video material for the presentation off and on location.
philgiles86.wordpress.com 