Closed kmuehlbauer closed 1 year ago
Thanks for putting these together @kmuehlbauer
For georeferencing... @kmuehlbauer what would you think if we had an optional cartopy dependency? To deal with these projections?
@mgrover1 Do you refer to map-making? Could you elaborate a bit more with regard to what functionality you have in mind?
I am thinking in terms of projecting data as well - see the MetPy functionality here https://unidata.github.io/MetPy/latest/examples/XArray_Projections.html
Yes, I see, they use an accessor to get a cartopy crs object.
From my perspective we would just need to add the aeqd cartopy crs to Dataset/DataArray when creating xyz-coordinates if cartopy is available.
Yup! That makes sense!
Sorry for the delay here @kmuehlbauer ... prepping for our ARM/ASR meeting next week.
No worries @mgrover1. It's great we are this far already.
From my perspective we would just need to add the aeqd cartopy crs to Dataset/DataArray when creating xyz-coordinates if cartopy is available.
@mgrover1 I've though about that the last days and tinkered a bit with pyproj
. I've ended up with a workflow where we can use pyproj
to:
spatial_ref
- Variable)spatial_ref
or create on the fly if not available)The users would be able to wrap that into a cartopy.crs.Projection
and use it for plotting with cartopy.
That would leave us with only pyproj
/proj
as additional dependencies. We could even make this optional. I'll see if I can workout a PR from that.
@mgrover1 I've setup a PR with a minimal pyproj-based solution in #87.
@mgrover1 We might close this issue and #25, as we have the basic workable georeferencing available now. WDYT?
Agreed! Let's do it.
to not forget the items from #25: