GeospatialScenario Quality of Life

[tobin-ford]

Consider adding the following convince methods for geospatial scenarios.

Wishlist

• set_geospatial_data to store weather dataset and metadata dataframe to GeospatialScenario. Opposite of geospatial_data (should be renamed to get_geospatial_data).
• Refactor GeospatialScenario plotting methods to pass kwargs to matplotlib or take fig, ax results so users can draw on their plots outside of the method.
• Saving figures from plotting methods in pvdeg.geospatial like plot_sparse_analysis
• Update ipython display method, to be more thorough. Show the weather dataset, display information about kestrel, show dask information, have builtin plot of coordinates (expandable).
• remove KDtree from downselect calls. we should generate the kdtree from the scenario's metadata at runtime
• separate Scenario and GeospatialScenario into separate files.
• geospatial scenario display should show the attribute name for the dropdown
• dask client initialization method in GeospatialScenario, add to display
• materials access updates need to be implemented in Scenario Materials access #130
• Dynamic rechunking of weather dataset Base chunk size on number of dask processes #119

[tobin-ford]

All of these are included in v0.5.0, with the exception of #119