Site Day

I had hoped to have this survey to do when (as in January when I did the tender visit most folk were working from home or whatever and it was very quiet) and it was easy to get set up around the site. As typified by this photo, this van got parked here a few seconds earlier (right in the way and the driver disappeared. If it was easy they would probably do the survey themselves, I always say.
Later in the afternoon I had a really weird software glitch on the controller R is holding. Difficult to explain, a file that holds code settings got corrupted. I had an earlier version controller in the car which I happen to know has the identical file. Awkward in the rain, but I was able to transfer a copy over by bluetooth and drop it into the system folder where it needs to live, restarted the survey program and it was happy again.
Code, think name or description flag. Each survey point has a name and points of the same name get treated similarly. In addition you can have numeric increments of each code; TRK1, TRK2, track 1 and 2 where all TRK1s get joined together in chronological sequence.. The survey continues like a game of -join the dots- to create the map. Young engineers are often tempted to follow one line at a time but this approach is very inefficient. Good use of codes sees you pick up everything as you go.
As an interesting aside the house in the background was R's former family home when he was at school. He knew the surroundings intimately and noted many changes.