Nice!
But it'd be nicer with earth's rotational axis staying in the same place.
In app.js, switching from THREE.TrackballControls to THREE.OrbitControls will make it behave like this:
But it'd be nicer with earth's rotational axis staying in the same place.
In app.js, switching from THREE.TrackballControls to THREE.OrbitControls will make it behave like this:
Thank you.
http://callumprentice.github.io/
before commenting. These are quite impressive.
How much work did this one
http://callumprentice.github.io/apps/country_selector/index....
take?
How would you rate the difficulty of doing something similar with:
* clicking areas brings a popover for more info
* from PostGIS latlong polygons for, say, France's regions (and maybe hierarchical subdivisions)
* replacing polygons by ones with finer details as a region is being zoomed on
* coloring the regions according to a choosable statistic
* Not familiar with the data set you mention but so long as it's mostly documented it should be okay.
* I've never tackled the idea of a hierarchal map even with vectors so I don't know - with the right data, the bit I'm most concern about is the transition from one data set to the next.
* Coloring regions is straightforward
I don't have spare time to do it but am happy to help if you get stuck.
> the bit I'm most concern about is the transition from one data set to the next.
Yep. I have dabbled a tiny amount with three.js; my understanding is that there would be at least some kind of lag, as a new geometry is inserted into the pipeline. I don't know about trying to transition a mesh into another one.
> I don't have spare time to do it but am happy to help if you get stuck.
Damn, I was not expecting that you would even ponder doing it. You seem like such a nice person.
The context of my asking is a for professional project where some visualization could help in selling it. Customers love the shiny. If I go on doing it, I'll let you know!