\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{NCO-JSON: A Flexible, Complete JavaScript Object Notation for netCDF}



\author[1]{Charles Zender}%
\affil[1]{University of California Irvine}%


\vspace{-1em}



  
  \date{May 27, 2024}


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





\selectlanguage{english}
\begin{abstract}
JavaScript Object Notation (JSON) is an increasingly popular text format
for data exchange. netCDF encapsulates the Common Data Model (CDM) and a
binary format for machine-independent and network-transparent storage of
scientific data and metadata. Previous netCDF-to-JSON translators have
been custom solutions with incomplete features, or based on more complex
formats than the CDM. Here we describe a flexible JSON format that
describes any classic or extended format netCDF dataset. This format,
called NCO-JSON, expresses the richness of the CDM and increases
interoperability between web services and netCDF data. NCO-JSON requires
no reserved keywords and so is completely compatible with all netCDF
datasets. It allows for selectable levels of fidelity to the original
data and metadata. The most concise and human-legible form of NCO-JSON
is also lossy. By design it distinguishes only the three atomic JSON
datatypes (float, string, and int). This suffices for many purposes yet
cannot guarantee bit-for-bit reproducibility of many netCDF datatypes,
especially in round-trip translations. NCO-JSON uses a more complex
object notation to encode the additional type information required to
reproduce netCDF datasets with full fidelity. We present the rules and
design of the NCO-JSON format, show results with real-world datasests,
quantify the space advantages vs. alternate formats (both JSON and XML),
and discuss corner cases and possible extensions.%
\end{abstract}%



\sloppy




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

