Select to expand quote
Simon100 said..
So lets get this bit stright to the sdop values are a margin of error does any one have the actual formula or method used?
The only description I recall is that the SDoP values in the Sirf chips is based on the co-variance of the Kalman filter. The ublox chips give a similar value with a different name which is calculated in a somewhat similar way.
What really matters, though, is to have a good idea what the relation between actual errors and accuracy estimates. With good descriptive statistics, we can decide how to use the values properly in the data analysis.
Select to expand quote
Simon100 said..
Cant we just use a combination of the doppler and heading data to get a better aproximation, what are really the odds that the doppler will read unusually high in your direction of travel right when your doing that 2 second run ?
From everything i have observed errors come from changing angles and bumpy water not just random gps spikes.
It's definitely worth-while to look into other ways to estimate accuracy, too; # of satellites and acceleration are already used to filter out bad data points, and often work well enough for really bad spikes. But you're looking at pretty heavily processed data, and results will vary by GPS chip, device, and even chip settings.
Select to expand quote
Simon100 said..
How many examples is there of large errors in the gps readings? the only ones i have really ever seen were actually the ka72 software which has now been fixed.
If i actually put 2 of each gps on a car straight above a wheel that is reading wheel speed off an abs sensor ( above so there is no errors in corners) will people accept that as true indications of the acuracey of each ?
I have seen plenty of relatively large spikes in GT-31 data, and (I think) a few in GW-52 data. The biggest I have ever seen was a > 1000 knot speed in data from a different chip (that apparently does not use doppler speed, but is quite popular otherwise). Could have been a problem specific to the unit I had, though, which I returned to the manufacturer.
The ABS sensor idea sound intriguing, but you'd have to verify that it actually is more accurate than our typical GPS units (and probably adjust for things like tire thread etc). We are talking about single-digit percentages or less; I'm not sure if ABS sensors need to have that level of accuracy, but I don't know anything about them. I once looked into using the accelerometer in phones for this purpose, but these things are way to inaccurate; they mostly need to know where up and down is, and if you are shaking the phone.
I think driving data can be a useful first step in the evaluation. It's very easy to gather data from multiple devices that way. Just avoid the bumpy roads :-). In paired GW-52 driving tests, I saw a nice correlation between the accuracy estimates and how closely the spikes resembled each other: spikes were in sync at low SDoP values, but out of sync when SDoP increased. No big surprise, but still nice to see. Since I was driving a big van on relatively smooth roads, I did not expect to see as many spikes as I did. I'm planning to repeat this with a few additional GPS units that use different chips and electronics, but it has been too windy recently to put these together.