organising the world's information, geographically lars rasmussen google maps in sydney. 500 million squares. within weeks high res of sydney; once or twice more even. zachary's pizza, berkeley originally a c++ browser; where2. tried plugins/flash. 4 weeks for prototype; as opposed to years for c++ app. javascript has inconsistencies, but compared to c++ it is easy. compared to google earth nowhere as rich. first day hit top load for 6 months. satellite imaging caused traffic to grow exponentially in one day. design philosophy end-user is royalty go beyond browser lowest-common-demominator : because they're google browser people ask them what they want. dynamic as native apps; simple as google website do what it takes launch early + often : with 4 months dev, figure 3 months to launch. larry page played with demo and said "just go". labs.google.com playground. 5000 emails a day when launched. now under google local; discussed frame layout endlessley; launched and people hated it, changed in a week. dhtml : javascript handles events, which can modify the structure of the page. browser does nothing until event handler finishes, then re-renders the page offscreen and displays it. back-button: virtual pages. what does it mean to push the back button? back should go back through search history, not random junk. browser remembers clicks in firames in back history. to get around this you use a "virtual" iframe which copies what is happening into your page. this way you can control the pages that are shown and consequently the back bar. backend map providers got nervous about housingmaps. housingmaps had inadvertently broken a link back to the data provider so they weren't being charged. api wasn't a technial challenge, but a contractual one. google loved the maps hacks but oculdn't tell anyone. google would never build a bus map route for seattle, but they are inspired by it. google watches the api key to see what cool things are happening. katrina imagery request was from the government. growth areas : flashy browser stuff is 3/4 ; 20/25 all over. map data is licensed. cafe in san-fran? cafe in berkey. 20 billion web pages "downtown seattle." doesn't know where silicon valley; people berrated them for not knowing where stuff was. user logs show that users think google knows that stuff -- mabye comes from the "know it all" search box. processing : different data and different confidence; can you join it? api is telatlis data ... navtech data is on the site. can they merge? can they merge other databases? adding spacial infrastructure to google search infrastrucutre. "cheapest gas via work" routing: shortest path algorithm .. if underlying data is correct works. however traffic not taken into account; taxi driver berrated him that maps takes him straight into traffic -- some drivers love it because tourists bring it and they make money. ridefinder -- nobody uses it but you get gps feeds from taxi drivers. drawing: pretty anti-aliased is nice. when is sydney coming: very tied to data format .. and sydney maps dont' come in that format. working to remove that, early next year. where can you get aussie map data? sensis, map data sciences. all comes from teh government. different grid systems around the world? no cartogpohers. in japan, use different datum, lat long different views of ovalness. datums need to be normalised. how make money? haven't settled on that just yet. users == money; not sure how but it can be there. advertisements coming. api via c++? no, web is focus. satellite tile age? higher == fresher. google earth looks after imagery; new sydney about 6 months. imagry has a "novelty" feel censorship of photos: have to respect. obfuscated javascript: makes code smaller. time to download is now in seconds. government fudging: not really. projections of tiles: new different ones on the way, maybe. night satellite, etc. winter/summer etc. geological features, historical maps. coming. disputed borders: no easy answers. chineese laws say you can't move maps off; but they do have maps in china.