Jim Frame, post: 405781, member: 10 wrote: In my world, I'd rewrite this as "I'm visiting relatives I'd really rather not hang around with for 3 days, so I found something to do that gets me away from them."
And now I have to leave early to make sure my data is OK
In the summer or 2015, we were doing a topo on a property owned by the only billionaire in the county and probably the province. He was doing a massive addition and reno to his old family homestead, turning it into a guest suite for other business types that might visit. Anyway I had one control point with known elevation and only needed to set two more points to shoot in the whole thing. Did what I could with RTK but there were areas where the robot was needed due to close to the old house, trees to locate and canopy. I set the points with the robot but always do it manually. I entered the new points into the DC but forgot to fix the elevations at the new points so they had the same elevation as the main control point, about a meter difference. Carried on getting my shots, likely about 200, that all had the wrong elevation. We sent a draft to the engineer and he didn't notice. Once my partner got to reviewing things something looked amiss and asked me to check it out. As soon as I looked at the draft I could tell things were not right. Couple of quick checks revealed my error and I went back to work at 9pm to fix it as I was pretty bummed out at making a rookie mistake.
I have made more than my share of goofs in the past but that one sticks out in my mind and likely always will.
Jim Frame, post: 405781, member: 10 wrote: "I'm visiting relatives I'd really rather not hang around with for 3 days, so I found something to do that gets me away from them."
Not the case here. We celebrated Mom's 90th birthday Thursday evening, and were just hanging around on Friday. Today we have two gatherings, the last one at home tonight with my stepdaughter & husband. Then relax on Sunday.
Mike Mac, post: 405797, member: 2901 wrote: I entered the new points into the DC but forgot to fix the elevations at the new points so they had the same elevation as the main control point, about a meter difference. Carried on getting my shots, likely about 200, that all had the wrong elevation. We sent a draft to the engineer and he didn't notice.
This is one of the reasons I almost always -- with very few exceptions -- run my raw data through Star*Net to produce final coordinates. Field goofs like that jump out and demand to be fixed.
I might have maybe misspelled a word about three years ago..
One I didn't make, but found.
Had a job replacing a bridge over a small creek and about 500' of roadwork on each end. State provided 3 control points on the shoulder of the road, one at each end and 1 close to the bridge. Put in cl bearing offsets and cl bridge offsets from the control and everything checked. Told the bridge guy to use the cp next to the bridge for his bm. I didn't go back until they had the deck on the bridge. First thing I noticed when I drove up was the new bridge was about 5' above the existing road, which wasn't what I remembered. I asked the bridge foreman if he' d noticed anything odd, a quick check of the plans showed the new was supposed to be about a foot higher than the old. Also showed the existing road profile adjacent to the control points was about 5' above the control points, which were actually about level with the road. Apparently when they did the original topo they assumed an elevation, then went back with gps and got elevations on the control, but never adjusted the topo to match. Had to redesign and find some borrow dirt to raise the road.
Wow! Send in the tall boats.
Next time a flood is headed your way you will know where to move your valuable possessions to protect them from the rising water.
I made a mistake once.
I thought I was wrong.
😉