I have 3 control points with static data.?ÿ
I also have an RTK file where the base was setup at an autonomous location (#500) and RTK shots were taken on the 3 static points. Will TBC see this as redundancy? Or do I need to run a static session on that base point #500? When I try to adjust the network, TBC says there isn't any redundant data. FYI, the difference in location between the static solutions and the RTK data is approx 3.5ft.
Also, I know TBC has a 'merge points' option when loading files with duplicate points numbers. If I run a static session on 500 and then merge the 2, will TBC know to move the relative RTK vectors along with the base point (500)?
Wait.
What??
???? ???ª?ÿ
?ÿ
There's a lot to unpack here....If there's no redundancy, there's nothing to adjust. You say you have static data, but is it contemporaneous? Do you have post processed vectors, as in you have downloaded ephemerides and run the Process Baselines command?
RTK vectors, like any other observation, will be used in an adjustment if their status is Enabled. If the status of an observation is Enabled as Check, or Disabled, it will not be used.
?ÿ
TBC, like other post processing programs, is just a free floating bundle of coordinates and vectors until an adjustment is run. Vectors, whether RTK, PPK, static, etc. are relative and they flow out from coordinate records. Same with terrestrial data. There might be two different coordinate records for the same point in the project - maybe one from the autonomous position when static was begun, and another from an RTK observation taken at a different time. Maybe another grid coordinate from a total station observation.
Generally the user will merge points that are the same, and classify one or more coordinate records as control to make them available to fix in a network adjustment.
?ÿ
I highly recommend running through some of the adjustment tutorials, and watching the Power Hours on network adjustments and mixed datasets. I'm on my phone right now but will grab some links tomorrow morning and post back here.
OK, here are a couple of good ones:
Tutorials: Look for the "performing common workflow" section, sample datasets in there
Network Adjustment Workflows & Best Practices?ÿ Power Hour, lots of good info and recommended workflows here
Another Power Hour that goes into detail about how the computation engine works (I highly recommend this one, it might be boring but if you don't understand how TBC combines data you're basically just flailing around in the program)
Another tutorial dataset with mixed data?ÿ Good for introduction to running mixed datasets
?ÿ
The best thing to do is collect static on your RTK base point as you collected points with your rover, also you could have collected static and RTK with your rover at the check in existing static points.?ÿ
I'm guessing that you didn't turn on static collection for the base as it did RTK. Always have that turned on, it doesn't take all that much data space.?ÿ
If you didn't collect static, then your point isn't fixed in the projection so adjusting to it would create all kinds of issues.?ÿ
You can simply checkbook adjust it using your static check-ins if you don't want to return to the field and collect static on it.?ÿ
See how the three static points check, normally it will be very close to the same numbers, for instance, the ellipsoid height might be 5.02' low, 5.01' low, 5.03' low on the three points. Simply raise the RTK base ellipsoid height 5.02' and repeat with lats and longs. A rough calculation but if all the check-ins show a consistent error it works. Then recalc and see how it checks. Basically back in your base point.?ÿ
This all depends on your error budget for the project, I surely wouldn't do that for say my DOT clients.
Simply raise the RTK base ellipsoid height 5.02' and repeat with lats and longs. A rough calculation but if all the check-ins show a consistent error it works. Then recalc and see how it checks. Basically back in your base point.?ÿ
That will work, but it's far easier to just fix one or more of the static points in a network adjustment.
This all depends on your error budget for the project, I surely wouldn't do that for say my DOT clients.
Yeah, we'd get dinged for that on a lot of our projects.
Simply raise the RTK base ellipsoid height 5.02' and repeat with lats and longs. A rough calculation but if all the check-ins show a consistent error it works. Then recalc and see how it checks. Basically back in your base point.?ÿ
That will work, but it's far easier to just fix one or more of the static points in a network adjustment.
This all depends on your error budget for the project, I surely wouldn't do that for say my DOT clients.
Yeah, we'd get dinged for that on a lot of our projects.
I can't recall ever doing what he needs, to recalculate in TBC his base point from an autonomous position with RTK ties to static positions. I always collect static on the base and use that.
I can't recall ever doing what he needs, to recalculate in TBC his base point from an autonomous position with RTK ties to static positions. I always collect static on the base and use that.
Same here. It's really unusual to me, although I have had to do it a few times when things went sideways in the field for another office/region.
I don't really like it, but sometimes it's all that can be done rather than mobilize all over again. Then again sometimes we just can't meet specs, so back to the field we go.
Sometimes we learn our lesson.
Same here. It's really unusual to me, although I have had to do it a few times when things went sideways in the field for another office/region.I don't really like it, but sometimes it's all that can be done rather than mobilize all over again. Then again sometimes we just can't meet specs, so back to the field we go. Sometimes we learn our lesson.
I guess I should qualify,,,,,,,,I haven't had to do it since TBC,,,,,,had lots of similar missteps early on, each time something new came along, it was put my hand on the hot stove top more than once.?ÿ
Thinking about it I believe the OP should check the base and be sure that there isn't a static file sitting in it for that day before heading back out. The survey style needs to be set-up to collect every time.?ÿ
Life gets a lot better a lot faster when you stop trying to hammer that square peg into that round hole, eh?
Life gets a lot better a lot faster when you stop trying to hammer that square peg into that round hole, eh?
I phrase it differently, but that is one of the first concepts I introduce when running training classes for field & office software: the code/software doesn't care how you used to do it in another program. There's a path of least resistance to get what you want out of a software package - don't make it harder on yourself, just approach it with an open mind and problem-solving mentality.
If you understand the fundamentals of data collection and processing, almost any of the modern field & office programs will work for you. Some are easier to use for certain functions than others, some are a little more "black box" but it's not hard to figure out how to get what you want out of them.
It does take time, though. We tend to be overly optimistic at judging how fast we can learn something.
