Add ability to save/export a view

[Marc Tanenbaum]

A user requested the ability to save and share a specific Heatmapper setup with others on his team. This would presumably mean saving a view file (as JSON?) with Aggregation/Rendering choices. This file could then be exported, copied/emailed/stored in a repo, and then loaded back into the Heatmapper.

My presumption is that this prefs file would not include the Data Export URL, since that would be pretty insecure.

Open questions:

• Should we support multiple views, such that you could keep a list of your favorites?
• Should we include export of date ranges? This is a tricky question since under some conditions you might want to return to a specific date slice. Under others you might want the latest data for the given settings.

[Former user]

I know this is old, but the ability to save Heatmapper presets would be valuable. Then any user on the project could just select from a dropdown of predefined preset views to initialize all the Heatmapper parameters. Then they can modify ranges, etc. as desired from there.