I have been through the SurvCE manual 3 times and I cannot find where it explains what it is doing when you hit the "Process GPS" button under the File-Raw Data tab.
Can anyone point me to somewhere that this is explained? Or explain it to me I suppose...:-D
Just press the botton!
You will see it do something.
That is what your kids would do, isn't it?
Just press the botton!
This is the way it is done these days.
No one knows what happens, it just happens.
Sarcasm off....
LOL..I did press the button, and it DID do something..Just what it did, I am not sure, though I have my suspicions.
And you are correct, that is exactly what my kids would do!:pinch:
YES, my 2 yr old daughter confirms this.
When a button is available or in sight and anyone is looking, press the button and see what happens.
When a button is available or in sight and no one is looking, press the button and see what happens.
😛
The Process GPS command in SurvCE/SurvPC would commonly be used in situations where it is desirable to recompute Northing/Easting coordinates from GPS observations that have already been recorded. Common scenarios where coordinate positions might need to be updated could include:
- Revised localization readings
- A refined Grid-to-Ground setting
- A changed coordinate system requirement
- A revised geoid
- etc
The Process GPS command is only available if GPS measurements are detected in the RW5 file.
>Note that for all processing where new coordinates are calculated (and beginning with SurvCE 2.0), upon exit the program will prompt you whether or not to store the newly calculated points into the coordinate file. This provides the flexibility to experiment with different processing settings and options without impacting the actual stored coordinates, until you deliberately choose to do so.
--
Ladd Nelson
Thanks Ladd, That's what I thought.
I had collected a couple of points with a bad geoid for which my position indicated out of range or zero, though I did use a localization using the published coordinates of those same two points. I did not process them.
Later I removed the localization (this is not easy to do or at least not straightforward) and created and installed the correct geoid and re-collected one of the two points.
I then GPS Processed the RAW data using no localization and the correct geoid and in looking at the data, the one time point matched the published coords withing 0.1+/-, but for the point collected twice, each time was a good bit different and about a foot + off the pub coords on the second run. I'll have to re-check it to see about the first one, but it seems the ellipsoid htgs were screwy as well...
