I'm doing a half mile long design survey of utilities and improvements. I've established control throughout the project using a combination of RTK and post processed fast static. Fairly tight stuff. Using a State Plane projection in Access running on a TSC3. Go out there this morning and set up the S6 on one CP and back sight another and do a back sight check. Misses by 1.2'. Okkkkayyyy. Something's up. Store a new point on the back sight and stake out to a third control point to try and figure out what in the heck is going on. Tell the S6 to turn to the point and the angle is substantially off. Something is really gobbed up. Put away the S6 and put the R8 base up on our primary control point for the project and Access is telling me my State Plane value for the point exceeds the tolerances for the autonomous position, so do a single point localization to just try and pin down the problem. Go back to the control point the S6 had been on and take a shot on it and inverse the original cp point and the new point back to the base point. The two distances match within .01', but the bearing is rotated 27-23-41. I double check I'm using the correct projection. I am. At this point, I'm like WTF. Switched back to an earlier coordinate file for the project and everything works like a charm. Something about that new coordinate file was just hosed, and I don't know what or how, which really bothers the bejesus out of me. It was like it had been somehow, some way, corrupted by Access . I check all the coordinate values when I get back in the office and everything appears to be just fine.
Any Access users out there have any similar experiences? Any insight? I'm fairly new to Access but after doing this a few hundred times without any major issues, to suddenly have Access drop me on my head like that ... I don't rule out operator error of some sort. Just like to pin point what in the heck happened.
Williwaw :-S out.
That made my tummy a little ill to read. I hate when those mysterious troubles creep up. Also, I am no help with the Trimble way, sorry man.
Do do do do. Do do do do. (Twilight Zone, right?)
Access decided to swap my northings for eastings and vica versa. I really hate it when that happens. My whole world gets turned upside down and turned around, leaving poor Willy very confused. :bored:
Williwaw, post: 323773, member: 7066 wrote: Access decided to swap my northings for eastings and vica versa. I really hate it when that happens. My whole world gets turned upside down and turned around, leaving poor Willy very confused. :bored:
That's what it looked like to me.....
I've seen this before; too. Can't say when, where, why or how.....I try to block out bad memories....:excruciating:
I have had this before. The "units" settings in job properties seem to to determine the order of CSV co-ordinate import.
The settings on "export fixed format > CSV" control the order of CSV co-ordinate import.
It may be that you have an incorrect setting somewhere.
My "state plane" co-ord system has similar eastings and northings where I live so can be confused.
