Google Maps, Earth take on full 3D imagery
engadget.com
engadget.com
antr submitted[0] a better link[1] with video. Seekable press event[2] is also up with more information.
[0] http://news.ycombinator.com/item?id=4074972
[1] http://thenextweb.com/google/2012/06/06/google-maps-launches...
They only have 3D imagery in a few cities so far (click on the city markers).
- They used new imagery from planes to do this, not the existing streetview imagery - I guess that means optical matching of the kind needed to do this (make a model from streetview imagery) is still a ways off.
- 3d maps has been done like this already (by bing and others), though this looks a better resolution.
- As someone who works with city spaces - can I use the 3d data? How can I download it or who do I have to pay?
I don't work with city spaces and I would still kill to have access to the 3d data.
Bing appears to be using a non-scalable approach for Bird's Eye view. E.g., Seattle downtown contains a few 3d buildings in a very confined area. It might even be manually modeled.
What Google has announced is impressive because it is automated and scalable. Small demos are great and all (e.g. C3) but qualitatively different from getting something like this deployed into the real world.
Disclaimer: I work at Google.
We're talking about a whole lot of 3D rendering, many polygons, and a whole crapload of textures. Easy pickings for a smartphone native app, where just about every major phone on the market has obscene amounts of hardware acceleration under the hood.
Not so easy for desktops - whose graphical performance is often nearly non-existent. Not to mention you take another huge performance hit from WebGL... which also has poor penetration. So not only would most users be unable to use your newfangled 3D maps, many of the ones that can, will have an unusably slow experience.
This is one of those places where native apps really shine.
2000 - "Run this on a phone? You're crazy" 2012 - "Run this on a desktop? Insane!"
Current JS and WebGL performance is well within the range needed to make this work. MapsGL is already rendering a quite large workload, in fact, my intuition is that the 2D rendering, especially with rasterizing label text all over the place, is likely more expensive than navigating an octree and rendering a mesh.
In the demonstration they discussed how they do this, which is essentially Google Planes getting AirView with special cameras (very similar to Google StreetView).
And clearly Google is rattled as all of this comes just days before Apple is set to announce their products. I guess losing a significant amount of traffic (all iOS users) will do that to you.
Either way it will be nice for Google to have some honest competition.
I've seen the "mobile wars" bit about Apple dumping Google across the news world and it's a bit bizarre really as no one can state what Google gains from the current situation, but I guess just the glory of being iOS' mapping technology?
Go center the map on Roswell, NM. Search for "motel" and you'll see the ad, and it will come back as the default selected pin.
3D imaging alone is close to useless. Google already has superb mapping, navigation, traffic and information systems, and layer that atop just ensures that they miss no checklist items. It's going to be incredibly difficult for Apple to compete with Google's offering, especially given that the gimmick (which it really is) of 3D has been diffused.
I guess losing a significant amount of traffic (all iOS users) will do that to you.
I honestly don't get this line of thought. The rather terrible iOS mapping application has zero Google ads or integration with other Google services. Where is Google profiting from that situation?
While everyone is busy firing up the conspiracy that Apple is dumping Google, it seems far more logical that the dumping is going the other way, and has been underway for years (the Android mapping app is literally years ahead of the iOS mapping proggy).
Actually, the iOS Maps app does offer sponsored links. e.g. http://www.flickr.com/photos/mjaysplanet/6992735051/
I often see sponsored links when mapping stuff in the Bay Area; no clue how common they are elsewhere. (Though the above link is a screenshot of Maps in the Netherlands.)
Presumably Google, not Apple, is profiting from those sponsored links, but I've never seen confirmation either way. If it is Google, then they might see some fiscal impact when Apple stops driving iOS traffic their way.
(And I think it's far, far more likely that Apple's dumping Google. Apple's made key acquisitions for satellite imagery, spacial rendering, and mapping; Google already had that tech in-house. Why would Apple make such a large fiscal investment if they had no plans to ditch Google? Likewise, if they knew they'd move all their mapping tech in-house, why let Google make advancements on iOS? By keeping the Google-based Maps app simple, it's easier to wow customers when they deploy their own solution. If Google were allowed to innovate, then Apple would be forced to be on par, and likely would try to be better, when the Apple-based Maps app went live.)
I don't think that's correct. Apple makes the application, not Google. It's possible, but it seems unlikely that there's a clause in their contract that says, "we'll give you map tiles, you also have to show these sponsored links."
It would be great if Google brought a Maps app to iOS, if only for the competition.
A quick bit of Googling turned up the following confirmation that those ads are, in fact, sold by Google: http://thenextweb.com/apple/2012/01/06/hate-the-ads-in-the-i...
I fully expect Google will ship their own mapping app for iOS, if they're ousted from Maps. Also, it's not like there isn't already competition – searching for "maps" on the App Store reveals a healthy collection of mapping apps, including MapQuest and Garmin.
The biggest hurdle I foresee is in legislation - how is Joe the Plumber going to feel about a private company flying UAVs over his backyard taking pictures?
[1] http://www.gearthblog.com/blog/archives/2009/02/post_3.html
I want it. Want want want want.