The Heliophysics Application Programmer’s Interface (HAPI) is a standard mechanism for accessing time series data. Because of its adoption at multiple Heliophysics (HP) and Space Weather (SW) data centers, it is now a useful way to reach many different resources within the community. It is also a COSPAR standard. The use of HAPI so far has been as a standard layer on top of a traditional mission or instrument archive, where HAPI lives alongside an existing, custom web-based computer interface. We will give highlights of recent additions to the specification which is now at version 3.0, with 3.1 around the corner. We also will present explorations into two new ways in which HAPI can be utilized. 1) HAPI as a way to access output from model runs, which can generate large volumes of data at various time cadences and spatial distributions. 2) HAPI as an interface over cloud-based data resources. In the cloud, HAPI can connect large volumes of data to scientist-friendly front-end analysis capabilities, such as a JupyterHub or potentially a Pangeo-like environment. The evolution of HAPI and its uses is expected to keep enhancing interoperability among Heliophysics and Space Weather resources.

Interoperability between datasets in Heliophysics and Planetary archives is increasingly important to address complex science questions about space weather and planetary plasma environments. Yet for cross-disciplinary studies, data ingestion is often a tedious, time-consuming process. We have developed the Heliophysics Application Programmer’s Interface (HAPI), a standard specification that captures a lowest common denominator method for accessing time series data. HAPI offers the ability to request data from multiple sources using a single interface, coupled with the ability to get identically formatted data from each source. HAPI has been recognized as a standard by the Committee on Space Research (COSPAR) and has gained adoption at multiple institutions in the US, including Goddard Space Flight Center’s Coordinated Data Analysis Web (GSFC/CDAWeb), the Planetary Data System Planetary Plasma Interactions Node (PDS/PPI), and the Laboratory for Atmospheric and Space Physics (LASP) Interactive Solar Irradiance Data Center (LISIRD). European plasma data centers such as the French Plasma Physics Data Centre (CDPP) and European Space Astronomy Centre (ESAC) are also in the process of adopting HAPI. We present an overview of the HAPI specification and describe how data centers can add HAPI access to their content. We also present how scientists can plot or download HAPI data using Python or using existing analysis tools such as Autoplot (Faden, 2010) and Space Physics Environment Data Analysis Software (SPEDAS) (Angelopoulos, 2019). Faden, J.B., Weigel, R.S., Merka, J. et al. Autoplot: a browser for scientific data on the web. Earth Sci Inform 3, 41–49 (2010). https://doi.org/10.1007/s12145-010-0049-0 Angelopoulos V, Cruce P, Drozdov A, et al. The Space Physics Environment Data Analysis System (SPEDAS). Space Sci Rev. 2019;215(1):9. doi:10.1007/s11214-018-0576-4

The Heliophysics Application Programmer’s Interface (HAPI) represents a grass-roots effort to develop a common interface that data providers can use to offer time series data for computer-to-computer data access. Multiple data centers with Heliophysics and Planetary data are adopting this emerging standard. Several scientific analysis packages (Autoplot, SPEDAS) seamlessly pull from HAPI servers, and we have created and are enhancing Python libraries that can be used to read HAPI data into useful data structures within personalized analysis code. The HAPI specification and supporting software are available on GitHub. We will discuss the latest developments of the HAPI specification, current server and client implementations, all in the context of the push for increased interoperability within Heliophysics and Planetary data analysis. https://hapi-server.github.io/

Das2 describes a collection of cooperating programs originally created to support daily review and analysis activities of the Cassini Radio and Plasma Wave Science (RPWS) investigation. The system proved useful and is now relied on for rapid access to working data sets from many planetary missions including Mars Express and Juno, as well as ground-based radio astronomy results from the Nançay Decameter Array and Long Wave Array 1. As more teams have begun using das2 tools, the need for updates to what was largely an in-house protocol have become apparent. Though Autoplot continues to be the most flexible and commonly used das2 client program, interfacing with other tools would benefit the research community. We will provide an overview of recent updates to the das2 interface definition supporting redundant servers and federated data source catalogs. We will describe a cross site deployment between Southwest Research Institute and the University of Iowa to aid collaboration among ASPERA-3 and MARSIS investigators. We will give an update on the status of new client libraries for NumPy and IDL, as well as das2 stream adapters for HAPI and VOTables. Finally, we will describe how working data sets can be published in-place by registering das2 data sources with a VESPA EPN-TAP service.

The ability to access time series data with one API would significantly enhance science data interoperability. The Heliophysics Application Programmers Interface (HAPI) is a simple, standardized mechanism for exposing time series data through a service. HAPI is being adopted by data centers within the Planetary and Heliophysics communities, especially for plasma, particle and field datasets. At the recent COSPAR meeting, the Panel on Space Weather passed a resolution encouraging data providers to have at minimum a HAPI server to deliver time series data. The COSPAR is now considering the resolution for full organizational endorsement. HAPI standardizes the two key parts of a data service: the request interface and the result format. The request interface is very simple and captures the common features of many existing data access services. For result formats, the HAPI specification allows several options, all of them streaming. Servers must provide a Comma Separated Value (CSV) result format, but may optionally provide a JSON or binary stream as well. The details of the request and result formats are described in the current version of the specification document, which is available at GitHub: https://github.com/hapi-server/data-specification. Several institutions have recently added HAPI-compliant access. These include the large Heliophysics archive at Goddard’s Coordinated Data Analysis Web (CDAWeb), as well as the Planetary Plasma Interactions node of the Planetary Data System, the Laboratory for Atmospheric and Space Physics at CU Boulder, the University of Iowa, George Mason University, and the Johns Hopkins University Applied Physics Lab. Multiple client options are available for accessing HAPI data from the growing number of servers. Autoplot (Faden, et al, 2010) and SPEDAS (http://spedas.org/wiki) both read HAPI data, and other clients (Java, Python, Matlab, IDL) can be downloaded from the HAPI Github project. The ease with which various providers have adapted existing servers to create a HAPI-compliant capability shows that it does capture a useful way to represent time series data. Because clients for reading HAPI data are also easy to create, we anticipate significant growth and interest in this emerging standard. Faden, et al, Earth Sci Inform (2010) 3:41–49, DOI 10.1007/s12145-010-0049-0