This is a bit tricky. While the general listing is easy to implement (likely using a bit more of OSgeo), getting the data onto some common or easy to make common grid is tough due to the size of these grids given a 1km resolution (or better).
An idea is to use EASE2 grid in general but give each downloaded swath an individual bounding box rectangle surrounding it on the EASE2 grid and just store that to h5. Thereby reducing the size to store while still making it easy to compile it to a pan-Antarctic/pan-Arctic view later on.
[ ] Implement API to also take line/polygon features (shape files?) as input for the listing/retrieval
[ ] Implement a way to store these data sets resampled on a pan-(Ant)Arctic but reduced grid (rectangular bounding box/envelope?)
This is a bit tricky. While the general listing is easy to implement (likely using a bit more of OSgeo), getting the data onto some common or easy to make common grid is tough due to the size of these grids given a 1km resolution (or better).
An idea is to use EASE2 grid in general but give each downloaded swath an individual bounding box rectangle surrounding it on the EASE2 grid and just store that to h5. Thereby reducing the size to store while still making it easy to compile it to a pan-Antarctic/pan-Arctic view later on.