## 3 Implemented Results of Multi-Cloud Services
### Application Cases Using ODC UI  
The ODC Services in the architecture diagram shown in Figure 2 refer to various projects that utilize ODC. These include the ODC Explorer for data exploration, the Web Map Service (WMS), the Web Map Tile Service (WMTS), and Web Catalog Service (WCS), which are handled by the ODC Open Web Services (OWS), as well as the ODC UI, which is capable of processing spatiotemporal Network Common Data Form (netCDF) data. This study presents the registration of processed TOAR/TOCR data in ODC UI and showcases of the registration of the ODC API and the new ODC API.  
Figure 6: Results of synchronization of KOMPSAT-3/3A reflectance data on AWS S3.  
Figure 7: Web search results for ODC KOMPSAT TOCR data indexing on AWS cloud.  
the processing results. In ODC UI, the ingesting process incorporated Level-1G and TOCR data for processing. Direct processing of the ingested data in ODC UI is not possible. The functionalities integrated into the UI are called 'apps' and are designed as independent modules. Registration is carried out through the administrator page, where the content of Satellites, Area, Area products maps, and Applications, as depicted in Figure 8, is registered for use. Specifically, it is necessary to register the data with the apps responsible for the processing in the Applications section. Figure 8a illustrates the configuration of the region. Figure 8b,c represent the area for each function and the satellite image settings, respectively.  
Figure 9 presents the results of normalized difference vegetation index (NDVI) processing using the registered data and designated areas with sample image sets. Figure 9a shows the outcome of the ingested dataset. It displays the registered data areas on top of an OpenStreetMap background map using web mapping. It shows all ingested data in ODC. ODC UI is equipped with eight core functionalities, including five in the land category and three in the water category. It is built using the Python Django framework, allowing for the addition of user data processing capabilities in the future. Figure 9b represents the user interface of the spectral indices processing page. Users can select the pre-registered data through the Satellite option and choose the spectral indices. They have the option to select from seven different processing options, including NDVI, normalized difference water index (NDWI) to estimate the leaf water content at a canopy level, and enhanced vegetation index (EVI) to quantify vegetation greenness. By selecting the processing area on the map through geospatial bounds and specifying the time range, users can monitor the processing status asynchronously as shown in Figure 9c. Once the processing with KOMPSAT 3A TOCR is complete, the results of NDVI are displayed within the predefined color scale from \(-1.0\) to \(1.0\), as shown in Figure 9d. Figure 9e,f show the results of EVI and NDWI processing, respectively, in this ODC prototyping model. When KOMPSAT ARDs of multiple time periods are built into this system, it will be possible to perform time series analysis using these high-resolution image sets.  
Figure 8: User interfaces for ODC data processing: (**a**) Areas; (**b**) Application type; and (**c**) Satellite sensor type.  
Furthermore, the processed results can be accessed through the Results and Output tabs for various information and data downloads. In the Results tab Figure 9g, users can review the processing area and duration, as well as the list of processed data. Additionally, in the output tab Figure 9h, data can be downloaded in PNG, GeoTiff, or netCDF format.