The Summer of James has begun. I will be leaving Mountain View in the next few hours heading toward Pittsburgh. If you're bored and want to follow along at home, here's a map of my recent progress: http://where.jo2y.com/
You emailed me weirdly. It didn't send it to me directly. It seemed to go to some mailbox on livejournal itself. I planned on replying eventually, preferably before Friday. Last minute packing sucks. I don't _need_ to stop in Columbus because it's so close to Pittsburgh, but I can if you want me to. I'm trying to get to St. Louis by Thursday, from there it's a 9 hour drive to Pittsburgh. If you wanted me to visit, it would be on Friday. Maybe dinner instead of staying the night?
If you get lost, you can stay at our place in Seattle. The cost is free if you write more about what tool you're using to post your crumbs (see attached link).
I can post more specific details eventually. On the computer in the car: I use GPSD, gpspipe and cronolog to create an nmea logs from the gps that is split into a new file every minute. Then I have a perl script that looks every minute to see if there are any new files that aren't being written to currently. If it finds any, it compresses them, and then uploads them to a server. On the webserver: I have another script that looks for new uploads, when one is found, it verifies a sha1sum, then uncompresses it. For each line in the file, it saves the nmea sentence into a postgresql table specific to that sentence. I also collect the long and lat from the GPRMC sentences and pass them to Geo::Google::PolylinEncoder. That module takes an array of points, does some math to remove redundant points, then returns an encoded string per these directions. That string is also inserted into the database. It looks like he just released a new version today. I'll need to see if fixes the broken line problems I currently have. In theory all of the
( ... )
It's been raining almost constantly since I left New Mexico. In some places between the downpour and the splashing from 18 wheelers, I had no visibility. Texas only lasted about 2 hours including my 20 minute nap. Oklahoma had a nice thunderstorm.
Comments 9
Neat app.
Reply
Reply
I emailed you a while back: did you need a layover in Columbus, OH?
Reply
I don't _need_ to stop in Columbus because it's so close to Pittsburgh, but I can if you want me to. I'm trying to get to St. Louis by Thursday, from there it's a 9 hour drive to Pittsburgh. If you wanted me to visit, it would be on Friday. Maybe dinner instead of staying the night?
Reply
No need to make a special stop: I was just offering. Probably better to drive the extra 3.5 hours to Pittsburgh.
Take care!
Reply
Reply
On the computer in the car:
I use GPSD, gpspipe and cronolog to create an nmea logs from the gps that is split into a new file every minute.
Then I have a perl script that looks every minute to see if there are any new files that aren't being written to currently. If it finds any, it compresses them, and then uploads them to a server.
On the webserver:
I have another script that looks for new uploads, when one is found, it verifies a sha1sum, then uncompresses it.
For each line in the file, it saves the nmea sentence into a postgresql table specific to that sentence.
I also collect the long and lat from the GPRMC sentences and pass them to Geo::Google::PolylinEncoder. That module takes an array of points, does some math to remove redundant points, then returns an encoded string per these directions. That string is also inserted into the database. It looks like he just released a new version today. I'll need to see if fixes the broken line problems I currently have. In theory all of the ( ... )
Reply
I'm wondering what will be worse -- driving through the dry counties of Texas or being in Oklahoma.
Reply
Texas only lasted about 2 hours including my 20 minute nap. Oklahoma had a nice thunderstorm.
Reply
Leave a comment