Scribd
Upload
8 views3 pages

Data Import and Update Procedures Guide

Uploaded by

geologiteknikpatgtl
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views3 pages

Data Import and Update Procedures Guide

Uploaded by

geologiteknikpatgtl
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

*Tips before you start reading:

 Red content means the really important steps. Please read VERY CAREFULLY on these
lines.
 Black content means standard procedures that you need to go through.
 Grey content means you can skip this step if you want. Most of the grey content are only
related with graphical display, so if you’re too lazy to take a look at the result, forget it…

1. Standard Procedures for data import/data update


i. Create directory called ‘Data’. Under this directory, create a directory
called ‘SLC’. Put all your compressed data (or decompressed data) to
this folder.

ii. Open SARPROZ. Press ‘Select Dataset’, For Site Directory, select the
parent folder where you put your SLC folder.

iii. If this is the first time you process the data, a panel called ‘SLC Data
Processing’ will automatically pop up. If you are only updating the data, click
manually on the bottom ‘SLC Data import’ to update the data.
iv. Click ‘Get Content’ to extract data from the .[Link] zipped file. If the panel
shows ‘Sensors:***, Image Nr:*’, it means the procedure is successful.

v. Set orbits : You can choose ‘All’ or ‘Update’ according to your requirement.
When you see a selected date for ‘Master Selection’, and parameters in ‘Area
Selection’, it means the procedure is successful.

vi. You can choose to ‘view footprints’ and ‘view parameters’. In Linux System
you might have to manually start Google Earth after generating the footprint
kmz file.
vii. Select Master: The software can automatically select Master image. But if
you want to select the Master image by yourself, select it in the box ‘Master
Selection’.

viii. Area Selection: Select the Area of Interest. Notice: Select small area so that
the process time for data is shorter!! Don’t Select ALL THE AREA
unless you really need to!
How to select Area: Enter the Center latitude, longitude and radius. Then you
can press ENTER or TAB, and please notice that the pixels of samples and
lines should automatically change. Click on ‘view’ to open your defined area
in Google Earth. If you have to open google earth manually, all the kmz files
are in ~/RESULTS/GEO/.

ix. Master Extraction/ Vie w Master: If you’re only UPDATING data and did
not change Master, IGNORE THIS STEP. Else please do the extraction.
x. Slave Extraction: Click the button to extract slave images.

xi. Co-registration: This step takes a long time if you’re processing all the data.
If you choose ‘Update’, the software will only co-register the updated image
and the process will be quick.

xii. View master/ view slaves: View the data after extracted and co-registered.

xiii. Press Okay. The process is finished now. You can check out the data statistics
from the main interface ‘Dataset Statistics’.

Common questions

Powered by AI

Strategic considerations depend on the user's need for reprocessing completeness versus efficiency. Selecting 'all' reprocesses every dataset and ensures a consistent baseline across the whole dataset but is time-intensive. Choosing 'update' saves time by only addressing changes or additions, suitable when the existing dataset's integrity is trusted and only the new data needs processing .

In Linux systems, users may need to manually start Google Earth because the software does not automatically open it. This step is required to view the generated footprint kmz file related to the selected area of interest .

Automatic selection of a master image facilitates data processing by eliminating the need for user input, thereby streamlining workflow and reducing potential user errors. Manual selection might be needed when specific requirements or unique data characteristics necessitate the selection of a particular image as the master, allowing for more tailored data processing .

Slave extraction follows master image extraction to obtain subsequent images that will be co-registered to the master image. This step is necessary because it lays the groundwork for analyzing temporal changes in the dataset by ensuring consistency and comparability among the images, crucial for any differential analysis or time series interpretation .

Co-registration is crucial in the data import process as it aligns the slave images with the master image to ensure accurate data analysis. If co-registration is not performed accurately, it can lead to misalignment of images and incorrect data interpretations. This step is time-consuming when processing all data, but choosing 'Update' can expedite the process by only co-registering updated images .

The use of colored text for task prioritization helps users focus on crucial steps, with red indicating critical actions, black standard procedures, and grey skippable tasks. This color-coding directs attention effectively, ensuring critical steps are not overlooked while allowing users to efficiently manage their workflow by focusing on essential and urgent tasks .

Not selecting an appropriate area of interest can lead to unnecessarily long processing times if too large an area is chosen, as the software will take longer to process the data for larger areas. The document suggests selecting a small area to shorten process time unless it's necessary to include a larger area .

Setting the orbits is significant for maintaining the spatial reference consistency of the images. Choosing 'All' ensures all datasets are reprocessed, while 'Update' sets the orbits for newly added data only. Correct orbit setting is essential for reliable data analysis and maintaining data integrity across multiple updates .

Skipping graphical display steps affects the user's ability to visually verify the accuracy of the data processing steps, potentially leading to oversight of errors. While not crucial for the data processing itself, these visual confirmations can aid in ensuring data is correctly set and interpreted, particularly useful when accuracy is critical .

Visible indicators such as 'Sensors:***, Image Nr:*' act as confirmation points for users, increasing confidence that data import was successful. Absence of these indicators might raise doubts about whether the import process executed correctly, prompting users to troubleshoot potential issues, thus underscoring their importance in process validation .

You might also like