Until we have fully integrated the Image in HoloViews with the data interfaces the existing geoviews Image and Contours plots should also support plotting non-geographic data. Currently this works but has two major issues:
1) The iris plotting calls do not respect the order of dimensions resulting in mislabeling of the axes.
2) The aspect on these plot types is set to 'equal' by default which is sensible for 'longitude' and 'latitude' since those exist in the same space but often results in very wide or tall plots.
The aspect issue should be easy enough to fix as we can just detect whether a plot is geographic using the is_geographic utility function in geoviews.element.geo and set the aspect accordingly.
The axis mislabeling is more problematic as it will require us to make changes to iris plotting functions so we can respect the order of coordinates in the cube if desired.
Until we have fully integrated the Image in HoloViews with the data interfaces the existing geoviews Image and Contours plots should also support plotting non-geographic data. Currently this works but has two major issues:
1) The iris plotting calls do not respect the order of dimensions resulting in mislabeling of the axes.
2) The aspect on these plot types is set to 'equal' by default which is sensible for 'longitude' and 'latitude' since those exist in the same space but often results in very wide or tall plots.
The aspect issue should be easy enough to fix as we can just detect whether a plot is geographic using the
is_geographic
utility function ingeoviews.element.geo
and set the aspect accordingly.The axis mislabeling is more problematic as it will require us to make changes to iris plotting functions so we can respect the order of coordinates in the cube if desired.