astropy / astropy/astroquery

working with vastropy.io.votable

Open
#3,466 4 comments 0 reactions 0 assignees View on GitHub
vizier
Dominant language
Python
Stars
791
Forks
451
Avg merge
1d 3h
Merged PRs (30d)
4

Description

Both [DataOrigin](https://www.ivoa.net/documents/DataOrigin/) and [mivot](https://www.ivoa.net/documents/MIVOT/) require to access VOTable fragments which are not available in `astropy.table.Table`.

DataOrigin is available in the [data_origin module of astropy]( https://docs.astropy.org/en/stable/api/astropy.io.votable.dataorigin.DataOrigin.html). and mivot is available in the [MivotBlock module](https://docs.astropy.org/en/stable/api/astropy.io.votable.tree.MivotBlock.html)

However, astroquery (for instance astroquery.Vizier) can't access these votable fragments.

For instance: (VizieR example, but it is the same with other Services)

```
>>> from astroquery.vizier import Vizier
>>> vizier = Vizier()
>>>exoplanets_star = vizier.get_catalogs("J/ApJ/788/39")[0]
>>>type(exoplanets_star)

```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the VizieR example through astroquery.Vizier and inspect how the result becomes an astropy.table.Table. Read the referenced astropy.io.votable.dataorigin.DataOrigin and astropy.io.votable.tree.MivotBlock modules to determine what fragments are lost. Done means astroquery results expose the required VOTable fragments, with tests covering the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.