Gluttons for Punishment? I was pretty excited about a new mashup of Google Maps, called Route You. In their own words:

We produce and translate raw route-information towards digital structured data.
We also create route-networks for GPS navigation systems. Our focus is mainly outdoor navigation for tourists, hikers, cyclists and motorbikers. During the outdoor activity, the user wants to be navigated via the most suitable and relaxing route, rather than the shortest or fastest.

We produce these kind of routes and route-networks which allow route-planning and turn-by-turn navigation for cyclists, hikers, citytrippers, motorbikers...

Ok, so the cool aspect of the site is that it would give routes that were custom catered to non-automobiles: walking, bikes, and scooters. Great! Just what I was looking for to avoid those freeway-addicted Google Maps. Easy enough: signed up, headed over, indicated I was looking for the fastest route via bike, plotted my start point and my finish point, and voila: a perfect, bike-friendly route. Right? RIGHT?

Um, No.

While the route they produced did have a big plus, in that it showed an elevation chart for the ride, it completely failed on the core competency of navigating: it directed me to a freeway. Now, I know: the site is free, and you get what you pay for, but this is utter foolishness: you specifically set yourself up as a site that is providing non-auto related directions, and you include freeway navigation? Fail.

To be fair, if I wanted to plot the whole route out, waypoint by waypoint, I could have, and it would have been very accuate. For that, however, there is another option: MapMyRide, formerly RouteSlip. Although the site has more advertising on it than a NASCAR entry, it offers a ton more in the way of calculation and automatic work. Want to figure out how many calories you burn on your ride? Done. Need to see the local bike shops on your route, in case you need supplies. Boom. Want your iPhone to automatically log your rides and send the stats to the website? Got it. They even offer training programs, and suggested rides, based on your workouts. Now THAT is a bike-friendly site.

Labels: biking, Google Maps

  ¶ 1:15 PM (0) comments links to this post

  iPhone vs. Treo: This Time It's Personal Ok, gadget fans. With the acquisition of the iPhone, and a few days to play with it, it's time to revisit the "What's Stopping Me From An iPhone" post from last year and see what, if anything, has changed. The rules remain the same: rank each of the day to day functions I use(d) my Treo 680 to do on a scale of 1-10 and compare the score with the iPhone. Got it? Great, then let's get ready to rumble!

Contacts. My biggest concerns were how the iPhone, with it's lack of search functions, would handle the over 8K contacts I have. Verdict: not a problem. The flick of the finger interface is complimented by an "Add to Favorites" that makes it easy to distill the most important contacts. The speed of finding a contact is roughly the same as using the Treo, as the unreal lag of the Treo in searching such a large contacts database was about the same. I would still prefer a real search, but the elegant browse interface makes it more than tolerable.
Old score: Palm: 10, iPhone: 2.
New score: Palm: 8, iPhone: 6.

Calendar. My old review said: "as a view only for my Outlook data, it'd do the job...but that's it." Uh, not sure why I thought that; you can easily edit and create appointments with a very cool analog dial interface. And Outlook synchronization with iTunes is actually flawless. The only feature I miss is a very minor one: the ability to have different colors on the appointments, depending on the category. However, the graphical display is so much better, it more than makes up for it.
Old score: Palm: 10, iPhone: 3.
New score: Palm: 10, iPhone: 10.

Tasks. Well, no change here: the feature does not exist on the iPhone. However, to be fair, I have used a total of 10 tasks in the intervening months since I wrote the last review. I'd say that this is kind of a dead feature for me, but I'd still like to have it.
Old score: Palm: 5, iPhone: 0.
New score: Palm: 2, iPhone: 0.

Podcast Player. If anything, I was way too generous to Pocket Tunes for the Treo. Since that review, it has repeatedly had a problem with skipping and freezing: nothing intolerable, but compared to iTunes and the iPod experience, I can't believe I suffered so long.
Old score: Palm: 7, iPhone: 10.
New score: Palm: 5, iPhone: 10.

Music Player. Uh, ditto.
Old score: Palm: 6, iPhone: 10.
New score: Palm: 5, iPhone: 10.

Movie Player. Wow, the iTunes interface and the big iPhone screen makes a pretty dramatic difference. And no audio sync issues. The biggest change? In the Treo, all applications have a 1 pixel white border around the screen, but in the iPhone, it's all one gorgeous glossy black surface, making it extremely easy to immerse in the video. Of course, not everyone feels the same, including noted director David Lynch: (note: he drops the f-bomb in this clip, so not all that SFW):

I, however, disagree entirely, and am absolutely floored by the capabilities here. The difference between the two is the different between YouTube and HD: yes, you can watch video through either, but what a difference. And the iTunes interface for video podcasts, etc. makes a whole world come alive. The only downside? No DiVX/Xvid support, so I have to reconvert the movies I have. That's aggravating.
Old score: Palm: 7, iPhone: 10.
New score: Palm: 6, iPhone: 10.

Calculator. No change here: still a wash.
Unchanged score: Palm: 5, iPhone: 5.

eWallet. Here's the biggest pain point so far of the iPhone. The Treo offers seamless, encrypted local data access for all of my passwords, etc. The iPhone offers a web-based sorta-solution, but, while security is perfectly fine, getting the data in there is a pain if you are not using SplashID. Plus, I need that info ASAP, not just when I have a web connection. This is the single biggest pain point, and will hopefully be solved with the new SDK in February. There is some hope on the horizon: Ilium, makers of eWallet, are doing a web-based version, but I still want it locally.
Old score: Palm: 9, iPhone: 1.
New score: Palm: 9, iPhone: 3.

Memos. Notes on the iPhone don't sync with the PC. What the heck? Annoying. I can still get all of my Outlook notes through Plaxo's iPhone optimized web interface, but that's just aggravating. However, aside from taking notes in meetings, I really only used Memos for blogging. With the iPhone keyboard, that could be a problem. Still, that interface is SO sexy...
Old score: Palm: 6, iPhone: 5.
New score: Palm: 7, iPhone: 5.

Games.. Yep, it's just that bad. As noted before, sure there are web based ones, but they are all pretty primitive and foolish. The iPhone supposedly runs OSX; you're telling me I can't play games? I've seen Jailbroken iPhones playing a full Nintendo emulator; this HAS to be addressed.
Old score: Palm: 7, iPhone: 0.
New score: Palm: 7, iPhone: 1.

Email. Ok, hang on, here. First, the iPhone keyboard is no tactile Treo, but it's definitely getting better. But the iPhone's email client is...OK. It has some notable lacks:
1) The fact that you can't multiple delete items at once is simply silly.
2) It tries to configure POP email accounts through SSL by default; that's not a usual setting for most POP accounts.
3) It does a good job with Google, but, while there is a default set up for Yahoo, they don't tell you you need a Yahoo Plus! account for it to work.
4) Um...I have yet to successfully configure it for my office. I hear tell from coworkers that there is a way, but the lack of configuration option detail in the iPhone makes me concerned.
5) You can't save emails. Strangely, the iPhone has an interface to file emails, but only to Sent, Trash, or Inbox: you can't add a folder? Well, you can if you use Yahoo or IMAP, but it seems there is only a way to create folders through a Mac or iTunes (haven't even verified if this is possible yet). Only way to save them is to keep them as unread.

Look, this is simply unacceptable. I'm expecting a LOT more here. This will be fine for me to browse email while on the road, but to use as a laptop replacement as I did with the Treo? No way.
Old score: Palm: 8, iPhone: 5.
New score: Palm: 8, iPhone: 4.

Bluetooth. Pairing my Jawbone was painless, unlike the kind of kludgy way the Palm does it. Surprisingly, I don't miss the Bluetooth headphones: the volume on them was definitely not loud enough in my downhill bike runs, and they are a little big. Plus, the A2DP solution I was using was repeatedly failing, making me very frustrated. And let's not talk about the fact that the Treo was simply losing the ability to send the audio anywhere, especially with a Bluetooth headset. The iPhone earbuds, by contrast, are light, loud, and comfortable. I still hate wires, but it's not noticeable.
Old score: Palm: 8, iPhone: 4.
New score: Palm: 6, iPhone: 6.

Camera. I'm pleasantly surprised by the quality here: far better than I expected. And the UI is slick. I would prefer a one-touch button like the Treo, but it's workable.
Old score: Palm: 5, iPhone: 7.
New score: Palm: 5, iPhone: 8.

eReader. Ok, I'll admit it: I will miss this one. However, with the video capabilities and iTunes sync, I think I can find other distractions. Still, I REALLY want an iPhone eReader. On the other hand, I have been reading books on the Treo less and less, and more using Google Reader to keep up with blogs, etc, so the overall impact is much lower. Finally, Amy has a Kindle on the way, and I'm sure it will make my eReader look like stone tablets.
Old score: Palm: 7, iPhone: 0.
New score: Palm: 2, iPhone: 0.

Google Maps. iPhone has the edge right now, with a slick UI, but the lead will be getting better with the new firmware update, which adds cell tower triangulation to Google Maps.
Old score: Palm: 5, iPhone: 7.
New score: Palm: 5, iPhone: 8.

GPS. Hoo boy, this is a tough one. I REALLY love the idea of convergence devices: one device to do it all. However, with the Tro and GPS, there were...issues.
1) If a call came in while using the GPS, the Treo forgot to talk to the GPS unit while I am on the call on my Bluetooth headset. As a result, it doesn't update the map...real helpful.
2) Listening to podcasts while the GPS was on was pushing the Treo to it's limit. Lots of skips and stutters.
3) Like the rest of the Treo, the TomTom software sometimes forgot how to handle audio, so the voice would just...stop. No way to get it back.
Having said all of that, I still REALLY love the convenience of it, but I always had to take a power cord and the GPS unit (about the size of a pack of cigarettes); I might as well take a separate GPS. Still, hope is on the horizon for GPS on the iPhone, soon.
Old score: Palm: 9, iPhone: 0.
New score: Palm: 6, iPhone: 0.

Travel Tracker. Haven't touched it since TripIt allows iCal feeds of your itinerary. Why? I added it to my Google Calendar, and Plaxo picked up the changes, and added to my Calendar. Voila.
Old score: Palm: 5, iPhone: 6.
New score: Palm: 1, iPhone: 6.

The Web. I called this one perfectly: while the minimalist approach of Blazer helps on the Treo, Safari is a FAR superior experience. I wish it supported Flash, and yes, I wouldn't mind some 3G action when I'm out in the Bay, but WiFi everywhere else more than makes up for it.
Unchanged score: Palm: 5, iPhone: 9.

The final tallies:
Old scores: Palm: 124, iPhone: 81.
New scores: Palm: 100, iPhone: 91.

The interesting part here is that parity is much closer, not so much for the iPhone being better than I previously estimated, but for the Treo getting so much worse since the last time I did this exercise. Again, these results are massively subjective, but the gist is that, with some email improvements and the ability to have applications locally on the phone, the iPhone blows away the Treo. Until then, it's a close call. Business users probably want to stick to the Treo for a month or two more until the SDK starts yielding good applications. If you don't care so much about Blackberry type of emailing, it's a no brainer.

Labels: Apple, cell phones, Google Maps, iPhone, Palm, Plaxo, Treo

  ¶ 2:27 AM (0) comments links to this post

  Dude, I'm So Tripping I travel a lot for work and fun. I tend to book trips on the individual airline's websites (after I use Farecast and SideStep to find the best deals), so I get the mileage bonuses. The pain of that is that you get all of these different confirmations, emails, and tracking numbers, so it's not easy to consolidate them down to my schedule. I use TravelTracker for the Treo to type it all in, but it's time consuming, and annoying.

Enter TripIt. That email confirmation you got? Forward it to plans@tripit.com. In under a minute, you head over to TripIt, and you get this:

Want to add more to the trip, like a car rental? Just forward it on, and TripIt adds it to it. Want to track some activities you want to do while on the trip? Use the TripClipper to bookmark it to your trip.

I like the service a lot: they focus on ease of use and solving a problem. There is definitely room to improve here, though: syncing with Outlook or Google Calendar, for instance. Consolidating Frequent Flyer accounts is another area they can help with. But for sheer, purpose-driven Web 2.0 approaching a difficult problem with a cool effortless solution. it works.

I have 5 invites I can give out if you're interested in trying it; let me know.

Labels: beta, free, Google Maps, Software, travel, weather, Web 2.0

  ¶ 6:33 PM (0) comments links to this post

  iPhone: first impressions In case you had not heard, the folks who camped out for days to get their hands on the new iPhone sort of wasted their time: unlike the Nintendo Wii, Apple was prepared for the demand. So much so, that today, I wandered over to the Apple store, where I was easily able to get my hands on an actual iPhone to play with (along with dozens of other people).

The good:

• This thing is the ultimate of small and large. The body is incredibly slim and the size is extremely small, smaller than my Treo, or even my old Palm TX. The screen is startlingly large, especially for movies. There is no obvious bezel, so this baby is all screen.
  
• The UI is amazing. The perfect Apple UI, it's sexy, responsive, and unbelievably cool. Transitions, scrolling, fonts: this device just screams craftsmanship.
  
• The phone is extremely great. Call quality is excellent, UI is superb, and address book integration is stunning. And that's not even mentioning the elegant touch of blanking the screen when you hold it to your face while calling.
  
• The screen cannot be believed. Bright, vibrant, and everything practically pops. with no reflections. Images are perfect, movies and Cover Flow ache to be savored.
  
• Just incredible UI touches. The dropping of the pins on Google Maps, the speed sensitive flicking of your finger in Cover Flow, the intuitive interface. Magnificent.
  
• LOVE the widgets. Yahoo Weather is unbelievably sexy, though strangely you can't reorder the cities you are looking at, just delete or add. Stocks was very cool. And Google Maps was delicious. Even Notes were DAMN cool, with a miniature yellow legal pad and sketch like font.

OK, enough gushing. Let's talk about the bad.

• The keyboard is as bad as the Newton's handwriting recognition was when it first hit. Yes, the iPhone tries to automatically correct your typing issues, and does an OK job, but this is clearly a device that can only be typed on with a single finger; two thumbs are out. The sensitivity of the keyboard is wonky, and it only takes advantage of the optional horizontal orientation when in web browsing mode; what a mistake. I can see Doonesbury cartoons making fun of this anytime now.
  
• Web browsing is slow, even on WiFi. This surprised me, as we're talking about Safari on a closed OS X environment. Why so slow? There are no other apps to slow it down? In contrast, the YouTube app was extremely slick and responsive. I was pleasantly surprised to see NetVibes load smoothly with no issues, but signing in was a strange experience on navigation controls that were hidden under translucent menus.
  
• Email was a pain. Sure, reading was actually cool and sexy (especially loved the inline photos, etc.), but writing only was good if you were replying or emailign someone in your address book. Typing the address in the To field was an exercise in frustration (see the keyboard issues).
  
• Orientation changing sometimes worked. Worked great in iPod mode for music, but video stayed stubbornly widescreen. Not that I'm complaining, but still... And the orientation change only works for some apps, not all.
  
• What the heck is up with Bluetooth? Bad enough they shipped a multimedia device without Bluetooth 2.0 (2.0 lets you stream audio to headphones wirelessly), but there seemed to be no obvious way to set the iPhone's Bluetooth name. Normally, not a huge problem, but in an ever increasing Bluetooth world, you better know what you are pairing with!

There's far more, but check out this accurate rant from another user:

1. Bluetooth is ONLY good for connecting a headset. That's it.
2. There is no file browser on the device at all. Data must be organized (if at all) in the appropriate application.
3. The camera is a simple application that has ONE button: the shutter. Pictures come out okay on the device, but nothing too fancy on a monitor, especially if it was an attempt at a macro shot.
4. SIM card is damn near impossible to open, if at all. I didn't look into it extensively.
5. Web browser is slow, even over WLAN. Even the simple OneList web app that was created takes around 20 seconds to load over WLAN. You can not highlight, cut, copy, or paste and text from a website, and you can not save any images you find from a website either. The only nice thing about it is the tabbed browsing, which crashed on me when I went to Engadget and YouTube on two tabs. This is the only application that allows you to use the keyboard in landscape mode.
6. The keyboard sucks. It gets slightly better after the iPhone "learns" you, as the employees said, but even then, it's not a device you can use with one hand comfortably, much less without looking.
7. You can only send one picture at a time in an email.
8. No custom ringtones (yet, as we were being told) and the alert tones can not be changed whatsoever.
9. The default ringtones are incredibly lame.
10. The only form of customization outside of a lame default ringtone is the wallpaper, which you'll only see when you need to unlock the device or when you get a phone call.
11. "Picture pinching" or using two fingers to zoom on any content is certainly fun to play with, but not practical whatsoever. This operation depends solely on using the device with two hands.
12. No document editor or native viewer. You can not store documents on the device to be viewed, they can only be viewed as attachments when they're sent to your in an email.
13. Visual voicemail is laggy and reacts about the same way as pushing the fast forward and rewind buttons on traditional voicemail systems. The only advantage is for those that get that many voicemail messages a day that they need to sort them according to priority.
14. NO games. None.
15. No voice dialing.
16. No speed dialing (which can be made up by the "quick list", but getting to that quick list isn't as fast as holding a single key on a real keypad).
17. No video (capture).
18. No MMS.
19. It's still <4GB for $500 and <8GB for $600
20. It only takes around 2 hours to explore every menu without any options for expandability except to scrounge around for new web apps that will load slowly and nowhere near as smoothly as the native apps.

The Apple Store I was at sold out of the 8GB versions by 2pm again, but the 4GBs were still available. And they said they expected more in tomorrow. So, I don't expect this to be a rarity. What I think I'll be doing is waiting to see what happens with three things: addressing the email/keyboard issues; looking at expansion to 3rd party apps and widgets; and definitely finding out how the synchronization with Outlook goes, as that's my life right now.

Still, definitely a game-changer, and a whole new class of device, but right now, the price keeps me away for the tradeoffs I mentioned. As the late-30's mother next to me breathed, nearly orgasmically, "I so need this," I would suggest you try for yourself, and make your own conclusions.

Labels: Apple, cell phones, Google Maps, iPhone, Palm, widgets, youtube

  ¶ 5:51 PM (0) comments links to this post

  In Praise of the Treo 680 Well, it's been nearly a month with my new Treo 680, and I'm pleased to report it's been a significantly better device than I had anticipated. I was moving from a Palm TX, with it's big screen and integrated WiFi, with a Bluetooth connection to my Sony Ericsson Z520 as backup. My biggest concerns were the sacrifice of speed of WiFi and the lack of screen real estate, as well as the purported disastrous Treo 680 battery life. I'm please to report that all of those concerns have been addressed.

Ok, let's start with the obvious. The keyboard is phenomenally easy to use, and makes mobile email a reality. Yes, I am now getting enticed by the prospects of checking email at any moment, but even for things like Twitter or detailed messages, it's extremely workable. The form factor of the Treo is the right balance of size and sleekness to me: it allows me to slip the Treo in a blazer pocket or the front pocket of my jeans, equally. Having never had another Treo, I can't comment on the lack of antenna that people praise the 680 for, but it certainly feels smaller than it is. Battery access is readily available (more on this later), and the stylus is VERY well integrated into the body. I also appreciated the ports being the same as the Palm TX, so I could use my chargers, etc. Other nice touches: a physical switch that allows me to switch the 680 to "vibrate" mode, without having to navigate menus, etc. VERY handy for meetings with clients. Advantage: 680.

Let's get the speed stuff out of the way: I hadn't realized that I was only on GPRS with my Sony, not EDGE. It makes QUITE a difference. Is it like DSL? No, but it is absolutely equally as fast as my TX's WiFi connection. And, without the overhead of the Bluetooth connection, it seems to be even more responsive. The keyboard, responsiveness, and EDGE performance do not make me miss my TX at all. The one concern I had was in downloading podcasts, but QuickNews lets you sync on HotSync updates, so no real impact. Advantage: 680.

Screen real estate. Yep, the 680 is noticeably smaller. Watching widescreen movies is a joke, though downloaded TV shows are perfectly acceptable. The screen is incredibly vivid, and very high resolution, even with a screen protector. Still, for multimedia, it's a hard adjustment. Advantage: TX.

SD card support. The 680 adds a very helpful cover to make the SD card slip unnoticed into the body. Despite my trepidations, it supports my 4GB card…most of the time. About once a week it can no longer "see" the card, and I need to reset it. Can be very frustrating, especially when it happens on a bike ride where I'm using PocketTunes to stream to my Bluetooth headset. Advantage: TX.

Bluetooth. My Sony phone was not all that comfortable with the Jawbone, but did offer voice dial support for Bluetooth headsets. For some reason, this is not a function allowed by Treo's (asinine). I'm trying some software solutions to see if they will help, but the phone at least keeps the pairing with the Jawbone. The Motorola Bluetooth headset is definitely more troublesome: it frequently loses the connection, but this may be more of a result of the updated software program. It does, however, stream sound from movies over Bluetooth, whereas the TX choked. Advantage: Tie.

Other miscellaneous issues have been reported as poor battery life, though I don’t have an issue with it: I have chargers at work and home, so it's fine. It does get a little addled with a lot of activity, but that's OK.

Downsides:

• The case is smooth. Too smooth. When one-handed typing, I am always afraid it'll slip out of my hand like a bar of soap. There is one rubberized point, but it only helps if you hold the Treo in your left hand. I'm probably looking at a "skin" case in my future.
  
• What the hell is with the radiation this thing throws off? Every had your cell phone close to a landline telephone or a speaker, and heard that buzzing? You quickly move your phone away, and all is fine, right? Not with the 680: this sucker needs to be FEET away from the interfering speaker. It seems just OK if I have in my pocket, and I sort of push my body between it and the phone, but it's amazingly stronger interference than any other phone or device I have ever had. I have to solve this, as clients are getting tired of having their eardrums ripped apart.
  
• Who stole the reset button? Look, I know we all want Palm devices to never need a reset, but with the crap I load in, it is an unfortunate necessity. Granted, the unplanned resets are less (not nonexistent, however) with the 680 compared to the TX, but the only way to reset the Treo is to pop out the battery and put it back in. Pain in the ass.
  
• Laggy UI. When the Treo gets bogged doing multiple things, it starts responding sluggishly to the keyboard. Yes, it catches up, but very frustrating.

Overall, I am extremely pleased with the 680. The convenience of having an all in one device, along with the enhanced data usage and keyboard, and the elegant form factor, make me very happy with the choice. Do I miss the TX? Well, with it's broken reset button and overtaxed OS, it was getting long in the tooth in any case, but no, overall, I do not. I highly recommend the 680 for anyone.

Labels: cell phones, Google Maps, iPhone, movies, music, Palm, podcasts, Treo, TX

  ¶ 3:02 PM (0) comments links to this post

  MyMaps is here What is it with Google? They getting scared by Yahoo's recent launches? In any case, they've now released MyMaps, an easy way to create your own Google Maps mashup. Mark your places on the map, add pictures, links, and voila. It took me about 5 minutes to create a map of all of the past places we have lived. Next, a map for my company of all of my clients.

Labels: Google, Google Maps

  ¶ 12:54 AM (0) comments links to this post

  Google Maps Sightseeing There have been planes. There have been ships. There have been cars. But now? How about Google Maps capturing a cruise missile in flight, over the Utah desert?

Big Brother's eye is unblinking.

Labels: Google Maps

  ¶ 1:30 AM (0) comments links to this post

  The Gigapixel Image An amazing example of Google technology layered on over the ever increasing ability of cameras to capture extremely large images with amazing quality. For instance, this gigapixel image of my hometown, Boston, captured from the Prudential Tower's Skywalk, allows you to drill in so tightly, with such clarity, it allows you to be come a virtual peeping Tom.

For instance, take a look at the original image here:


Now, here's the Hatch Shell (where the Boston Pops plays on July 4th, miles away:

The photo of the Hatch Shell is not a separate photo; it's a zoom of the top left of the 1st photo. You can practically read the names of the composers etched into the steps; that's Mozart's name on the right. Amazing; we're finally getting technology that shows like CSI always supposes we have.

Enjoy a virtual visit to a still life of Boston in the summer. See you there!

Labels: Google Maps, photos

  ¶ 3:49 PM (0) comments links to this post

  New Widgetbox Widgets Check out two new WidgetBox widgets I've added in the right column. Man, these things keep coming and get cooler and cooler.

• The Internet Address Book Pidy. Simple: consolidate all your social networking and sharing URLs into a single "badge." Clever.
  
• The Google Maps Widget. Paired with a text Widget for a caption, allows me to display a map of where I'm traveling to this week. With how much I've been traveling, always fun to show.

WidgetBox makes these things easy. Now, if they'd only integrate all the Google Gadgets, we'd be all set.

Labels: Google Maps, travel, widgets

  ¶ 12:21 AM (0) comments links to this post

  James Kim: killed by Google Maps? James Kim's body was found today, ending the search for the tech community member. As I wrote last week, James was always a great part of my tech and media consumption, and I am extremely sad for his family and coworkers.

Now the question turns to "How could this happen?" Interestingly, MSNBC suggests part of the blame may lie with our ever-increasing reliance on Google Maps. I have been a victim of this myself: in our driving trip to Dallas and the Southwest in 2001, I used Microsoft's Streets & Trips to plan a scenic drive to Taos...and almost got Amy and I killed, careening off a cliff at 60 MPH, Roadrunner cartoon style. The road went from a flat blacktop in the desert to a dirt trail barely large enough for a single car in 50 feet...and the trail ended above a cliff. This, because I asked Microsoft for a "scenic" route.

Looks like there's a market for a new map site: one that uses real-world info. Seems like an ideal Web 2.0 idea: combine social networking with Flickr and Google Maps, with an associated wiki: Voila! Mapr is born. :-)

Note: I will collect royalties on that and donate them to James Kim's family, if it's used.

Labels: cars, Google Maps, news

  ¶ 1:10 PM (0) comments links to this post

  San Francisco Parking Carma From the "why didn't someone think of this sooner?" department: a Google Maps mashup showing you near real-time parking space availability in San Francisco. Cool, but I wish it showed all of the parking lots and the cost for hourly and daily parking for each.

By the way, if you are looking for a good Google Maps mashup directory, can't go wrong with this site.

Labels: cars, Google Maps, San Francisco

  ¶ 1:42 AM (0) comments links to this post