[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus,

Thank you for your message.

I note you have changed the handling of GPGSV which should resolve that issue.

The Odometer function appears to work as expected. I took the Pocket PC and GPS Receiver out in the car as I'm temporarily unable to cycle.

Before testing, I deliberately ran the GPS Receiver battery down, so it would fail whilst logging. After failure, GCC displayed 'impossible' data as expected. Converting the .gcc file to a .gpx file and viewing the data points shows erroneous data points at the end as would be expected, but time delayed after the other points which was not expected. Deleting these erroneous data points naturally corrects the .gpx file. Erroneous is perhaps a better word than corrupt to describe the effect in this instance.

It is similar to the file already provided to you which you repaired. Further testing would be needed to find why the apparent time delay occurs. In this failure mode, a repair function like you mentioned you wished to create, would seem to involve just deleting as many data points as required from the end within the .gcc file.

In the absence of such a function at the moment, feeling adventurous, I attempted out of interest a rough and ready repair of the .gcc file myself without any knowledge of the file format or it's structure, and was actually partially successful. The 'impossible' data is repaired and correct information shown. However, it seems the file structure is incorrect as an error when opening the file is displayed 'File has been closed incorrectly. Do not continue this file!' Perhaps there is a checksum or similar.

Both files are attached if you are interested.

I am awaiting a replacement GPS Receiver. I will test the behaviour with that in due course, and carry out some further testing to determine what happens during other failures such as Pocket PC battery failure, crash, or running out of storage space, and what recoverable data remains in the .gcc file in those events, and whether storage on SD Card or Internal Memory is relevant.

If needs be, I am happy to attempt to write a simple standalone script myself to provide periodical dual backup and sequential overwrite, with automatic stop when loss of GPS data is detected. This will facilitate recovery out on the ride. I don't expect just two additional files that can be deleted as required to be a problem, or there to be any significant usage of resourses. I expect this to provide robust protection in all but hardware destructive failure modes.

I note you have not heard of such issues being a big problem. My observation would be it is possible, probably likely, behaviour differs dependent on the hardware or combination of hardware in usage. In addition to that, how many of the tens, possibly hundreds of thousands of users that have downloaded and installed GCC ever provide any feedback to the developers of any kind, having carried out any significant testing, or long term usage, using the software seriously or in such a way it would even matter to them if issues were encountered. If the activity level of the programs official program forum thread refered to a contact point in the help file is an indicator, it is relatively very few users that provide feedback. The issues may not be that uncommon at all, it might just be taking the time and making the effort to report them is uncommon.

I have an observation regarding the setting in Options > GPS > GPS activity: On my system running 4.9 beta 5, whatever is selected affects the displayed update frequency of the time h:m:s on the main screen.

Having always logged every second until now, and seeing the time display increment every second as one would expect of a time display that has seconds displayed, nothing is apparent.

Change the log interval to anything other than 1 second and the time display is affected accordingly. I don't know if that behaviour is actually intended for some reason, but if it is intended, I don't know why that would be.

Keep up the great work. I for one appreciate it and look forward to the next beta or full release.

low.flying.pigs