Raw Trip Data (CSV)

The software I used on the trip, called obdgpslogger, writes raw OBD and GPS data to a SQLite3 database (obdlogger.db). The final database was 83 megabytes, or 28 megabytes when zipped, which is too large to post at Google Sites, where I host files. Obdgpslogger has a utility, however, which will convert the database into a CSV file, and I have done that, and zipped the result, which produced a file of only 8.5 megs, which is under the 10-meg limit.

Download the raw trip data in CSV format (zipped).

Download the complete trip map in KML format (zipped) for use in Google Earth or Google Maps.

Also, the man who wrote the obdgpslogger software has used my trip and my data as an example of how the software can be used. Take a look at the page on his site.

Email me if you are interested in getting the raw trip data in the original SQLite3 database.

Posting the whole trip map was the end goal for this particular blog, so I consider it now complete. It is possible that Rinarledge.com will someday become a blog generally for the Rinard-Arledge coalition, but for now, good nite and good luck.

Generated The KML

I got in contact with the author of the software that I use to generate the route maps. He agreed that the program seemed needlessly slow. He looked into it and suggested I run a couple indexes on the database holding the data:

create index idx_gpstime on gps(time);
create index idx_obdtime on obd(time);

After this, the program runs in approximately one minute, versus something like one week before the optimization. That works out to a speed improvement of about ten thousand time. Wow.

So I generated the file and it is about 25 megabytes, which is too large to upload to the same place I keep the other KML files, and also too large for Google Maps to accept. I don't know what to do about that, but for now I'm just going to do nothing.

Problem Calculating The Trip KML

Altogether I took 505 trips in my car during the journey, where a trip is defined as turning on and then off the engine, for no matter what length of time. I would usually calculate the most recent couple dozen trips into the multi-colored map shown at the top of the page, because that was about the amount I could calculate overnite, which was usually about how long I had to do the task. So to calculate all 505 trips, I knew, would take days. Three days ago I started the calculation, and it got as far as #405 by this evening, then a few minutes ago, the computer crashed. I was foolishly trying to install Mythbuntu at the same time, and also surfing the web. One of those things caused the problem.

So it'll be a several more days before I can post that data, if I can even find a way to post such a large file -- it might be over a hundred megabytes. There were sixty megabytes of raw text records in the SQLite3 database.

But first I'm installing Mythbuntu.

Fin

We made it to Madison yesterday afternoon. We have lots to deal with, many chores, plenty of stress, but we are happy to have made it here alive. The biggest problem on the trip was the water pump, which makes the whole thing pretty lucky, I think. I will finish up over the next week or so with some more posts and pictures about the end of our trip, and looking at all the data I collected.

Thanks to all the people we saw who made our trip fun and comfortable.

The Home Stretch

Ashleigh and I arrived in Chicago yesterday in the morning. We had brunch with our friends Dan and Abby, who are engaged to marry in April. In the evening we had a delicious home-cooked meal at Abby's family home. Today, soon, we will drive out to Madison, the long-awaited final destination on this ambitious trip. If we don't crash on these final few hundred miles of roads, we will have executed the original travel plan with remarkable success. Wish us luck on our home stretch.