2.2.2 Load local data

2.2.2.1       NetCDF data

Click the NetCDF button to import the .nc format satellite data stored in user’s own computer. The user can select the sub-dataset of .nc file that needs to be loaded (Figure 2-7), click “OK” to load it into 3D geosphere. Result is shown in Figure 2-8.


Figure  2‑7. Load NetCDF data
 
Figure  2‑8. NetCDF data loaded

2.2.2.2       HDF data

Users can also use SatCO2 software to open satellite data in .hdf format. However, users are required to provide the latitude and longitude ranges of the satellite data, as well as invalid value identification. (Other software can be used to obtain the above information such as the HDF explorer.)
After clicking the “HDF” button, a dialog box will pop up (Figure 2-9). Select the local HDF data to open and click "Next." After filling in the information such as “spatial range,” “No value,” “parameters,” etc. (Figure 2-10), the HDF data can be loaded into the 3D geosphere (Figure 2-11).


Figure  2‑9. Load user HDF data dialog


Figure  2‑10. Fill in the dialog box for information


Figure  2‑11. HDF data loaded

2.2.2.3       TIFF data

Click the “TIFF” button and select the local .tif data to load into the 3D geosphere.

2.2.2.4       In situ data

After clicking the "In-situ" button, the pop-up dialog box is used to import the local in situ data in .csv format (Figure 2-12).
The in situ data shall be pasted in the CSV table according to certain rules. Click the button of “generate template” in the window, and the .csv template can be exported to the local directory. The exported template is shown in Figure 2-13, where columns A to D are listed as required information (longitude, latitude, date, hour) and cannot be deleted. The user adds other parameters’ information in the follow-up columns. After pasting the corresponding data in the template and saving it, click the “load data” button to load it into the 3D geosphere (Figure 2-14).


Figure  2‑12. Load local in situ data dialog
 
Figure  2‑13. In situ data template
 
Figure  2‑14. In situ data loaded