2 ideas and then 1 idea:
<p>1. <span class="caps">GPS</span> devices need more information about real-time traffic information. The best source for this is other GPSes that are also stuck in traffic. If they could communicate, they could intelligently route traffic to optimally spread traffic over primary and alternate routes. There are products that do this. iPhone and Android would also be excellent candidates.</p>
<p>2. To share this information, they need to be networked. They can form an ad-hoc wifi network when near one another and nodes with internet connections like internet phones and nodes near municipal wifi (which could be embedded into traffic lights?) can act as up/down links to a central database of traffic information.</p>
<p>3. In lieu of available real-time information, devices could sync with the central database by docking. A Bluetooth-enabled <span class="caps">GPS</span> could send its daily traffic recordings to your phone, which syncs itself to your computer when you carry it inside to home or work, which communicates this information to the internet. Pattern recognition is applied, and then traffic patterns are downloaded via the same channels to your <span class="caps">GPS</span>. It can use the traffic patterns to avoid areas of likely congestion during your route. (And you could cut out the middleman if your phone is your <span class="caps">GPS</span>.)</p>
It’s funny you should mention an ad-hoc network for GPS devices in cars.
Back at RIT I took Ad-Hoc Networking with Prof. Alan Kaminski. One of our common discussion topics was using small mesh networks in cars traveling in "close" proximity to provide mostly real time traffic data.
I was surprised that we never thought of your third point in our discussions. We were so focused on the real time data that we never even thought of recording traffic data from previous trips to estimate how busy the roads were likely to be.