Stunt geolocation:  Verifying the unverifiable
First Draft uses cookies to distinguish you from other users of our website. They allow us to recognise users over multiple visits, and to collect basic data about your use of the website. Cookies help us provide you with a good experience when you browse our website and also allows us to improve our site. Check our cookie policy to read more. Cookie Policy.

This website is hosted in perpetuity by the Internet Archive.

Stunt geolocation:  Verifying the unverifiable

When working on open source and social media investigations there are occasional images that at first seem as if they would be impossible to verify. The following picture, showing a 9S470 Self Propelled Command Post, was shared with us on Twitter.

The image is significant because it shows what appeared to be one of the units that was part of the military convoy seen travelling through Russia in late June 2014 that contained the Buk missile launcher Bellingcat identified as also being seen in Ukraine on July 17th, and linked to the downing of MH17.

In the Bellingcat report Origin of the Separatists’ Buk we were able to track the convoy using images from multiple sources as it travelled through Russia to the Ukrainian border.

1-LqwVobDFaENWvz5DEU9h6Q

Copyright: Bellingcat

At the very least this new image would add to the details we had gathered about the route of the convoy, and the original version of the image on VK.com already had location information tagged to it, indicating it was taken in Rossosh, Russia (50.202944, 39.510314).

However, despite having co-ordinates, it’s still important to match what’s visible in this image with other images from the ground, to confirm that the co-ordinates provided are accurate. Google Streetview images of the area are available, but the photograph appears to provide little information that could be used to find its precise location.

1-ArRwCsYqgQs3DBqf-OAYYg

However, there is in fact plenty of information in the image that can be used to match the location. First it is possible to establish the position of the camera in relation to the vehicle by examining the road markings.

The vehicle is between two sets of dashed lines, the set that is furthest away extending further to the right than the set closest to the camera.

1-9F8EVW8q6rTYqUtaA-oaVQ

In the Google Streetview imagery the same pattern of dashed lines can be seen, and based on the position of the dashed lines in relation to the solid lines the camera must be on the left side of the below image pointing across the road.

1-OtGyr9fKWmwMd7xJbm3O1Q

Google Streetview

Street markings are not unique, but other elements of the photograph match to what is visible in the Google Streetview imagery. Barely visible behind the tire of the vehicle is a white pole that’s also visible in the Google Streetview imagery.

1-Wcnv_ERiZ0KYWXLFJRI17w

Also visible in the top left corner of the photograph is a pole that also matches the Google Streetview imagery.

1-UEfdsGjoADP8ejymODJVMQ

Individually these features are not uncommon, but there is one element of the photograph that is very unusual, and confirms the exact location of the vehicle.

A crack is visible in the photograph, running through the middle dashed line, with a patch of discolouration around it that matches to what’s visible in the Google Streetview imagery.

1-Ddt0624Z4wMwPRmpnhb7vQ

Unlike other matches in the photograph this pattern of cracks and discolouration would be something that’s very unusual, and combined with the other matching element would establish this as the exact location. This shows that even when a photograph appears to provide no useful information it’s still possible to find the exact location it was taken.

Eliot Higgins from Bellingcat first published this on March 3, 2015 at https://www.bellingcat.com/resources/case-studies/2015/03/03/stunt-geolocation-verifying-the-unverifiable/. We have reproduced it here as part of The First Draft collection.

Leave a Reply