When camera.roll = 0, the camera.changed event doesn't fire when changes only occur to the heading. e.g. if the user is looking down and rotates the camera. This causes issues with our compass not updating.

Sandcastle example:

Try the rotate buttons in the sandcastle below, you'll see that the camera.changed event is fired only when the roll =/= 0:
[Sandcastle](https://sandcastle.cesium.com

Please respect the following template to report a new issue, otherwise your issue will be automatically closed.

Before submitting, search through existing open or closed issues reports and through blender.stackexchange.com to check whether the issue already exists.

If the issue concerns an operator that grab geodata from an external web service (Basemaps, OSM, SRTM), then it can be a network

Currently the layer cannot be selected for low zoom levels.

I briefly looked some of the h3lib code via web interface, and they use malloc / free. Forgive me if h3lib can already configure to be used with other memory management routines.

I am wondering if it is possible to add configurable memory management routines other than malloc / free. I could certainly modify the code myself, but then it would create an upgrade / merge issue.

Basically, I a

Hello Maurits,
This is more of a request than it is an actual issue, but I think the value in this request is really high (for newcomers, especially - but not limited to).
Could you please add a COMPLETE application example of using the API (with user authentication, maybe even with the user-creation SQL script, table authorization, etc).
This would be really really helpful as a quickstart /

Is there a way to know when the imagery was collected? I assume sometime in the daylight hours, and probably recently(?) but I have no way of knowing by looking at the output and the associated image.

Can that output be put in the CLI output or some other metadata file that gets associated with the LC####### directory?

'react-autocomplete' (https://github.com/reactjs/react-autocomplete) is no longer maintained and causing warnings

react-dom.development.js:12357 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.
• R

Link for Pyrocko should point here: https://git.pyrocko.org/pyrocko/pyrocko rather than here https://github.com/pyrocko/pyrocko