Can HAPI also become an IVOA Standard for Delivering Time Series Data?

A standardization effort in the Heliophysics community has results in the creation of a specification for accessing time series data. The Heliophysics Application Programmer’s Interface (HAPI) standard tries hard to stay away from any Heliophysics-specific requirements, so it is useful in any context where there is tabular data with consistent records over time. The interface itself is very simple and was created to be a kind of lowest common denominator representation of what was already being done. It could be useful for astronomers for two reasons: 1 it is now a good way to uniformly access many datasets and servers in Heliophysics, so people outside the field do not need to learn any data-center idiosyncrasies. It could also be useful to the astronomy community for its own use as a way to simply and efficiently deliver time series data products. We will describe basic features of HAPI for people in IVOA to help analyze the potential usefulness of HAPI for astronomy.

VOTable in Parquet (motivated by recent work on time-series analysis in Parquet)

We present a proposal for associating full VOTable metadata with an individual Parquet file or a partioned multi-file Parquet dataset, either by embedding the data in the Parquet file(s) or by wrapping existing Parquet files that can't be edited with VOTable metadata as an annotation.

Pulsar and FRB Radio Data Discovery and Access: an update from
INAF and RIG activities

The INAF radio archive recently completed a new data release
for time-domain observations (pulsars and FRBs) gathered with the
Sardinia Radio Telescope: after a quick recap about how the different
data formats are being handled, I will introduce the discussion about
the draft of the IVOA Note "Pulsar and FRB Radio Data Discovery and
Access" produced within the RIG. Thus, I will focus on the mapping of
the different data formats (e.g. PSRFITS/PSRCHIVE and FILTERBANK) onto
ObsCore DM and summarize the proposal of an extension table dedicated to
time-domain data. Also, issues like the identification of the
data_product_type and o_ucd are presented and addressed to the relevant
IVOA Working Groups.