Is There Linux Trip-Planning Software?
Spiral Man writes: "There has been a lot of talk lately about Linux on handheld and embeded device. One interest of particular interest to me is in-dash computers for cars. Probably the most important app for one of these (aside from the CD player) would be a navigation and trip planing package such as DeLorme's Street Atlas, and Microsoft's Streets USA. My question is: Are there any apps, or even plans to write apps like this for Linux. Preferably these would use a commercial, or at least well updated, street database, and would have to be able to track you current location with a GPS." Especially considering the coming flood of GNU/Linux-based handhelds and dashboard computers, this question will be one of the toughies for folks who want to use Free software wherever possible, but who also want the capabilities in applications like Streets USA. Are there any competitors out there in the Free world?
The problem is not so much the programming, as there are several good public-licensed Geographic Information Systems softwares out there that could be cut down to do the job. The problems is where are you going to get the mapping database?
The owners of the database need to have a huge number of copies sold in order to cover their considerable cost in labor for cleaning up raw data. Maybe what is needed is for the software publishers to piggyback a linux program on to their existing Windoze package.
*whup* "Get along, little electrons. Heeyah!"
Use Yahoo Maps. Not platform dependant, easy to use, huge map database. Click "maps" from http://www.yahoo.com
This was added to woody just yesterday - looks very decent. It doesn't do street-to-street routing, but looks pretty good for city-to-city stuff. Has CLI, newt, and gtk interfaces. Grab the source here.
I just checked 2 routes on Yahoo! Maps, one trip that I've personally driven completely and another that I've done about halfway. One was from my home to Arlington, VA. Where's it take you? Across most of the major highways in southern Pennsylvania, then right down the Baltimore-DC corridor. And then (get this) right through DC and down Pennsylvania Avenue! Get comfy - you'll be sitting still for a while there. I plotted my own route which was faster, shorter, and had much less traffic.
The second route was Boston to Seattle. Still a lot of excess road-switching, and oddly, it didn't route through Ontario between Buffalo, NY and Detroit, MI, which is my preferred route. You miss a number of cities going that way. Also, it keeps you off of I-90 for the majority of the trip, which just about the most direct route.
I'll be sticking with paper maps for a while. If you've got someone riding with you, let them read. And whether you're solo or driving with someone, a stop every few hours along the way to get out and stretch your legs is good for you anyway.
you could always run one of the windows only trip planning software programs with WINE, though i don't know if they would run at all or if they would be too stable
just an idea
Two wrongs don't make a right, three lefts do!
From the Netpliance I-Opener hacking board: Great GPS implementation has both Win and Linux stuff in it.
This may be more to the point: GPS for Linux on the same board. Mentions Mayko, which is what I will be trying on my vehicle-mounted I-Opener, but on FreeBSD. Not exactly trip planning software, but covers the navigation portion of your question.
Visit DC2600
Eve Fairbanks says I drive a hybrid!LOL
There would be a legal mine-field getting hold of this infomation for free. The money put into these surveys needs to be re-couped somehow.
Back in my WABI days, we found that Delorme Street Atlas was so well-coded and clean that it ran with extraordinarily few problems on WABI.
I've never tried it on WINE, but I suspect that it would have a pretty good shot there, too, depending on the current status of the WINE implementation.
The reason we liked Delorme so much was that most of the applications we tried to run on WABI turned up at least a handful of compatibility issues that we had to deal with. Many MS applications took months of analysis (black box analysis, of course) to get them to work.
Delorme Street Atlas worked right out of the box.
Of course, YMMV, this was 5+ years ago.
1. Things are not where they are supposed to be. In the files for Alaska, points were often plus or minus five percent. The town of Bethel was off by about eight miles.
2. Numerous duplications. We found one subdvision in Anchorage was duplicated three times, in slightly different spots.
3. Don't know where they got the base maps, but I figure it was a historical archive. The towns of Whitney and Spenard havn't existed for thirty years or more...
I sure hope they get better with practice.
*whup* "Get along, little electrons. Heeyah!"
I plotted a route to Arlington, VA, not Washington, DC. There was no message about "city-center" in any case.
How hard can it be to plan a trip? I just kind of get on the road and head toward my destination. I can get to practically any location in the Continental US in 32hours or less. Sometimes I do use a road atlas (hard copy). I find that this method is more efficient than any of the software packages that I have seen or used.
Brought to you by Frobozz Magic Penguin Fodder.