PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2016-11-07 INTERCHANGE_FORMAT = ASCII NOTE = "N/A" END_OBJECT = TEXT END JUNO JUNOCAM EXPERIMENT DATA RECORD (EDR), REDUCED DATA RECORD (RDR), AND GLOBAL MAP IMAGE ARCHIVE Table of Contents 1. - INTRODUCTION 2. - FILE FORMATS 3. - VOLUME CONTENTS, DIRECTORY, AND FILE NAMING CONVENTIONS 4. - CONTACTS FOR MORE INFORMATION 1. INTRODUCTION This volume contains the ancillary data files that support the JunoCam EDR, RDR, and Global Map Image archive. These files include an index file ('INDEX.TAB') that tabulates the contents of the volume and gives useful ancillary information, and documentation files. For more information on the contents and organization of the volume set refer to the 'Volume Contents, Directory, and File Naming Conventions' section of this document. The JunoCam EDR, RDR, and Global Image Map archive is compiled for the National Aeronautics and Space Administration (NASA) by Malin Space Science Systems personnel under the direction of Michael Caplinger, JunoCam Systems Engineer. Leslie Lipkaman, Daniel Krysak, and Robert Zimdar are responsible for its compilation. The image files are organized according to NASA's Planetary Data System (PDS) standards. An image file is organized as a PDS labeled file containing an "image object". 2. FILE FORMATS 2.1 Document File Format Document files with the .TXT suffix exist in the Root, INDEX, CATALOG, and DOCUMENT directories. They are ASCII files, which may have embedded PDS labels. Lines in a .TXT file end with a carriage return character and a line feed character. This allows the files to be readable under various operating systems. Documents in the DOCUMENT directory may contain formatting and figures that cannot be rendered as ASCII text. In such a case, a PDF (Portable Document Format) is used which is an open standard of Adobe Systems Incorporated that is frequently used for distributing documents. Adobe offers a free program, Acrobat Reader, for viewing PDF files. 2.2 Tabular File Format Tabular files (.TAB suffix) exist in the INDEX directory. Tabular files are ASCII files formatted for direct reading into many database management systems on various computers. All fields are separated by commas while character fields are enclosed in double quotation marks ("). (Character fields are padded with spaces to keep quotation marks in the same columns of successive records.) Character fields are left justified, and numeric fields are right justified. The "start byte" and "bytes" values listed in the labels do not include the commas between fields or the quotation marks surrounding character fields. The records are of fixed length, and the last two bytes of each record contain the ASCII carriage return and line feed characters. This allows a table to be treated as a fixed length record file on computers that support this file type and as a text file with embedded line delimiters on those that don't. All tabular files are described by PDS labels, either embedded at the beginning of the file or detached. If detached, the PDS label file has the same name as the data file it describes, with the extension .LBL; for example, the file INDEX.TAB is accompanied by the detached label file INDEX.LBL in the same directory. 2.3. PDS Label Format All data files in the archive have PDS labels, either attached at the beginning of the file or detached in a separate file. For examples of PDS labels, see the JunoCam Experiment Data Record (EDR) and Reduced Data Record (RDR) Data Products and Global Map Image Standard Data Product Software Interface Specifications (SIS). A PDS label, whether attached or detached from its associated file, provides descriptive information about the associated file. The PDS label is an object-oriented structure consisting of sets of 'keyword= value' declarations. The object to which the label refers (e.g. IMAGE, TABLE, etc.) is denoted by a statement of the form: ^object = location in which the carat character (^, also called a pointer in this context) indicates where to find the object. In an embedded label, the location is an integer representing the starting record number of the object (the first record in the file is record 1). In a detached label, the location denotes the name of the file containing the object, along with the starting record or byte number, if there is more than one object in the file. For example: ^HEADER = ("F01.IMG",1) ^IMAGE = ("F01.IMG",1025 ) indicates that the IMAGE object begins at byte 1025 of the file F01.IMG, in the same directory as the detached label file. ^MINIHEADER_TABLE = ("F01.DAT",0 ) ^DAT_TABLE = ( "F01.DAT", 64 ) indicates that the file begins with the mini-header which precedes the original binary data packet produced by the instrument and that the binary packet is 64 bytes from the first byte of the file. Lines of text in detached labels end with a carriage return character and a line feed character. This allows the files to be readable under various operating systems. 2.4. Catalog File Format Catalog files (suffix .CAT) exist in the Root and CATALOG directories. They are text files formatted in an object-oriented structure consisting of sets of 'keyword=value' declarations. 2.5. Science Data File Formats For information about the format and content of the data products, see the JunoCam Experiment Data Record (EDR) and Reduced Data Record (RDR) Data Products and Global Map Image Standard Data Product Software Interface Specifications (SIS). 3. VOLUME CONTENTS, DIRECTORY, AND FILE NAMING CONVENTION The files in this volume are organized starting at the root or 'parent' directory. Below the parent directory is a directory tree containing data, documentation, and index files. Directory names are indicated by brackets (<...>), upper-case letters indicate an actual directory or file name, and lower-case letters indicate the general form of a set of directory or file names. Top-level Directory ------------------- AAREADME.TXT The file you are currently reading. ERRATA.TXT This text file contains a listing of comments and updates concerning the archive volume. VOLDESC.CAT This text file contains a description of the volume contents as a PDS catalog object. It is a required file on PDS archive volumes. CATALOG Directory ----------------- The files in the CATALOG directory provide a top-level understanding of the mission, spacecraft, instruments, and data set. The files in this directory become part of the PDS Catalog to provide background information for the user searching for data. Their format and contents are further specified in the PDS Standards Reference. See the file CATINFO.TXT for details. DATA Directory -------------- The DATA directory contains version 1.0 of JunoCam CODMAC Level 2 EDRs, version 1.0 of JunoCam CODMAC Level 3 RDRs, and version 1.0 of JunoCam CODMAC level 4 Global Map products. CRUISE data can be found in Release 0001 (JNOJNC_0001). See JUNO_JNC_EDR_RDR_DPSIS.PDF and JUNO_JNC_GLOBAL_MAP_SIS.PDF in the DOCUMENT directory for a description of the different levels of data. DOCUMENT Directory ------------------ The DOCUMENT directory contains documentation to help the user understand and use the archive data. See DOCINFO.TXT for a description of the files in the DOCUMENT directory. INDEX Directory --------------- The INDEX directory contains PDS index files for this archive. An index file is an ASCII table with each record (or line) in the table containing information about a single data product in the archive. Files in the INDEX directory are provided to help the user locate products on the archive volume. See the file INDXINFO.TXT for additional details. DIRECTORY/FILE -------------- | -- AAREADME.TXT | -- CATALOG | -- CATINFO.TXT | -- DSMAP.CAT | -- JNC_EDR_IMG_DS.CAT | -- JNC_GLOBAL_MAP_DS.CAT | -- JNC_INST.CAT | -- JNC_PERSON.CAT | -- JNC_RDR_IMG_DS.CAT | -- JNC_REF.CAT | -- JUNO_INSTHOST.CAT | -- JUNO_MISSION.CAT | -- JUNO_REF.CAT | -- DATA | -- EDR | -- CRUISE | -- EFB | -- JUPITER | -- ORBIT_## | -- RDR | -- CRUISE | -- EFB | -- JUPITER | -- ORBIT_## | -- GLOBAL_MAP | -- DOCUMENT | -- DOCINFO.TXT | -- JUNO_JNC_EDR_RDR_DPSIS.HTM | -- JUNO_JNC_EDR_RDR_DPSIS.LBL | -- JUNO_JNC_EDR_RDR_DPSIS.PDF | -- JUNO_JNC_GLOBAL_MAP_SIS.HTM | -- JUNO_JNC_GLOBAL_MAP_SIS.LBL | -- JUNO_JNC_GLOBAL_MAP_SIS.PDF | -- ERRATA.TXT | -- EXTRAS | -- EXTRINFO.TXT | -- EDR_TIMING_OFFSETS.TXT | -- RDR_TIMING_OFFSETS.TXT | -- TIMING_OFFSETS_DESCRIPTION.TXT | -- INDEX* | -- VOLDESC.CAT * Directory and subsequent files will be provided by the Juno Science Operation Center (JSOC) 4. CONTACTS FOR MORE INFORMATION For details regarding generation of the JunoCam EDR & RDR archive: ---------------------------------------------------------------- Michael Caplinger Malin Space Science Systems PO Box 910148 San Diego CA 92191 jncdata@msss.com For overall content and design of the JunoCam EDR & RDR archive as presented on this volume: --------------------------------------------------------------- Leslie Lipkaman Vittling, Daniel Krysak & Robert Zimdar Malin Space Science Systems PO Box 910148 San Diego CA 92191 jncdata@msss.com