We have static pretty much down pat and are getting good results even in marginal areas(big oaks and pine trees).

However stop & go is another story.

First off we have three recievers and are trying to use double bases and known point init for the rover, all set and adjusted on a previous session.

Our main question is when we bring in the data and process the vectors most(80%) are marked as 'fail-partial'.
We are using 5 sec interval with 1 min occupations. We set all previous control points as known in the Promarks and try working from these.

Basically we are not getting the warm and fuzzy with stop & go that we get from static.

Any comments?

CJ

Stop and Go is a lot hairier than static. That said it can give excellent results. First, was your alarm set to "on" on the kinematic rover? You really want this on as it will indicate that you need to do a re-init (which is just a stop and go shot on a known point). Second, how many sv's were you tracking? This gets into two possibilities. Obviously you get better accuracies with the increase in sv's, but you also have more flexibility in cleaning the data back at the office. I would suggest with the partial solutions that you look at increasing your mask by 1° increments until you get a fixed solution (provided that the mask is still under about 25° and you still have at least 6 sv's in the solution). Third, I have seen very rough kinematic results before caused by solar storms. Be sure and check the space weather. This is good advice for static work too, but nearly a must for kinematic work.

All that said, I would strongly suggest setting up a "play ground" and work with the stuff until you feel comfortable with what it will do and under what conditions it will do it.

Hope this helps,
Shawn

I vote for a 2 second epoch interval, too.

CJ, heed what Shawn and Mike have told you.

Marginal conditions are also mentioned (oak and pine trees)... stop n go GPS falls apart quickly if you are working around obstructions. It works best when there is a wide open sky view throughout the project area since you must maintain lock as you travel from point to point or else re-initialize often.

Listen to what Shawn says good advice same advice you will get from Phil at Thales. Try recon a few way points ahead of time and see what kind of sats you are getting. This will also aid in the office in where to be when and how to move between points and maintain lock. Bottom line plan, plan, plan, and you'll get great results.

Good Luck

You already got good advice all around. One more thing. Save years off your life by figuring out how to make it work without spending money on gasoline.

Learn how to make it work close to home.

Compare sessions that work with sessions that fail so you learn to recognize things that go wrong in the field.

Sometimes a Stop&Go can be saved with a static observation on the first failed point so it turns into a control point.