This is a really impressive demo. Most virtual globes (e.g. Google Earth) separate the terrain, surface image and building data. Normally, these are sent to the client separately and merged in the graphics card: the surface image is texture mapped onto the terrain, and then the building data is drawn separately on top. Special routines are used to draw trees (e.g. billboards).
What Nokia have done here is to merge everything - terrain, surface image, buildings and trees - into the same model. They're still using the classic chunked level of detail approach, just with more complex models, which the graphics card handles with ease.
This requires more work on the server side to prepare the data, but once it is done it is really fast for the client. The main disadvantage is that the data ends up being very static - you can't move objects around, for example.
P.S. I'm currently working on open source WebGL globes like OpenWebGlobe (www.openwebglobe.org) and WebGLEarth (www.webglearth.org). If you're interested in this sort of thing, I recommend reading www.virtualglobebook.com .
What? It's not just merging the different datasets into models, it's an complete accurate 3d model of terrain from C3 Technologies (now owned by Apple, btw), they take thousands of low-altitude photos and do a photosynth-esque reconstruction.
Mmmh sorry but I have to disagree with you. I can't let you tell this without some corrections, non-expert people could take it as it is.
In short, your post is mainly uninformative.
>> Normally, these are sent to the client separately and merged in the graphics card
It means nothing. You moreover can't really know what the batching and draw calls scheme is in google earth nor in this nokia 3D maps.
>> Special routines are used to draw trees (e.g. billboards).
Mmmh. Ok ok. 3d applications are complicated, there is special routines for a lot of things btw...
>> What Nokia have done here is to merge everything - terrain, surface image, buildings and trees - into the same model.
I agree with that.. vulgarly. It does not mean there is one mesh and it isn't. It can be confusing.
What you mean is there is one skin.
>> They're still using the classic chunked level of detail approach, just with more complex models, which the graphics card handles with ease.
You don't know what the chunks and lod algorithm is and i guess it might be very innovative. Or not. Well but you are talking about the global chunked lod approach so you re right, but it can be very confusing. The LOD algorithm is probably very innovative.
>> This requires more work on the server side to prepare the data, but once it is done it is really fast for the client. The main disadvantage is that the data ends up being very static - you can't move objects around, for example.
This is just false. Please don't take it bad, people may be deceived by that and this is as false as possible. There is actually no benefit to explain why but it could looks like "there isn't any more server side preparation because the mesh is not construct on the fly, this is not faster in the client - you can't say it - it depends highly on the draw calls scheme, the vertex complexity, the textures fetches etc. etc. and the data are static you are right but yeah it is highly doubtful - 3D programmers are smart, take the example of moving BSPs in the quake engine, who could have say that BSPs can move...".
Anyway, thank you very much for the links and references, they are pretty interresting.
edit: please note that I'm trying to do all the efforts to make this post as constructive as possible.
The mapping team at Nokia is by far the best software development team in the organization (maybe with the exception of Trolltech/qt), and it's surviving the MSFT integration. It's (largely) the legacy of the successful acquisition of Gate5 in Berlin -- and somehow the team there was able to resist full assimilation into the Borg. I was talking to a Nokian today who commented that in Nokia, "Berlin is the new Helsinki".
Your friend is right. I freelanced there earlier this year to create a prototype of Ovi Maps on Windows Phone. I couldn't stay on to see the production version through (commitments in London), but what they shipped on the Lumia (Maps and Drive) is awesome.
[Edit] Earlier LAST year, this year's only a few days old ;-)
Can anyone fill us in on how they're collecting such accurate 3D detail for all these buildings? I mean are they flying airplanes with 360 degree cameras over the major cities at low altitude, for instance?
The LIDAR data is also used in the Nokia City Scene app http://www.youtube.com/watch?v=_MxnUAVhdnU Worth noticing is that you can click on every building i.e. 3D information is combined with regular streetview data.
It's based on C3 Technologies' product, which was unfortunately acquired by Apple, so don't count on Nokia's contract being extended. It uses a custom aerial camera system and photogrammetry toolchain to create 3D data with minimal human intervention.
Australian company Nearmap started with exactly the same goals and have a similar product (custom aerial photography system with automated processing), but they don't seem to have figured the 3D photogrammetry part out yet.
Fantastic. Is there a way to create a link to a given viewpoint location/direction/zoomlevel? That would make it possible to share views of the world, always nice.
When zoomed into an area for which there is 3D building coverage, it feels almost game-like. And I say that from a vantage point of some relevance. :)
I wonder how photography will be affected by this sort of technology in the not so distant future, as the images and point cloud data increase in definition. For instance, instead of waiting for the perfect weather conditions for the desired picture, the "photographer" could simply manipulate lighting and such, then render the scene in high definition.
It looks as good or better than google earth, particularly the trees, but the (texture) caching seems to be limited, which could be obviated by using local storage.
In my area (Canary Wharf in London) with Google I can see the Crossrail works going on but there nothing happening on the Nokia maps so Google is more recent here.
First time I saw Google Street View, I was sitting on my balcony with my laptop. I looked at the Google image for my street, and it was me sitting on the balcony with my laptop. I had to do a double-take before I realized the picture was taken a few weeks prior.
Amazing how well the software renders thousands of objects. On close inspection, I find the post-apocalyptic aesthetic of the rendering geometry very appealing. http://i.imgur.com/dNYer.jpg
It really kind of irks me when people complain about standards in a web demo. HTML5 is not standardized. These demos are no more than POCs written to show what the technology is capable of and where the organization sees themselves going forward.
When you see run-the-business type web apps being written in non standard technology, then you can complain. When you see a neat toy being written in non standard technology, take it for what it is.
[+] [-] twp|14 years ago|reply
What Nokia have done here is to merge everything - terrain, surface image, buildings and trees - into the same model. They're still using the classic chunked level of detail approach, just with more complex models, which the graphics card handles with ease.
This requires more work on the server side to prepare the data, but once it is done it is really fast for the client. The main disadvantage is that the data ends up being very static - you can't move objects around, for example.
P.S. I'm currently working on open source WebGL globes like OpenWebGlobe (www.openwebglobe.org) and WebGLEarth (www.webglearth.org). If you're interested in this sort of thing, I recommend reading www.virtualglobebook.com .
[+] [-] espes|14 years ago|reply
[+] [-] yogrish|14 years ago|reply
[+] [-] FredBrach|14 years ago|reply
In short, your post is mainly uninformative.
>> Normally, these are sent to the client separately and merged in the graphics card
It means nothing. You moreover can't really know what the batching and draw calls scheme is in google earth nor in this nokia 3D maps.
>> Special routines are used to draw trees (e.g. billboards).
Mmmh. Ok ok. 3d applications are complicated, there is special routines for a lot of things btw...
>> What Nokia have done here is to merge everything - terrain, surface image, buildings and trees - into the same model.
I agree with that.. vulgarly. It does not mean there is one mesh and it isn't. It can be confusing. What you mean is there is one skin.
>> They're still using the classic chunked level of detail approach, just with more complex models, which the graphics card handles with ease.
You don't know what the chunks and lod algorithm is and i guess it might be very innovative. Or not. Well but you are talking about the global chunked lod approach so you re right, but it can be very confusing. The LOD algorithm is probably very innovative.
>> This requires more work on the server side to prepare the data, but once it is done it is really fast for the client. The main disadvantage is that the data ends up being very static - you can't move objects around, for example.
This is just false. Please don't take it bad, people may be deceived by that and this is as false as possible. There is actually no benefit to explain why but it could looks like "there isn't any more server side preparation because the mesh is not construct on the fly, this is not faster in the client - you can't say it - it depends highly on the draw calls scheme, the vertex complexity, the textures fetches etc. etc. and the data are static you are right but yeah it is highly doubtful - 3D programmers are smart, take the example of moving BSPs in the quake engine, who could have say that BSPs can move...".
Anyway, thank you very much for the links and references, they are pretty interresting.
edit: please note that I'm trying to do all the efforts to make this post as constructive as possible.
[+] [-] nobody_nowhere|14 years ago|reply
[+] [-] Spearchucker|14 years ago|reply
[Edit] Earlier LAST year, this year's only a few days old ;-)
[+] [-] micheljansen|14 years ago|reply
[+] [-] jasondavies|14 years ago|reply
[+] [-] roadnottaken|14 years ago|reply
[+] [-] te0006|14 years ago|reply
[+] [-] iconfinder|14 years ago|reply
[+] [-] Zirro|14 years ago|reply
Nokia scores a point with me here, if they keep delivering things like this I may even consider buying one of their phones one day.
[+] [-] adam-a|14 years ago|reply
[+] [-] lostsock|14 years ago|reply
[+] [-] Niten|14 years ago|reply
[+] [-] Geee|14 years ago|reply
The LIDAR data is also used in the Nokia City Scene app http://www.youtube.com/watch?v=_MxnUAVhdnU Worth noticing is that you can click on every building i.e. 3D information is combined with regular streetview data.
[+] [-] sern|14 years ago|reply
Australian company Nearmap started with exactly the same goals and have a similar product (custom aerial photography system with automated processing), but they don't seem to have figured the 3D photogrammetry part out yet.
[+] [-] andreadallera|14 years ago|reply
[+] [-] unwind|14 years ago|reply
When zoomed into an area for which there is 3D building coverage, it feels almost game-like. And I say that from a vantage point of some relevance. :)
[+] [-] rev087|14 years ago|reply
[+] [-] smhinsey|14 years ago|reply
[+] [-] blub|14 years ago|reply
[+] [-] bluena|14 years ago|reply
[+] [-] slug|14 years ago|reply
[+] [-] cpolk|14 years ago|reply
[+] [-] Alexx|14 years ago|reply
[+] [-] untog|14 years ago|reply
Stuff like this does look genuinely awesome, but Google Maps provides a whole different set of functionality. Searching, routing, etc.
[+] [-] Gerdus|14 years ago|reply
[+] [-] iaskwhy|14 years ago|reply
[+] [-] MindTwister|14 years ago|reply
[+] [-] bcowcher|14 years ago|reply
I tried zooming over my workplace in Darwin, AU and the building we work in isn't even there.. (its roughly 5years or so old)
I imagine there is probably a mash up of old/new map data in there depending on the population of a given place..
[+] [-] jamesbkel|14 years ago|reply
[+] [-] freehunter|14 years ago|reply
[+] [-] headShrinker|14 years ago|reply
[+] [-] kordless|14 years ago|reply
[+] [-] rospaya|14 years ago|reply
[+] [-] potyl|14 years ago|reply
[+] [-] jasondavies|14 years ago|reply
[+] [-] feralchimp|14 years ago|reply
On latest Chrome: There was a WebGL compatibility problem. Please check system settings.
Yay standards?
[+] [-] freehunter|14 years ago|reply
When you see run-the-business type web apps being written in non standard technology, then you can complain. When you see a neat toy being written in non standard technology, take it for what it is.
[+] [-] YourAnMoran|14 years ago|reply
[+] [-] artursapek|14 years ago|reply
[+] [-] Yaggo|14 years ago|reply
[+] [-] rplnt|14 years ago|reply
[+] [-] acgourley|14 years ago|reply
[+] [-] suyash|14 years ago|reply
[+] [-] recoiledsnake|14 years ago|reply