Bushnell Backtrack D-Tour

[Oluffen]

I thought I posted a reply just a moment ago, but it didn't show up here.
Sorry if it now becomes multiple messages...

Thank you Matthias for your information I will give the demoversion of Fugawi a try.
You might be right about the legal aspects of the btk-file but I don't understand way Bushnell choose to use this format. They certainly would sell more of the Back Track D-Tour if the data recorded with it where usable in ordinary GIS. And even if the format is owned by a company, the data recorded by me is definitely mine!

Lorry´s recent input to this might be interesting, but makes me regret that I stopped learning programming a loooong time ago...

[kumo]

I thought I posted a reply just a moment ago, but it didn't show up here.

The forum has a trap against spambots. Too many links or other items (don't know the rules) and a post is rejected.

[IlmariKrebs]

http://www.degruyter.com/dg/viewarticle....eventlink/$002fj$002farsa.2011.46.issue-4$002fv10018-012-0005-y$002fv10018-012-0005-y.xml?t:ac=j$002farsa.2011.46.issue-4$002fv10018-012-0005-y$002fv10018-012-0005-y.xml

Would seem to be useful given that the thing has a Sirf IV in it.

This seems to be a very long shot.

[IlmariKrebs]

There seems to be an other workaround: upload your files with
http://bike-gps.idrz.de/updates/Btkup.zip to another gpsdevice and load the data back onto the computer.

This site does not seem to be available anymore. Try to search for Btkup.zip.
Maybe gpsies.com can point you to a site.

HTH

Ilmari

[Lorry]

This seems to be a very long shot.

It's probably the only shot we have though

I don't think there's too much of a legal issue - Working out a log file format isn't really into the realms of grand hackery. It's even worse now that the official software won't read any logfiles off my device any more, I can only use it at all with saved tracks.

The Backtrack software is weird - It seems to be mostly written in Flash and the tracks it exports to its window on Google Maps isn't exportable or even at all usable - So I don't think the Fugazi route is going to be of any use at all alas.

The SiRF route is probably the best bet - My assumption is that it is getting a payload from the chip and writing out the data it needs pretty much as it gets it with very few conversions in a fixed format - That said there seems to be quite a bit of waste in there; it's odd.

[Oluffen]

I found something about a software named >>>Fugawi<<< which may be able to read *.btk files.
And this 'Fugawi' software appears to have a Google Earth plugin that is able to export data in *.kml format.

I gave the Fugawi software a try yesterday. At first I was hopeful because it rekognized the btk file format, but when I tried to load the file I got the error message "division by zero"

I used Fugawi version 4.0.12 and maybe there is better success with another version?

[kumo]

I have no idea. I found this via Google (based on your request) but never used it.

[routeconverter]

I thought I posted a reply just a moment ago, but it didn't show up here.
Sorry if it now becomes multiple messages...

Actually Akismet classified the reply as spam. Sorry I didn't find out that earlier.

[throwaway]

I don't know about the file you specified, but I have been trying to figure out how I could edit Waypoint.gtk to use this thing for geocaching. Made a breakthrough today, and decided I didn't want my top Google result for trying to figure this out to not to have any good info. It uses a 64 bit floating point format for latitude and longitude.

Lat-Lng pairs are (relative addresses in that file):

* 0x18, 0x20
* 0x30, 0x38
* 0x48, 0x50
* 0x60, 0x68
* 0x78, 0x80

The four bytes (out of eight) that immediately follow each pair look like they could be a 32-bit UNIX timestamp, but for some reason they're all the same for me, at least in the Waypoint.btk file.

[Oluffen]

Sorry for my limited knowledge in this area, but what does this mean? Does it gives us a clue of how to interpreat the file to get us the waypoints in a standard format?

Regards,

I don't know about the file you specified, but I have been trying to figure out how I could edit Waypoint.gtk to use this thing for geocaching. Made a breakthrough today, and decided I didn't want my top Google result for trying to figure this out to not to have any good info. It uses a 64 bit floating point format for latitude and longitude.

Lat-Lng pairs are (relative addresses in that file):

* 0x18, 0x20
* 0x30, 0x38
* 0x48, 0x50
* 0x60, 0x68
* 0x78, 0x80

The four bytes (out of eight) that immediately follow each pair look like they could be a 32-bit UNIX timestamp, but for some reason they're all the same for me, at least in the Waypoint.btk file.