Closed Cadair closed 2 years ago
EUI is currently available via the VSO. We are also currently working on making SPICE available via the VSO as well.
I'm going to close this as I'm not sure the value of tracking what the VSO serves belongs here - the goal of sunpy-soar
is to provide access to everything on the SOAR, and any coordination above that should be done somewhere else (perhaps at the SunPy ecosystem level).
This issue is part of the sunpy ecosystem, I don't know a better place to track it.
I think it's important that we start documenting overlap between different clients, because as is the case with the SUVI client in core at the moment the overlap (or more accurately the lack thereof) is actually kinda nuanced. Users being able to see when they might need to use sunpy-soar vs being able to use the VSO is valuable documentation in my mind.
Users being able to see when they might need to use sunpy-soar vs being able to use the VSO is valuable documentation in my mind.
Fair point. In that case I think an explanation along these lines best put in the README of this pacakge (which is also the docs for this package), and that's the action needed to close this issue.
Provide a general description of the issue or problem.
The VSO is already indexing some of the SOAR archive, this issue is to keep track of what products are and are not also downloadable through the VSO.
From speaking to Ed, I know that the EUI data are already accessible (without the ability to search on Level), if anyone knows anything else please let us know.