On a related note, are there any tools out there that can convert GPX to FIT file format? I can create some GPX-format test data for my app, but I need some way of converting to FIT-format for the simulator.
I've tried GPSBabel (reads but doesn't write FIT) and TCX Converter (claims to write FIT but doesn't give an error message or write the file).
Thanks, but really I'm looking for a quick & simple solution. Can you transfer a GPX track to a Garmin device and internally some Garmin software converts it to a FIT file, which you can then pull out of a folder somewhere? I've read some suggestions that that might be the case, but haven't found any details.
FIT File Repair Tool? I've got a license and it certainly allows formats other than FIT to be input/output.
Is the GPX file just position info though? If so there would be no FIT(ness) elements to convert I suspect...
Thanks! that does look useful. Yes, for this app all I care about is the position info. My current FIT files (off a real device) take up to 6 hours each to run through the simulator, so anything I can do to speed that up will be a win!
It would be great if the simulator had a feature to playback at 4x, 8x, 16x real time speed.
Thanks
So is it possible? I have a technically working idea for stopped time, but I need to run it through several options. Several minutes to test each case sounds boring. :)
It would be great if the simulator had a feature to playback at 4x, 8x, 16x real time speed.
Thanks
We've discussed this, and it's something I would personally like for testing purposes. It's on the road map, but I don't yet know when it might get added.
This would be really nice to have :) If you're playing back a .fit that was recorded with smart recording changes in lat/lon can be a bit to show, and I also test with a few .fits that have 10 hrs of data (1s recording) that take a long time to run through.
The main thing here is that we can't just play the file back faster. That will just cause the data to progress through the file at a faster rate, and doesn't change anything about the rate the data is processed by your app. If you simply play a 1/sec FIT file back at 10x speed, you will just miss 9/10ths of the points.
To add this type of feature properly, we would have to make the entire simulator fast forward at the accelerated speed, including things like system timers and time of day, which is pretty difficult. We can just accelerate the data and the compute function, but that could cause issues if an app attempts to compare any times to the rest of the system.
