Supporting <group> in astropy.io.votable
See original GitHub issueThe VOTable recommendation includes a <group>
entity (see section 4.9 of IVOA VOTable). This grouping is used by several IVOA recommendation, for instance to specify that a set of columns containing coordinates are related to the same reference frame. As far as I could check, it is not possible to build a VOTable with grouped param
’s or field_ref
’s.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
VOTable XML Handling (astropy.io.votable) — Astropy v5.2
The astropy.io.votable sub-package converts VOTable XML files to and from ... There are a number of data storage formats supported by astropy.io.votable ....
Read more >VOTable XML handling (astropy.io.votable) — Astropy v1.0.4
There are a number of data storage formats supported by astropy.io.votable. The TABLEDATA format is XML-based and stores values as strings representing ...
Read more >astropy/tree.py at main - votable - GitHub
astropy/astropy/io/votable/tree.py ... Raises a `~astropy.io.votable.exceptions. ... This is a terrible hack to support Simple Image Access.
Read more >Reading and writing Table objects — Astropy v0.3.dev3797
A number of formats are automatically supported (see Built-in ... can be registered with the Table class (see I/O Registry (astropy.io.registry)).
Read more >Astropy Team
astropy.io.votable, Pey Lian Lim, Thomas Boch, Tom Donaldson, Pey Lian Lim ... performing (or helping perform) the release process for astropy-helpers ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
An additional problem is that writing out <GROUP>s at <RESOURCE> level is not supported. This turns out to be a simple bug for which I have developed a fix. Still working on the big can of worms of constructing acceptable test cases given that this only became possible in VOTable 1.2.
I hope this work will also lead to fixing the problem in the present issue; stay tuned.
(Note that reading <GROUP>s at <RESOURCE> level from a file became supported after #6262 was resolved in 2017.)
Yes, I think so. I was not sure that topic was the place to push for the implementation of
group
, specifically.