PySPEDAS interface

[Beforerr]

There are some features I really like about Speasy like data caching. I am just wondering if it is possible to integrate this with PySPEDAS (since PySPEDAS could process data after loading and provides some dataset not available else where)?

Loading data in PySPEDAS is pretty standardized, so it should be possible to implement a "virtual" data provider that calls PySPEDAS underneath (similar to the customer file support in https://speasy.readthedocs.io/en/stable/user/direct_archive/direct_archive.html).

For exmample, the path "pyspedas/elfin/epd/elb_pif_nflux" would call "pyspedas.project.elfin.epd" underneath and return "elb_pif_nflux" data. But I am not sure if caching would work in this case. So I would like to hear some opinion on this.

[jeandet]

@Beforerr, this is technically possible, we could even cache calls.
The challenges I see are:

• global states inside PySPEDAS
• usage of slow/non threading friendly CDF library
• PySPEDAS is also downloading stuff on users disk

The best but maybe non realistic solution would be to make PySPEDAS use Speasy for data retrieval and agree on a common data container for ND time series.

A 3rd option, could be to build a simple PySPEDAS server like speasy_proxy.