\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}



\usepackage{float}








\begin{document}

\title{Keeping Everyone HAPI: Achieving Interoperability for Heliophysics and
Planetary Time Series Data}



\author[1]{Jon Vandegriff}%
\author[2]{Robert Weigel}%
\author[3]{Jeremy Faden}%
\author[4]{Todd King}%
\author[5]{D Aaron Roberts}%
\author[6]{Bernard Harris}%
\author[6]{Robert Candey}%
\author[6]{Nand Lal}%
\author[7]{Douglas Lindholm}%
\author[7]{Thomas Baltzer}%
\author[5]{Scott Boardsen}%
\author[8]{Lawrence Brown}%
\author[9]{E. Grimes}%
\affil[1]{Johns Hopkins University Applied Physics Laboratory}%
\affil[2]{George Mason University}%
\affil[3]{Self Employed}%
\affil[4]{UCLA/ESS}%
\affil[5]{NASA Goddard SFC}%
\affil[6]{NASA Goddard Space Flight Cntr}%
\affil[7]{Laboratory for Atmospheric and Space Physics}%
\affil[8]{Applied Physics Laboratory Johns Hopkins}%
\affil[9]{University of California Los Angeles}%


\vspace{-1em}



  
  \date{May 27, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
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%
\end{abstract}%



\sloppy




\selectlanguage{english}
\FloatBarrier
\end{document}

