## 4 Data Source and Pre-Processing  
The Juno spacecraft's 53-day orbit around Jupiter allows it to directly sample Jupiter's equatorial ionosphere [3]. An auxiliary information system's data are its most essential component. The position and velocity are examples of supplementary data, as are the target body size, shape, and orientation, records of monitoring plans, spacecraft and sensor instructions, and notes explaining how things performed. Coordinate and time systems serve as good examples of reference systems. During pre-flight, flight operations, and post-flight long-term data analysis, archives that facilitate easy and rapid access to data and other components of the information system are essential [15]. The American space research community strongly advocated the construction of improved information systems and their accompanying standards in 1982, to make fast access to and use of stored scientific data less of a pipe dream and more of an expectation [16]. The report recommends establishing standards and protocols for gathering and utilizing ancillary/engineering data to properly comprehend measurements from scientific instruments and cross-reference the results across different instruments and missions. This suggestion spawned the \"SPICE\" auxiliary information system at NASA. The SPICE implementation attempts to meet the previously described specified criteria. Kernels are a common name for the core SPICE datasets. Using SPICE kernels, space scientists and engineers may quickly and accurately access and utilize information about a spacecraft's location, orientation, and other auxiliary data [15]. The \"SPICE\" observation geometry information system is available to NASA flight projects and NASA-sponsored researchers through NASA's Navigation and Ancillary Information Facility (NAIF). This system is intended to support scientists in planning and analyzing scientific observations conducted by space-based instruments on robotic planetary missions. Additionally, engineering duties connected to these missions are supported by SPICE via its usage in this capacity. Although planetary exploration was the primary emphasis when SPICE was first developed, it has now expanded to include applications in heliophysics and Earth science. There are no restrictions on who may use the SPICE system, as long as they adhere to the rules and guidelines outlined on SPICE's Support and Rules webpages. In addition, it is open to the general public, but only with little assistance from the NAIF. The first step in the SPICE implementation process is the generation of auxiliary data. An application program interface (API) is included in the SPICE Toolkit. Customers use it to read the SPICE auxiliary data files and calculate the derived observation geometry, like the height, lat/lon and illumination angles. Furthermore, many sorts of solar system events utilize these data. The Jet Propulsion Laboratory at the California Institute of Technology, working under contract with NASA, created the SPICE system. Dataset files were obtained from the Planetary Data System (PDS; [[https://naif.jpl.nasa.gov/naif/index.html](https://naif.jpl.nasa.gov/naif/index.html)]([https://naif.jpl.nasa.gov/naif/index.html](https://naif.jpl.nasa.gov/naif/index.html)) accessed on 22 January 2025). Data uniformity and consistency throughout space and time are crucial for spotting changes [17]. Pre-processing steps must be implemented to provide reliable data and forestall any possible mistakes. Pre-processing is a term borrowed from data mining that describes assembling, cleansing, normalizing, and transforming data [18]. The integration of data is an essential step that must be taken before matching and organizing information, as it is the only way to detect and eliminate data duplication and inconsistencies. Integration of remote sensing data is related to aligning visuals via rectifying and co-registration employing the same benchmark and control points.