![]() ![]() The first thought in support of 180-second occupation time would be multipath detection/mitigation. Six or more GPS satellites are being tracked with a low PDOP.It is clear of multipath-enabling obstructions.I scratched my head on this one, and even checked with a few GNSS engineer friends of mine about the upside of occupying a point with RTK for 180 seconds (assuming a 1 Hz rate) rather than 30 seconds, or even 15 seconds for that matter.įirst of all, there are several assumptions in this conversation: The reader offered that he “couldn’t imagine that we are getting a good solution with anything less than 120 epochs.” I realize that most, if not all, manufacturers advise (or design into their software) that 180 seconds of data is sufficient for an RTK shot where the purpose of that point is to establish secondary control. ![]() I’m not referring to the topo type of point where you’re collecting somewhere between 1 to 5 seconds (and averaging) of data, but rather the RTK shot where you want the highest confidence and accuracy in the RTK position. The discussion has several points, but the one I’d like to address in this column is the occupation time for RTK points. It seems that most GPS/GNSS users have developed their own opinion based on their own experience. A reader wrote me about occupation times for RTK work, and it’s spurred a conversation I think will be interesting to you and perhaps a little controversial. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |