I have a project that has both RTK and conventional data. The conventional data woks with the 2 OPUS points on the project just fine. The RTK data is another story. Every RTK shot appears to be 3 to 4 feet higher than their corresponding conventional points.
I've looked at rod heights, base height, instrument heights, and can't find anything that looks wrong. Even when they were sitting on the 2 OPUS points taking direct shots on the RTK points they were 3 to 4 feet off. When I look at the vector data in TBC it looks like it should work.
Has anyone ever run into this before?
Thanks.
If this was Washington State, I would say it was the difference between NGVD29 and NAVD88
I suspect that there's something not processing in TBC corectly and I just can't find it. My project is in NAVD88 and the conventional data is being process with those elevations as its starting point.
Tiglinda
I don't know if this is pertinent to your problem but one of our guys had a 1.25' discrepancy that we attributed to this issue.
Was the initial RTK base point occupied using a "Here" position? If so, you may have to delete that coordinate entry from that point and recompute the project.