Navigating the Future: Take Me to Bob

Google has just announced a free turn-by-turn navigation app for Android 2.0 in the US (Radar post). Google Maps Navigation relies on Google's own mapping for routing you. As with many navigation devices you can search Business Listings. However, they are also including data not traditionally available to navigators. In the promo video Google demonstrates that you can ask to be taken to "The King Tut exhibit". GMN will determine that it's in Golden Gate Park and route you. This is "because it is connected to the internet it is using all of the latest information on the internet."

This is huge. To be able to request implicit destinations based off of realtime information is something that has never been available before. What new queries will be available to us because of this? Google has a lot of data. How much of it can be assigned a location? Lots. There are millions of KML files out on the internet. Here are some of the useful queries

"Take me to Bob Smith" - If Bob is your friend on Latitude then Google Maps Navigation can take you to him. If Bob moves then GMN could even re-route you. I wonder if they will enable the chase scenario.

"Drop me off in time for the #48 bus" - Google knows the public transit schedule. So not only can it drop you off at the nearest stop, it could drop you off at the stop that will ensure the shortest multi-modal trip.

"Show me homes under 500K in Capitol Hill" - Via Google Base, Google has real estate information (it has had neighborhood data for quite sometime).

"Take me to my next appointment" - If you use Google Calendar and you accurately fill out the location field then this is a snap.

"Take me to the nearest Winter Coat Sale" - Using Adsense for Google Maps, GMN can easily lead you to local sales.

"Take me to the bar my friends go to the most" - Using Social Graph API and the new, experimental Social Search to tap into Foursquare, GMN can determine where you friends go, aggregate their destinations and lead you to their favorite watering hole.

"Take me to the largest event" - Using a combination of Latitude and its new access to the Twitter Firehose (which will soon include location - Radar post), Google can determine where people are.

"Take me on a tour of the top 10 historical sites here" - Using Wikipedia Google can determine what the sites are and where you should be taken. Alternately, Google could take you on user-generated tour.

"Take me to the most picturesque place near here" - Several years ago Google bought Panoramio, a location-based photo site. Google can determine which place nearby has had the most photos of it taken.

"Take me on a tour of the site from Around the World in 80 Days" - Google already geoparses many of the books it scans (just see this map). This routing is quite possible.

"Take me to the EPA's protected sites" - Government data is becoming more available. This is just one possible governmental query. You could also ask to go on a tour of TARP fund recipients or Democratic donors.

Obviously not all of them will be enabled, but I bet that within a year some of them will be. What other scenarios can or should they implement?

Four short links: 24 September 2009

Historic Cartography, MySQL Futures, Timewarping GDB, Open Source Werewolves

1. Milestones in the History of Thematic Cartography -- This resource provides a comprehensive view of the history of cartography, with examples of maps created throughout the ages and background information about the contexts within which those maps, visualizations and map making technologies were created. Explore each time period, click on the images and stories found throughout each time line, and read more about the history of creating thematic maps as a means of visualizing data. (via Titine on Delicious)
2. Interview with Larry Ellison (Infoworld) -- Asked about MySQL, "No, we're not going to spin it off," even if asked to by the EU, Ellison said. Lots of detail and interesting tidbits in this interview. (via timoreilly on Twitter)
3. GDB and Reverse Debugging -- GDB version 7.0 (due September 2009) will be the first public release of gdb to support reverse debugging (the ability to make the program being debugged step and continue in reverse). (via Hacker News)
4. A New Self-Definition for FOSS -- There was this clamour in the past to get companies to open source their products. This has stopped, because all the software that got open source sucked. It’s just not very interesting to have a closed source program get open sourced. It doesn’t help anyone, because the way closed source software is created in a very different way than open source software. The result is a software base that just does not engage people in a way to make it a valid piece of software for further development. I don't agree entirely with this quoted piece, but there's a lot to what he says. Open source is not a silver bullet--hell, most people don't even know what the werewolf is. Open sourcing doesn't magically make developers appear, open sourcing doesn't magically make a market appear. Your closed source problems still exist after you open source because it's. not. about. you. It's about the users and their comfort, abilities, and freedoms. (via Simon Willison)

Four short links: 6 July 2009

iPhone Maps, Tooth Milling, Scratch Updated, Newspapers for All

1. Offline Mapping App for iPhone -- carry Open Street Maps maps with you even when you're not in 3G/wifi range. (via Elisabeth)
2. My dentist used an in-office CAD & CNC mill to produce a new tooth for me today (Nat Friedman) -- hello, future!
3. New version of Scratch released -- Scratch is an excellent way to teach kids how to program (I've had success with lots of 7 and 8 year olds). The new version includes keyboard entry, webcams, and support for Lego WeDo. The user interface has also been changed to work on a Netbook's 800x600 screen. Kudos to the Scratch team! (via scratchteam on Twitter)
4. Newspaper Club - a Work in Progress -- blog for the Newspaper Club project. "We're building a service to help people make their own newspapers. This is the blog where we're alarmingly honest about where it's all going wrong." I can't figure out whether this is a brilliant decentralisation move that will disrupt the newspaper industry, or a paper form of steampunk. (via Simon Willison)

Walking the Censorship Tightrope with Google's Marissa Mayer

Google sometimes finds itself at a difficult crossroad of wanting to make as much information available to as many people as possible, while still trying to obey the laws of the countries they operate in. I recently had a chance to talk to Marissa Mayer, who started at Google as their first female engineer, and has now risen to the ranks of vice president in charge of some of Google's most critical product areas, such as search, maps, and Chrome. We talked about some of Google's future product directions, and also about how Google makes the decision as to when information has to be withheld from the users. Marissa will be delivering a keynote address at the O'Reilly Velocity conference next week.

James Turner: As VP of Search Products and User Experience, you're responsible for a vast swath of the Google product line, from search to maps to Google Labs. You were also the first female engineer at Google. Can you talk a little about how you came to Google and what brought you to where you are today?

Marissa Mayer: Sure. My background is when I was at Stanford, I was doing a symbolic systems degree in artificial intelligence. And I was always somewhat interested in search. I ended up getting an email [from Google] towards the very end of my job interview process. I came to Google and did the interviews. And I came here because I really wanted to put my AI background to use. For about the first year or so, I did. I did a lot of work on categorization, some work on search quality. And then interestingly, we sort of had a void around how the site looked and felt and how it worked. And we tried very hard to hire someone in UI. We thought we needed someone to do UI like one day a week, and do systems engineering the rest of the time. After a few months of failing to hire such a person, Urs Hölzle, our VP of Engineering, pulled me in and said, "Marissa, we've looked through all of the resumes and you have this background in your undergrad on cognitive psychology and philosophy and things. And would you mind dedicating one day a week to UI?" So I did.

I pulled together a volunteer team to help out one day a week while we all still worked on our various AI and systems work. And then, of course, one day became two days which became three days or four days or five days. And I was also programming at that point. I switched over from a lot of the AI work I was doing to programming the front end for Google, working on the Google web server because it was nice for me to be able to not only make decisions about the UI but also to implement them.

And then because I was implementing the changes to the front end, I would go and meet with Larry and Sergey. And they would say, "What's happening on the site this week?" And I would say, "Well, I coded a change that looked like this. And I coded a change that looked like that. And translated this page and it'll go here. And there'll be a pull-down over there for the number of results." And without even realizing it, I did project management before Google had project management, by specifying how things were and looked and communicating to the rest of the company about how these changes would manifest. And then when we got to about 200 or 300 people, Larry and Sergey discovered that most companies have this function, product management, which I didn't know about; they didn't know about prior [to this]. And we decided we should have such a department. They realized there were a few of us around the company that were doing product management even though that wasn't our title. So they started the product management group and got it started earlier. And so I became a PM.

First, I was the PM on Google.com, really broadly across the whole site, because there were only three of us. One of us did the site, which was me. Salar Kamangar did the ads. And Susan [Wojcicki] did the partners. And then as our teams grew, I became the director of consumer web properties, where I still did all of the consumer facing work of the website including branching into Gmail and tool bars and some of these other areas. And then as we progressed, eventually, we restructured so we had search, ads, and apps, because Gmail and the related space of calendar and docs became large enough that it made sense to spin it out. So then I kept the search piece and the properties we have that are more related to search.

James Turner: There's always been other companies trying to take a piece of Google's dominant position in search; how does Google plan to stay a step ahead in search, especially in light of new players like Wolfram and Microsoft's new emphasis on Bing?

Marissa Mayer: Well, we are very focused on search. We have a large team here that's really focused on it and working hard on it. And we're constantly trying to forge in new directions. So we were really excited about the launch of our search options page because we think that allows us to try a lot of new ways to slice and dice and filter results. We were also really excited about Google Squared, which attempts to do automated text extraction from the web and present comparison tables for different entities in response to queries. They're both new ways to search. How do you generate a timeline from a web search? How do you generate a comparison table? And some of our competitors are also looking at those same issues. So I think on the whole, right now, our search is a very healthy ecosystem. There's a lot of interest. There's a lot of activity, and there's a lot of new ground being forged.

James Turner: Google users want the most useful results, but content providers want to get their pages seen, sometimes it seems at any cost. How will Google continue to provide the most useful results in the world of increasingly sophisticated SEO gaming?

Marissa Mayer: Well, we generally -- we really want to be fair in these issues as well as be good to users. We do think that spam is very detrimental to the user experience. We do have an incentive to find spam and remove it from our results. But we want to do something in a way that's very scalable. The web is scaling at an incredible rate. And we don't think it's really viable to try and fight spam in a manual way. So we're always looking for new algorithmic ways to understand new spam techniques, to be able to detect them in an automated way and remove them from our results. And the nice side benefit that scalability has is it's also reasonably objective and fair.

(continue reading)