Query SOAR FoV Metadata for L2 Remote sensing instruments EUI, PHI and SPICE

Open
#8,766 8 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, data

Research direction

Start by reviewing the soar-sunpy package and its gallery examples, then inspect the TAP tables v_spice_fov, v_eui_hri_fov, and v_phi_hrt_fov and the sample ADQL request in the issue. Done means the package exposes the requested FoV metadata functionality and includes gallery examples for the EUI, PHI, and SPICE cases.

Written by the indexing model from the issue text.

Description

Feature Request net
Describe the feature

Recently the solar orbiter archive now has FoV metadata information available for all files via TAP for several remote sensing instruments and sensors:

  • EUI L2 HRI174 and HRI1216
  • PHI L2 HRT
  • SPICE L2

Detailed information about the columns including descriptions is available via the TAP tables page published at:
https://soar.esac.esa.int/soar-sl-tap/tap/tables

  • v_spice_fov
  • v_eui_hri_fov
  • v_phi_hrt_fov

Using standard metadata requests it is possible to retrieve FoV information about a given file or set of files:
For example for a given file:

But of course it is also possible to query on any column in the table. There are a few indexes in the columns

With this information it makes it 'quite easy' to make beautiful plots without the knowing the details and internal metadata of each instruments FITS files like:

image

As well as earth perspective:
image

And positional:
image

It could be nice to expose some of this functionality from the soar-sunpy package and also create some nice examples in the galleries

Proposed solution

Consider exposing some of this functionality via the soar-sunpy package and even creating a nice gallery

Dominant language
Python
Stars
1k
Forks
682
Avg merge
1d 17h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sunpy/sunpy

All issues in sunpy/sunpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.