GNU Astronomy Utilities - Tasks: task #15912, VOTable input-output
You are not allowed to post comments on this tracker with your current authentication level.
task #15912: VOTable input-output
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Sun 07 Mar 2021 02:39:52 AM UTC | ||
Should Start On: | Sun 07 Mar 2021 12:00:00 AM UTC | Should be Finished on: | Sun 07 Mar 2021 12:00:00 AM UTC |
Category: | Libraries | Priority: | 5 - Normal |
Item Group: | Enhancement | Status: | None |
Privacy: | Public | Percent Complete: | 0% |
Assigned to: | None | Open/Closed: | Open |
Effort: | 0.00 |
Tue 09 Mar 2021 07:09:21 PM UTC, comment #3: |
Francois Ochsenbein <fochsenbein>![]() |
Sun 07 Mar 2021 09:00:02 PM UTC, comment #2: Thanks a lot for the great feedback François. Indeed, I really look forward to expanding the elements within 'gal_data_t' to preserve the rich metadata of VOTable. Hopefully as we start implementing VOTable, we'll see what is necessary at each level and implement it.
Here are some brainstorms on each point that just occurred to me and I am adding here only for the record (may be useful later!). We should discuss them each in separate tasks during the implementation phase of VOTable (tasks that spin-off from this one).
Adding VOTable features in Gnuastro will be a very productive step forward, it is an honor to do it with your help and guidance as the author of the standard :-). Thank you François. |
Mohammad Akhlaghi <makhlaghi>![]() |
Sun 07 Mar 2021 08:00:00 PM UTC, comment #1: The Generic data container will likely have to evolve to ensure that metadata are not lost between reading a VOTable and re-writing it ; for instance the UCD would have to be added, but also the groups of columns, the references linking columns & parameters ; I did not yet have a deep look at the section 10.3.6 which details this, but I will ! |
Francois Ochsenbein <fochsenbein>![]() |
Sun 07 Mar 2021 02:39:52 AM UTC, original submission:
The Virtual Observatory's VOTable format is an XML-based format for storing and sharing table data. It is one of the core formats used in the Virtual Observatory and thus heavily used in astronomy (for example see task #15911).
We should add features to read each necessary column of a VOTable into Gnuastro's Generic data container, very similar to what we do with plain-text tables or FITS tables.
There are several XML parser libraries that we can use, like libxml2 or expat. |
Mohammad Akhlaghi <makhlaghi>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-03-07 | makhlaghi | Carbon-Copy | - | ![]() |
Added -email is unavailable- |
I'm not sure to understand what is a "MACRO" in the first item about semantics in comment #2 ?
Yes a PARAM is like a FITS keyword — the problems with FITS keywords (other than the standard ones described in the FITS documents) is that they lack a lot of details (units, explanations, possibility of arrays, precision, etc.).
About parsing a VOTable in C, a colleague wrote a set of functions based on libxml2 which seems to work well − I should check whether it could be reused; it is rather small (1000 lines) but it only deals with TABLEDATA (pure xml) serialization. On the other hand, the XML structure is simple enough to envisage a dedicated code for VOTable without the complex machinery of libxml2...
There is also the code in the voclient by Mike Fitzpatrick: https://github.com/mjfitzpatrick/voclient/blob/master/libvotable/votParseP.h
Cheers, François