When doing kinematic work, the data processes OK when the downloads from both receivers and the HP handheld are done together, but when I try to import files loaded with an older version the raw data comes into the project with the initializations listed as "static" when they were in fact kinematic. This situation makes it impossible to process the kinematic with either version of the processor.

Remember the older versions would not allow you to initialize a kinematic session unless you logged a kinematic without turning off the receiver, then eliminated a one-second ???? between them. I know that some users had found a way with older versions to initialize the next day on a known, but I have never been able to make that work consistently.

Any suggestions?

NN,

I'm not sure I understand the problem in the 1st paragraph. I just ignored the k/s when I imported into 2.4 but I did have the D-file from the handheld in the same directory. Didn't seem to have any problems.

See your question above for 2nd question response.

Hope this helps,

Jimbo

Based on very limited experience with the way V2.5 handles kinematic data, it appears to me that the software doctors have created a confusing situation by using the term kinematic to mean one thing in one context and something else in another. As used in the general context of the Locus system, the term kinematic has come to mean stop-and-go surveying with a receiver that is continuously logging data, with the corresponding D file that contains the information the software needs to be able to process the desired portions of that receiver file and which parts to disregard.

But now with the new system, you can also log a different type of kinematic file, which is actually a trajectory. Thus in Ashtech Solutions, designating data as kinematic really means that you are interested in processing as a point each epoch of data recorded while the receiver was in motion. And in the apparent logic of the new software, even the familiar concept of the kinematic point is now considered to be a static point because it was recorded while the receiver was at rest, even though the receiver was running continuously between points.

To see this illustrated, select a portion of the rover file between a pair of points and have that portion of the file processed as a kinematic session. You will see that each epoch of data becomes a point (with fairly high residuals, as might be expected.) I suppose this could have application for roughly defining a route or center lines of roads.

Jerry

Jerry,

You have the right idea, but if properly initialized, the residuals will not be high.

Brian