The H was off due to a fat finger of the coordinates and the V was off due to inputting ft and not meters?ÿ
More reason to use only meters all the time...until final delivery of coordinates.?ÿ
I got some data recently where they did several VRS occupations, repeated them 3 times each, then did static because the agreement between occupations did not meet the criteria, which was in meters, and they were looking at feet.?ÿ
?ÿ
The H was off due to a fat finger of the coordinates and the V was off due to inputting ft and not meters?ÿ
Surveying can be a humbling profession.
Years ago before Google Maps and Bing Maps were even a twinkle in someone's eye, I was working on an as-built of a 180' mono-pole cell tower in Memphis, TN.?ÿ The drawing and 2-C letter went out and all was good for a couple of years.?ÿ Then the boss's phone rang one day and I got called into his office.?ÿ We'd recently acquired a licence for Delorme Maps and the boss had already keyed in the lat/lon that the caller had given to him. It seems that I'd moved the tower from just off the Nonconnah Parkway in Memphis to somewhere in northern Mississippi with the flick of a single finger.?ÿ I desperately hoped that the caller or the boss were wrong but when I went back through my calcs and worksheets I realized that it was all me.?ÿ When I keyed the state plane coordinates into Corpscon to get the lat/lon for the center of the tower, I had transposed the thousands and ten-thousands digits in the northing.?ÿ The resulting latitude was several tens of thousands of feet too far south.?ÿ
After that, I've always run the calcs both ways to look for blunders (sp -> lat/lon -> sp).?ÿ If the input coordinates don't match the output, you probably shouldn't trust the lat/lon.?ÿ I also input the lat/lon into DelormeGoogle MapsBing Maps to be sure that I'm at least in the correct state.?ÿ ??ÿ
