Open ahuang11 opened 1 month ago
I'd be ok with assuming lat,lon inputs with geo=True
and projecting them using our own internal functions from HoloViews without having to bring in geoviews/cartopy/proj for that one common case. I would not be ok with checking the ranges and automatically converting; at best that could be a warning (maybe people really do want to look at some tiny area of the earth, or vice versa!).
Okay I think a warning is probably good, because without it, the data is centered around 0 and that can be confusing.
Sometimes, I don't want to use geoviews because it's extra dependency and import (and sometimes it breaks):
I'm wondering whether there should be a kwarg to transform so the above can be simplified down to
Or, if it detects the x is between -180, 360 and y is between -90, 90 without any crs/projection kwargs, automatically convert to easting/northing?