Read the statement by Michael Teeuw here.
Developing USGS Earthquake Map (2MB GIf warning) Topic 2
-
You can now also edit your posts, once you fixed your last bugs :) Just make sure the conversation stays understandable by not removing your original post but instead adding a second section:
Version 2
-
@croxis Thank you. The plan is to get it working and then release it as MMM-GlobeJS. Then try it using the WebGL rendering and release that one as MMM-GlobeGL. We’ll see if my ambitions get the better of me.
It only took a few hours to get the globe up, but my Javascript skills are rudimentary. Also, I haven’t tested this on a Pi, as I’m building the next mirror for my office and they gave me a FitLet PC to use for the project.
-
@bhepler would be nice to see it as one module with the ability to choose between canvas and webgl in config
-
@strawberry-3.141 Hah! Don’t ask for much, do you? Have you seen my Javascript skills?
That said… good idea!
-
I feel you on the javascript skills. I switched from canvas to svg and now nothing is rendering sigh.
The reason why I went with d3 (which planetary.js is based on) is because d3 can also render flat maps. Rasp pis might not have enough oomph to run spinning globes so my hope was to have flat maps as an option
-
@bhepler i guess if you can do it in two, you are also able to do it in one. if you can’t there are enough people to help
-
@croxis Flat maps? Intruiging. I hadn’t considered that as an option, but I suppose it makes sense. I did find Cesium, which appears to support flat maps natively (as well as a host of other very useful features). But It looks processor-intensive right out of the gate. I’m not even going to bother trying that one on a Pi.
@strawberry-3-141 True that. It’s not like we’re hurting for disk space on these things. Just memory and computational cycles. I’ll give it a go and if I hit any problems, I’ll reach out. Not here, of course. I’ll start a new thread.
-
@bhepler Just an update: The globe with planetary.js is a bit of a processor hog. On a quad core i3, it’s maxing one core and the other three hover between 40-80% at any given time. I’m going to try WebGL next and see if the hardware acceleration can reduce that.
The FitLet runs hot. Of course, that may be due to one core always maxed at 100%. Even just staring at the desktop.
