Consider adding the following convince methods for geospatial scenarios.
Wishlist
[x] set_geospatial_data to store weather dataset and metadata dataframe to GeospatialScenario. Opposite of geospatial_data (should be renamed to get_geospatial_data).
[x] 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.
[x] Saving figures from plotting methods in pvdeg.geospatial like plot_sparse_analysis
[x] 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).
[x] remove KDtree from downselect calls. we should generate the kdtree from the scenario's metadata at runtime
[x] separate Scenario and GeospatialScenario into separate files.
[x] geospatial scenario display should show the attribute name for the dropdown
[x] dask client initialization method in GeospatialScenario, add to display
[x] materials access updates need to be implemented in Scenario #130
Consider adding the following convince methods for geospatial scenarios.
Wishlist
set_geospatial_datato store weather dataset and metadata dataframe toGeospatialScenario. Opposite ofgeospatial_data(should be renamed toget_geospatial_data).GeospatialScenarioplotting methods to pass kwargs to matplotlib or takefig,axresults so users can draw on their plots outside of the method.pvdeg.geospatiallikeplot_sparse_analysisScenarioandGeospatialScenariointo separate files.