>>bernhard seefeld: okay. welcome. today wetalk about the future of google maps. in this session, we're going to show you a few morethings of the demo you just saw in the keynote and then we'll go into the new api thingsthat mano and ken are going to talk about. do you like the demo?[ applause ] >>bernhard seefeld: okay. great. so my nameis berni, and this is yatin. he was the engineering lead on the project and he's going to showyou few things. thanks. so i thought we could start and look at threethings that we couldn't show at the keynote. so one of the things is the related places.you saw that i clicked on the museum and then other museums showed up on the map and thenyou could go around and explore and explore.
so one cool thing is that we can turn it,actually, into a map on the entire world. so there's a place here nearby called monk'skettle. people from san francisco might know it. it's known for a great beer selection.it's a really great pub. it has a great beer selection. and you see now that i've searchedfor it, all other places show up that are -- like gestalt is a bar nearby that alsohas a great beer selection. and if i zoom out, i'll get more places like that: sevenhills, daily grill. they're all great. but one cool thing is i can go further andfurther, and then i can, for example, go and zoom into austin.anyone here from austin? >>> yeah. right here.>>bernhard seefeld: okay. so we'll see whether
this actually works, but you're verifyingthat those places are good. so now we see that the eastside showroom showsup, and the contigo, and before, i got some -- the flying saucer draught emporium. thatsounds pretty -- is that right? >>> yeah.>>bernhard seefeld: so we generated a whole map for the entire world that is now aboutbars with great beer. [ laughter ][ applause ] >>bernhard seefeld: isn't that great?so yatin is going to show you another one of those photo tours.>>yatin chawathe: berni showed you a photo tour of the inside of the vatican. what i'mgoing to show you is another photo tour that
takes us to an even larger scale, so you cansee that we can sort of make this thing work not just at -- for a single landmark likethe st. peter's basilica but even an entire city's worth of information.so this here is a view of the houses of parliament in the center of london, and i am going tostart the photo tour and just watch how it sort of shows you a little bit of the housesof parliament, and now it's just you turn around and you see big ben right in the cornerover there, and it's going a little further away, showing you a little bit more -- actually,that wasn't big ben. that was the other tower at the other end. there now you start to seethe big ben. these are views of the big ben and the housesof parliament taken from the london eye by
users just like you uploaded to google, andhere's the entire city of london seamlessly stitched together into a very, very compelling3d experience. and jonah jones, who was helping berni withthe demo live at the keynote, and i are going to have a full session on how some of thetechnical and design details of the new google maps work. this will be on friday, i believe,at 9:00 a.m., so come join us there if you have more questions.and i'll hand it back to berni to show you just one other tidbit from the new googlemaps. >>bernhard seefeld: okay. thanks. so we useactually cinematic principles to steer the camera. the algorithm knows the dramatic effectsthat are required to get to this stage, so
very cool. so you should definitely go.so i have a question. does anybody know what happened last thursday afternoon? anyone fromaustralia here? you cheated. nobody? yell it out.>> (speaker is off microphone - eclipse) >>bernhard seefeld: very well. so what we'regoing to do now is go and change the system time to last thursday. a little bit later.i think like 5:00 p.m. would be good. okay. so we go back here. what is happening?so let's go to earth and start zooming out. let's see the world.and so now that we look here at the sun, you see that there is a little black spot here.so that's the moon. and then we turn around. so the -- i told you that the stars and themilky way and the sun were in the correct
position, so is the moon, and it's actuallike a simulation of the sunlight going to earth and the moon is in the middle, so wesaw this solar eclipse. and actually we were just practicing the keynotelast thursday and we looked at this screen and we're like, "shit!"[ laughter ] >>bernhard seefeld: "why do we have a blackspot on earth?" [ laughter ]>>bernhard seefeld: then we just turned around. we're like, "why is there a black spot? ohhhh!"then we went online and there was indeed a solar eclipse, so it was kind of funny.all right. so this is -- well, i wouldn't suggest you should change your system timeall the time but it's like one of the neat
things. so wait for the next eclipse and thenjust go on line. so okay, with that, i'll go back to the slides.i think i just pressed the wrong... >>ken hoetmer: the laptop might have turnedoff. >>bernhard seefeld: okay. thanks. and so here'sthe agenda that i should have told you before. i guess these were the three interesting thingsabout the new google maps and then you'll get an update on the new google maps apisand the next million maps. and before i hand it over, i'd like to recommendyou sign up or recommend to your friends our online courses, and they go through how touse the new google maps, maps engine lite, and google earth. just go to g.co/mappingcourse and there will be online courses, massive
online courses that you can take and helpyou learn a lot. thanks. >>ken hoetmer: all right. so my name is ken.i'm a product manager for the google maps apis based in sydney and i'm going to talkto you a bit about some new things we have coming up in google maps apis.so as i do that, i'm just going to tackle the obvious question -- i've seen it askedon twitter a number of times already -- and just not beat around the bush and tackle itstraight up, which is: are you going to announce a new google maps api right now?and the answer i have to give you, unfortunately, is: no. remember that the new google mapsthat was just demo'd in the keynote and that berni and yatin have demo'd now is a preview.that's not to say that we won't at some point
announce a new api based on the new googlemaps, but we need to remember that this technology is actually quite nascent and we still havea lot to do with the product before we can think about giving it to third parties. sothat's the bad news. the good thing is, i do have an announcementand i think it's an announcement you're find very compelling and it may just be sort ofthe largest visible change that we've introduced to google maps apis in the last eight yearsthat we've been around. to do that, i'm going to set up by takinga look at what the google maps api version 2 looked like circa 2006.now, you can see on this map the familiar pieces of the google maps api: the red pin,the info window, the same kinds of familiar
yellow and blues of the google map base map.the info window, as you can see, circa 2006 had nice rounded corners as all good web 2.0products did at that time, as well as we had an incredibly large shadow, which was alsopopular in web 2.0 in the 2006 era. if you flip forward to google maps api circa2013, can anyone spot the difference? i'll flip back, flip forward.we squared off the corners on the info window, certainly. so web 2.0 is over. we still havethe same pin. we still essentially have the same info window. we still have the same designand base map. we introduced street view, of course, in 2007 and that came into the api.when we relaunched version 3 of the javascript maps api we actually added support for mobile.but essentially what you're seeing between
these two -- 2006 and 2013 -- in seven yearsis essentially the same product. loads of new features but essentially the same look.now, when you compare this to the new google maps, which we've been talking about a lotalready today, you see a completely new experience in the new google maps. the base maps area completely different design and set of colors. the marker is different. there are no infowindows, really, anymore. everything is sort of pulled to cards onto the -- onto the left-handside of the screen. and the control experience is completely differentas well. we have a carousel down at the bottom of the map, rather than the zoom slider thatyou've come to get used to on the left-hand side of the map.and when you look at the mobile applications
that were discussed in the keynote today aswell, they've also undergone a redesign that aligns more closely with new google maps wewere talking about earlier. again, then you flip over to the google mapsapi and i think i've kind of beat the dead horse here long enough, but it's time fora new look. we're stuck in 2006 on nokia 95s, waiting for wiis. this is what was happeningin 2006 while the rest of google maps has moved along ahead of us.so here's what we're going to introduce. it's called: google.maps.visualrefresh = true.this is one line of code which is a global property which you can add to your javascripton your page and what it will do is it will change the look and feel of the javascriptmaps api.
to illustrate, i'll just pull up the picturethat i was showing you earlier, and when i applyggoogle.maps.visualrefresh = true, thisis what you get. it's the same google maps api that you'vecome to get used to and that's on now a million sites we announced earlier, but it's beenrefreshed with a brand-new more beautiful design inspired by the work that's been donein the mobile applications and now the new google maps.so these are the same base tiles that are used in the new google maps, but renderedas images not rendered as vector tiles in the browser.so we've taken the same design for the base maps that's been used in the new google mapsand the mobile applications and brought it
into the javascript maps api.that's what i was going to talk about here, one of the four major changes.the second major change that we've introduced is a new default marker. so you would haveseen on that screen that we've removed the shadow from the marker that you've come toknow and love, and we've brought in the marker that's now the default in the new google maps.the info windows, which i had commented on a number of times earlier, have also undergonea change. the new info window is a much fresher, lighterlook and feel. the shadow is gone on the info window as well.and finally, the controls have undergone slight change, just a fresh coat of css to bringthem into 2013.
now, it's important to note that this is aseamless transition and has been carefully designed to be so. so it's just one line ofcode that you add to any maps api application and it will just enable the new look and feel.any custom markers, custom info windows, custom tile overlays, custom -- custom map types,anything that you've done to customize your map will stay the same and will work as intended.so this is just a transition of the ui elements. and to illustrate that, i've just thrown upa picture of the -- of the more than a map showcase site that we have which i'll demoin a second that we've upgraded to the new look and feel just in the last half hour.and of course we have another api, the static maps api, which we've added the refresh toas well. it's a simple url parameter and visual_refresh=true.
so with that, let's flip to the demo.so here what i've got -- if you can see -- is a side-by-side view of the classic googlemaps api, if i can get this control to work. let's see if i can remember my url.apparently that works. so i've got side-by-side on the left the classicversion of the google maps javascript api and on the right a refreshed version, andthese are running exactly the same code except for the global property has been set on theright. so you can see the -- the older tiles on theleft a lot more yellow than on the right, and this is the new design that's been introducedin the new google maps. if i zoom in, you'll see the same style ofmaps as berni was -- was showing earlier with
the same icons, et cetera. we don't have theluxury of rendering vectors in the browser and creating a new map for every place, butwe do have the same look and feel that we can bring into the api.if i open the info window, you can see side by side the difference of the info windows.in satellite mode, we've also changed the labels in the hybrid view so that they'refreshened up with the new google maps look and feel.and everything else you can see remains the same. so peg man can still be dragged ontothe map. that works. and everything is as expected.if you flip over to a couple other different places, here london -- and i show you on themap -- you can see how the new look and feel
of the base maps actually really does changethe look of the maps api application. in this case, it's a much fresher look.so what i'm going to do now, to prove to you that this is actually available now, you cango change your site now, is go to morethanamap.com, which is our showcase case for the maps api,flip over to demos, to base maps, and there it is.so it works. now, if i click on styled maps, styled mapsalso still work the way they did before, and i guess the point i'm getting at here is thatin some ways this is a non-announcement. it's one line of code that changes the importantthings but doesn't change all the customizations that you've created.routing here as well works, going up to elevation
in san francisco. again, it all looks as youwould expect, but we have a much brighter, fresher look to the api.i'll step back to my deck over here. great.now, i'll just talk a little bit about availability. as i mentioned in the demo with morethanamap.com,this is available now. it's available in both our experimental and release branches foryou to opt into. and we're going to take this new look and feel by default to the rest ofthe million maps api sites on the web. and the way that works is it will become defaulton the experimental branch in three weeks -- or in three months' time, in august, andthen three months later on the release branch, which is the default branch for our enterprisecustomers, in november.
okay. that's it for the announcement of therefresh. the other thing i wanted to talk about wasto expand a bit on the numbers that brian announced in the keynote. and the numbershe announced were that we now have 1 million maps api sites and apps, and the other isthat these million api sites maps are viewed by 1 billion unique visitors a week.just sort of wrap your head around that one while i do the little spinning animation.to help you contextualize how big these numbers are and why we think this is so importantto us is, you know, sometimes we don't think about the scale and reach of the maps api.keir clark, i don't know if he's in the audience but he generally reviews around three sitesor apps per day on the google maps mania blog.
if he were to continue to do that at thatrate, it would take him 1,000 years to review all of the maps api sites in the world. wenow have google maps in 200 countries. if you do simple math, 1 million divided by 200,you get 5,000, which means there are roughly 5,000 of maps api sites in every country inthe world. and the last stat here that i want to throwup there, because i think it's -- it's the most interesting, especially given, you know,what larry was talking about today in the keynote about bringing the internet to therest of the world and a number of people have talked about today, if we -- if we take thatthere are roughly 2 1/2 billion people on the internet and we know that we get a billionunique visitors to maps api sites every week,
we can't exactly correlate unique visitorsto people because global networks sometimes mean that multiple people hide behind thesame ip address and perhaps a number of us in the -- in the audience here and myselfuse multiple devices in a day, so it's really hard to kind of work that out, but we do knowif we look at our numbers across a month, we can very, very confidently say that halfthe internet sees a google maps api map every month.this is a quite an incredible distribution. as we talk about that, it is interesting tothink about what kind of maps are these maps that make up the million, right? we have usedhotel booking sites. we used real estate sites. but they don't make up the 1 million. the1 million has typically been made up of really
kind of local, innovative, inspirational mapsthat developers have created themselves because they had an idea or they saw a need in a localcommunity. that's how you get a million around the world. you do that in every country ofthe world and you will get a million sites. and so i just threw up an example here. thisis a transit simulator from brasov, which is a city in romania. how many of you haveheard of brasov? i see one hand. brasov is a city of about 350,000 people inromania. somebody in the city released transit data and then somebody else in the developmentcommunity created a map and an interactive simulator of that transit data.this kind of thing has been happening around the world 1 million times.here is another interesting map. this is an
aid map from haiti by an organization that'sa coalition of ngos who are providing aid after the earthquake in 2010 in haiti. whatthey do is they use this map to collaborate on sharing information about the projectsthey're doing so they can work more effectively together.in this case, this is an example of how people have used maps and the ability to overlaytheir own content on the maps for their specific use case in a way that saves lives.this is an application, planefinder, which if you remember the opening video in the keynote,it was actually featured there. it is a data visualization. developers have been creatingdata visualizations since the maps api came out.this one is fascinating. you click on any
airport in the world and it creates this fireworkexplosion in your browser, showing you where all the planes go. it is fascinating.this is another one here. we talk about ways people have used the google maps api withmashing it with other bits of data to create really compelling and important visualizations.this is a map of articles in wikipedia that reference a place or articles of a place.and the points on the map are colored based on how many words have been written aboutthat place. and what you get effectively is a populationdensity map. it's fascinating. here's another one, just to illustrate theways the maps api has been enabling communities. there is loads of typography on buildingsin london. now i'm not a typography specialist
or generally a person who spends a lot oftime looking at it. there are a lot of people in london who do, it turns out. and importantfor them is to document this and share it. well, of course, they've used google mapsapi map. instant street view is an interesting applicationwe saw show up. this is where people have started to take the maps api beyond just abasic map. and instant street view here works like google instant. you start typing in andit takes you to different places in the world with street view.finally, geoguessr, how many of you have played geoguessr? see loads of hands. loads of hands.fascinating. this is -- this is the latest viral site we've seen created with the mapsapi. very simple concept as they show you
a bit of street view from somewhere in theworld. and your job is to click on the map whereyou think the street view was taken. and you get points based on how close you were tothe right location. it is incredibly educational and insanely addictive. so if you haven'tplayed it, go try it out. now, it has been these kinds of applicationsthat have really inspired us. so what we decided to do is to put together a little video tributewhich i'm going to roll now and set up mano marks who will come and talk about the nextmillion maps. [ video playing ][ music ] [ video ends ]>>mano marks: wow. sorry, i prestaged my slide.
wow. so, i have been on the maps team, themaps and earth team since about -- since 2006, so about seven years now. and i get tearywhen i see that video. i get moved by the incredible changes that we've made in thedevelopers world but also in the world of the internet. in 2005, 2006, the mashup revolutionwas born and it started with people developing apps with the google maps api. that was thefirst monster mashup. people realized that they could take services that is a major corporationwas providing for free and mash them up with their own data. we have moved a long way sincethen as you have seen from the samples that ken has shown.but basically it's taking the power of maps and putting them in the hands of developersand putting them in the hands of people in
the world.i didn't do a little spinny thing on the "wow" like ken did. that's because i'm just spinningin my heart. okay. [ laughter ]so what i want to talk to you about now is the next million apps, the next million mapsand how we are taking maps to new platforms. you saw the new -- you saw the new googlemaps in the keynote, the preview and you saw it in berni's talk here.and what has become pretty clear to us -- and also to pretty much everyone is that mobileis the future, except it's not the future. mobile is not the future anymore; mobile isthe present. and when google maps started, it was enoughto serve map tiles to a browser, and that
was pretty revolutionary at the time. butwe've looked beyond that. and since the launch of android, we've been putting maps into thehands of mobile users. but what we really want to do is put the samemapping experience in the same map data into the hands of every major -- every user ona major platform. you see here we have web, mobile, androidand ios sdks. so we are really exciting that these are our major platforms. these are whatyou can see right now and what you can develop on right now.and the reason for that is that mobile data is about 13% of global internet traffic, accordingto mary meeker's internet trends report. 13%, but that's up considerably just from lastyear.
and in some places in the world, it is themajority of internet traffic. so we want to put powerful mapping experiences and powerfulmap data that google has and that google scale into your hands.so when i say "on-location," what i'm really talking about is this concept of on location,that your app is about more than just identifying where somebody is, but it is about givingthem the entire context in which they -- in which they are right now.it's about giving them data. it's about giving them, as you've seen, this idea of what -- whereare they going? not just knowing -- when you are building an app, you don't to just wantto know where somebody is and you don't want to just ask them where they're going, knowwhere they are going. get contextual information
from your users and build that into your applications.now, we see on the maps team that there are actually, we believe, three components tothis. now, there's the powerful visualization technologies in the browser and on androidand ios. there's also our on-location services. so we've talked a lot for years about ourplaces api, our directions api, our geocoding api, all of which can be used on a googlemaps application. and we've started recently talking about thisdata platform. i'm going to talk a little bit more about that in a minute because iwant to talk -- i want to update you on the visualization platform. now, as i mentionedbefore, maps have been about serving map tiles to a client application that then just simplyrenders those map tiles. that's what maps
have been in the browser. that's what mapshave been on mobile devices. in 2011, we released vector mapping on android. and in 2012, wereleased it on the -- on ios. so mobile actually took this idea of vector mapping, took thistechnology, and the first place we were able to start using it.awfully creaky stage. this is the first place that you were actuallyable to get vector mapping. and why is vector mapping important? because it can do all thoseinteresting things that you saw berni demonstrate. you can render data on the fly and respondto user inputs without having to worry about roundtripping once again to the server toget data back in and shove it back into your application.so that gives you really interesting things
like camera animation, and i want to actuallygive a quick demo of that. if i can find my demo now. oh, the demo was loaded into theother machine. nevermind. i'm going to move on.but basically allowing you to do -- many of the kinds of animations that you've seen bothin the video and live. we've shown you these kind of animations where you can zoom in,see these 3d buildings tilt and pan the map in a very smooth way.and we're going to be talking a lot about those in the two mobile sessions -- the twodedicated mobile sessions. ken? i don't know why that happened.so the two dedicated mobile sessions on ios
and android today and tomorrow as well asthroughout many of our different sessions the next couple of days. so we have 17 -- 17sessions and one codelab that will be taking place in the next few days.so i want to announce today that we're making updates to both the android and ios apis.so the android api got pushed. it was announced actually in the keynote with the new googleplay services update. you will get a new version of the android api -- the google maps androidapi v2. and we're also announcing that today we'rereleasing version 1.3 of the google maps sdk for ios.so the android api, as you know, is built into google play services, which means thatany device that has google play services automatically
gets updated. you get -- without you havingto do any work. so any updates, any improvements, bug fixes, performance management that wecan add automatically updated in the app. and it brings the power of the consumer, googlemaps' vector rendering engine into your applications. when we released in 2011, google maps forandroid, the first thing that developers asked is: how can i use this in my applications?now starting last november, you can. and the google maps sdk for ios is a staticlibrary that you can download and incorporate into your applications. and it brings in thepower of the google maps application for iphone and it is available on both iphone and ipaddevices. and it allows for very easy integration withgoogle maps and also allows you, therefore,
to use google's services on your google maps.and we also launched an url scheme that allows you to launch the google maps applicationfor iphone directly from your application if you don't want to use the sdk.let's talk a moment about this data platform. there's a couple of things i want to highlight.the first is the tracks api. so imagine you have an application that doestracking of your users or some asset or something. an application that, say, is a social applicationso you can track where your friends are located. now, imagine you wanted to send -- you wantedto know minute by minute where somebody using your application is. think about how manyqueries one person would be sending to your server in a day. say they're using it forten hours. that's an easy calculation.
once a minute for -- for an hour times ten.that's a lot of pings per person. imagine your application is used by 5,000 or 10,000people. to track where their friends are in any moment. you want to know at a frequencymore frequent than once per minute. that's a lot of queries hitting your server justto collect location information for individuals. we've set up the tracks api that allows youto do just that. it allows you to present information about -- to collect informationabout your users in google's cloud anonymously and then be able to track those users as theygo. so pulling down location information for each individual from google's cloud withoutstraining your resources. because we've figured out how to do these sorts of things.the other data platform that i'd like to mention
is google maps engine. brian called this outin the keynote. we're really excited about the google maps engine platform. now, mapsengine is a platform for uploading your geo data to our cloud services and then servingthat data out in the same infrastructure and the same way that we serve out data. so ifyou want to collaboratively work on an application on a set of data with a bunch of other peopleacross the globe and you want to use high end gis data and you don't necessarily -- notall your users are necessarily going to be developers, they might simply be users. youcan then load those up and build those out to scale so that you can serve out your datato a large number of users. one of the reasons why this is important is because, again, weget into these queries per second. so if you
have an application -- i'm going to say, sayyou are a local government officer and you have a gis shop for, say, the city of newyork. and a hurricane or some other kind of disaster comes, a bunch of people might behitting your site to find out information about where to find shelters, where to evacuate,all that sort of thing. if all that is running off of google's data centers, which are replicatedaround the world, you don't have to worry that your servers are going to go down. it'sserved over the same infrastructure that we use to serve out google earth and google maps,and then we allow you to communicate that to your users. you choose how many and who.you can -- it's basically like google docs, you can choose to share it with only a fewpeople. you can share it broadly. you can
share it with just an url. and then you can-- you can serve that out to as many -- as many people as you want. you can serve itout on whatever devices you want people to reach as well. and we announced last weekthat we also added a new api for it. this allows you to programatically interact withthe google maps platform so you can upload data and you can edit data. you can interactwith your data dynamically in the google maps platform. we have traditionally sold thisto large enterprises but we wanted to -- we frequently get asked at google i/o, how cani play with it? and the great news is that you can play with it today. go to the -- ifyou're here at google i/o, go to the google maps sandbox and ask them to sign you up foran account for google maps engine and we will
give you a test account that will allow youto develop using the google maps engine platform. and then it will have api access and you canalso serve out those -- that data on top of the google maps javascript api using a mapsdata layer. so we're really excited that you are going to get a chance to play with thenewest, latest and greatest data platforms that we have on -- at google. i should alsomention that the tracks api is free to play with as well for a limited number of assetsthat you're tracking. so if you want to get started, if you wantto get started with the developer experience at google maps, go to developers.google.com/maps.also, some of us will be in the sandbox for the next three days. we're excited to talkto you about ow new platforms and how you're
going to get started using our apis. thankyou. [ applause ]i'm not going to take questions, sorry. we have seven minutes left. do you want to takequestions? ken will take questions and i will take questions, too. apparently we are takingquestions. we have seven minutes' time, so, before it runs out.>>mano marks: if you want to ask a question. please come to one of the mics here and ask.if you have a question, come to the mic. >>> with the new google maps api and the abilityto visualize the buildings in 3d, are you going to provide rendering solutions for peoplewho want to render stereoscopically. >>ken hoetmer: i think something might havegot lost in the translation. the update to
the google maps api is an update to the basemap tiles. we are not introducing any 3d functionality at this time.>>mano marks: in the mobile apis we have 3d buildings built in. we don't currently havea solution on mobile for rendering things stereoscopically.>>> on apple maps for ios you're allowed to inject your own map layer on top but it doesn'tseem that we're able to do that in the ios google maps app or anything like that whereasgoogle -- >>mano marks: are you talking about a tilelayer of some kind. >>> yeah, sure. where google has allowed youto inject the google map into your own effect. i'm wondering if that will be allowed in thefuture.
>>mano marks: it's built into the apple mapsapplication. we a comment on future features for google maps. we're really excited thatpeople can build this, though, into their own applications.>>>hi. how's it going? >>> it's good. i have a question about thetracks api, how different the api is from the latitude api.>>mano marks: how different is the tracks api.>>> how different latitude api from tracks api?>>mano marks: latitude. so the tracks api is designed specifically for developers whowant to not be tied to other google apps like latitude or coordinate. they want to buildout their own. it's simply you assign an id
and you give a location and then you uploadbunches of crumbs of that. then you build out your own visualization.>>ken hoetmer: the simplest difference. latitude was about tracking people. tracks api is abouttracking anything that moves. you can put a gps sensor on anything and call it an assetand track it in the tracks api. >>> okay. thank you.>>> i notice -- sounds kind of crazy, but can google maps api be extended to lord ofthe rings or make a searchable map using, like, i don't know -- make a searchable middleearth. >>mano marks: yes, people have done that usingtile overlays to lay them on top of google maps. so, yeah, in fact, you can. and if youcan get gps to work, you can do it on a mobile
device. if you get gps to work in middle earth.>>ken hoetmer: google maps api has been based on an assumption that it's got the earth underneathit. that assumption doesn't need to hold. you can create, effectively, the same patchwork of tiles for some other world. which we used to have in the api for mars and moon.if you can create that and find that map for middle earth, you can definitely use the mapsapi for it. >>mano marks: you would create a custom maptype and you basically provide a mapping between what your world coordinates are and latitudeand longitude so the maps api knows how to interact with it. and, yeah, it's -- checkout gta4.net/map. you'll see the grand theft auto map rendered in using the maps api withcustom street view. very cool.
>>> thank you. of course. you can use gme,google maps engine, to do it as well. >>> this is a little bit bigger picture, isuppose. you talked about the progression from tiles to vectors and then to today'sannouncements of all search and intent and what you're going to be next as part of maps.where did that come from? was it always kind of, you know, something that was being developedin maps? the kind of new direction for maps as a contextual and intent-based tool.>>mano marks: do you want to answer that? >>ken hoetmer: we have the map here.>>brian mcclendon: i think the intent overall is what we've discovered is maps data arekind of the center of so many of your walk around carry the phone. so many of them -- aboutwhat the data, i think i think the maps, you
do start to -- geo fences, motion models,there are things that we will be able to do in your application.>>> my question is about google earth. so i've seen there's a lot of innovation withgoogle maps. you mentioned features and zoom out to space reminded me of google earth.can you comment on what the role between google maps and google earth is going to be.>>mano marks: it's basically the same team of people working on both applications. we'rein pretty early stages now with the new google maps and we're seeing a lot of evolution ofthe base platforms, the web, and earth. we can't announce it right now any changes toany other platforms that we haven't already announced. but, yeah, we're excited aboutthe possibilities that webgl will bring us
but also we have over a billion installs ofgoogle earth around the world and a very active user base.>>> thank you. >>> i have a higher level question that idon't know is fair to ask you guys but i'm going to anyway. you're delivering the newmaps apis through the google play services rather than through sort of platform levelchanges? i got the sense that that was coming out at a broader level for not just maps apisbut other stuff as well. i'm assuming that this is driven by platform update by oemsand operators. is this kind of a broader strategy that google is looking at in terms of keepingthe android platform fresh for developers but not being bound to the oems and operators?>>brian mcclendon: the simple answer is yes.
the advantage of google play services, andthe advantage of any dyanmic library is bug fixes, updates and the like. and with theservices going all the way back to froyo, it gives developers the opportunity to reacha wider audience. >>> do you guys see that extending furtherbeyond what was announced today? is that a broader endemic like api strategy?>>brian mcclendon: i think the first version came out a few months ago. i think it is anongoing process. >>ken hoetmer: take this as the last questionas we are a minute over. >>> so one of the nice features is to takeour own kml file and have it integrated onto google maps rather than just integrating googlemaps into our own website. do you have additional
features with the latest google maps versionwhich allows for more context specific retrieval of data and kml or is there anything sortof back and forth that we can do that will allow for that interaction to be more intelligent?>>mano marks: we don't have anything to announce at this point around kml rendering and thenew google maps. so certainly kml is a standard that we helped pioneer through keyhole andthen google earth and we gave away to the world and we're still committed it and itis very exciting. >>mano marks: thanks a lot everyone. see youin the sandbox. [ applause ]
Thanks for reading Futuristic Garage Design. Please share...!
0 Comment for "Futuristic Garage Design"