tru-traffic.com

I have to do a small conversion to import a Geologger file. The "file format presets" has a GeoStats TravTime & Geologger format but it doesnt seem to work. Can you look at my csv file to see if it needs some help?

The following works on my system without problem:

1. Right-click on list of Trip Logs and choose Import Trip Log...
2. Select the .csv file and click Open.
3. In the list of Presets, choose "GeoStats TravTime & GeoLogger"
4. Click OK.

This seems to import everything correctly with the possible exception of the time zone, which defaults to UTC and which you may need to manually override before clicking OK.

If this doesn't work on your system, then please describe what symptoms you observe.

Regards.
Greg

I was able to reproduce the problem.

Instead of importing the file directly into Tru-Traffic, if you first load the file into Excel, then copy and paste it from there into Tru-Traffic, then you hit an error and the import fails. It seems that this sequence changes the column delimiter from the expected comma (CSV) to a tab (TSV), and Tru-Traffic is still looking for the commas.

Ver 10.0.7 will fix this.

In the meantime, to work around the problem you can either

1. Import the file directly into Tru-Traffic, as in my previous post, or
2. After pasting the data copied from Excel and choosing the GeoLogger Preset, manually change the column delimiter to tab before clicking OK.

Regards.
Greg

Still importing the geologger with better success. I have been sticking to the importing rather than the copy paste. I say this next statement with great hesitation but I think we may have a bug. I have been importing geologger files when I came across some distances that dont make much sense. I fear its the conversion of the lat and long that may be causing the problem. I have attached the gps file.

When I import I get some distances that are over 1000 feet for a 1 second time increment. Do you get the same value as well?

Thank you for reporting that and for posting the file.

I was able to reproduce the error, and I confirm that it's a bug in Tru-Traffic that can occur upon parsing certain types of values from the trip log files -- oddly, the error stems from incorrectly parsing some of the times.

Ver 10.0.7 will fix this bug. Should be available soon.

Regards.
Greg