scotttodd / chronographer Goto Github PK

Look into OpenStreetMap, Google Maps API, Google Earth API, etc?

Zooming behavior would need to be improved and integrated somehow. It might also help to replace the three.js particle rendering if something else fits better visually.

Trying to rotating south of the equator sends the camera up north.

Asset paths should be treated consistently

• images/circle_alpha.png in chronodata.js
• ../../dist/images in earth.js
• ../../third_party/images/cartographer.png in main.scs

Volcanic Explosivity Index data is present for some eruptions in the dataset.

Maybe use ProgressBar.js or SpinKit.

Send percent processed from chronodata.js? Or simply show a spinner with no estimate?

Rather than require to access as javascript strings (after building into a silly javascript file using a python script), read the files (synchronously or asynchronously if possible) like we did for Painterly Rendering. Maybe there is some other better way to approach this?

Untested in non-fullscreen div containers but window.innerWidth should be replaced with container.clientHeight or container.offsetHeight (see this stackoverflow post).

Rotation directions might be inverted in some cases

Use a CDN or other publicly hosted source for three.js and other javascript dependencies?

I think there are too many imports on each example page, but I don't want to package those libraries into the built main.js. How do other projects handle this?