Cemetery recording

Yesterday we learned some relatives had been buried in a nearby cemetery, and though there was a picture of the gravestone on line at the eGGSA site, the inscription was faded and hard to read. The Silverton cemetery was close enough, so we went to have a look. The grave was of Karl Jacob Denneville and Gladys Adelheid Dennewill -- if you are interested in what we discovered about them, check our other blog here. But in this post we are describing how we went about recording them.

It seemed like a good opportunity to come to grips with the BillionGraves Android app.

In theory it is simple: take a photo of the gravestone inscription with a cellphone, upload it to the BillionGraves database and there it is, waiting for someone to look at it, with the GPS coordinates showing its exact location.

We'd tried it a couple of times before, when we'd been on holiday far from home, and seen a grave of some relative. But it somehow never seemed to work. But this was close to hom. I printed out the instructions, and carefully read the web site on the computer at home, so this time it would surely work. It didn't

The pictures wouldn't upload. I thought I'd delete them and try again. The application crashed. It also seemed locked on the wrong cemetery -- it showed Mamelodi cemetery, which was about 4 km away. There is a thing for adding another cemetery, but when you're actually in the cemetery, looking at a squitty little screen on a phone in bright sunlight, it's easy to miss that option.It has a thing for linking two or more photos of the same gravestone, but it is also hard to see what pressing the link has done, if anything.

So we took pictures on ordinary digital cameras as well -- no good for BillionGraves, because they don't have GPS positioning to inpoint the location of the grave.

We went home again, and then with our WiFi were able to upload the photos. And, after a lot of fruitless efforts, we finally managed to enter a new cemetery into the database.

With the photos taken on ordinary cameras we were able to record them on the Find-a-Grave site, where one has to do everythin g manually, but at least you can see whether it has worked and what is there.

So both sites are very useful. If BillionGraves is working as advertised with no glitches, then it's brilliant. You can zip down a row at a cemetery taking a photo every couple of seconds and upload them every 5 graves or so.

With Find-a-Grave you have to upload each picture individually, link it to the right cemetery, and type in the name of the person mentioned on the stone. Even at it's best, it's more work. But it's reliable.

BillionGraves is quick when it works well, but slow and frustrating when it doesn't. But it's a good idea and deserves support.

I have one recommendation to make. If you join BillionGraves, look first at the Transcription option. That lets you index people and transcribe epitaphs that other people have photographed. The value of that is that you can get a better idea of how the site worls, and become familiar with it. It could be that that will reduce fumbling and floundering when you get to a cemetery and you're not sure what is happening.

The trouble is that, like the recording of graves, when the transciption system works, it works well, but four times out of five I get the message "Oops... we just had an error on our side. Try again later"