My Co-Worker brought in the as staked data from his Trimble Access DC. I noticed when processing that he used the wrong zone for Oklahoma. Being as he calibrated to the section line to a local coordinate system based on 10,000. Will his as staked points be wrong or will the calibration have taken care of that by reducing it to local coordinates? I have never seen this before so i am unfamiliar with this situation, any help would be appreciated.
A great deal of my work is located in the area that the two zones overlap and this happens to me all the time. As far as I can tell, I haven't seen any adverse effects.
I'm by no means an astrophysicist...but if you localized to a local grid plane, I would assume ever' little teen be copasetic.
I did set a job up once in the DC and when I tried to fire the base receiver up I was given some error like "location is outside the coordinate zone"...Instead of choosing Oklahoma 3501, I was in Zimbabwa or somewhere on another continent. The DC apparently didn't like it.
Thanks for the info man, i didn't think it would but you can never be too sure.
Just keep your eyes open, and your ear to the ground.
When in doubt, make a redundant measurement.:-D
Cheers,
Radar
Radar
What the heck does that avatar mean?
Radar
something to do with Freemasons.
Radar
you have joined the secret society of stonecutters, number nine zero eight, splitting the stones of ignorance that obscure the knowledge and truth
now let's all get drunk and play ping pong
The biggest thing to watch is the difference between grid & ground inverses on the DC. I have seen crews mess up localizing before and a 500' line would vary by +/- 20'. You still have good data, just make sure that you use the correct grid/ground setting.
The easiest way to fix this is to import the data into TGO or TBC and re-define the parameters & projection. The DC is really only working in WGS84 anyway.
This has happened to us several times mostly when it's been a rental or loaner DC. It can reaaly give you fits until you realize what's happening.