Create a merge project folder containing the following:
A)
- this jupyter notebook
- a copy of the dive files to be merged (_ppp.mb88 files)
- a copy of the corresponding datalists (_ppp.mb-1 datalists)
B)
- this jupyter notebook
- a copy of the dive files to be merged (_pp.mb88 files)
- a copy of the corresponding datalists (_pp.mb-1 datalists)
- a copy of the existing, corresponding navadjust project files
- Abyss0XXX_navadj.mb-1
- Abyss0XXX_navadj.dir folder
- Abyss0XXX_navadj.nvh
- Abyss0XXX_navadj_dx.txt
- Abyss0XXX_navadj_dy.txt
-*.rte files
-----
## Merge project
A) Data of each mission is shifted in respect to the above mentioned absolute navigation values, and/or referenced ship bathymetry (note the accuracies of available absolute navigation fixes!). So, each survey should be in the approximate right location. Disadvantage: set ties of previous navadjust-projects are lost. Therefore: **Prior to adjust overlapping areas, set ties within each survey to keep the previously adjusted navigation!**
B) Use the tool *mbnavadjustmerge* to merge existing, not shifted navadjust-projects. Advantage: set ties of previous projects are translated. Disadvantage: only relative navigation constrains. **Limited to maximum offset of 400m between merged surveys!**
-----
%% Cell type:markdown id: tags:
### Merge project - approach A)
#### Mission 0XXX1 + 0XXX2
*Enter short narrative of dive areas, overlap, and available navigation references.*
**Set up a new mbnavadjust project**
- File > New > Name navadjust project: navadjustProjectName
- File > Import Swath Data > Choose datalistdive0XXX1
- File > Import Swath Data > Choose datalistdive0XXX2
1) Set ties to keep internal navigation of each survey:
- View > Show Survey-vs-Survey Blocks > Choose Block survey 0 vs. survey 0 (subsequently 1 vs 1)
- View > Show Only Selected Survey-vs-Survey Block
- View > Show True Crossings > navadjust in NavErr window. Dismiss.
- View > Show Crossings with 50% overlap > navadjust in NavErr window. Dismiss.
- Action > Invert
2) Merge overlapping areas:
- View > Show Survey-vs-Survey Blocks > Choose Block with survey0 vs survey1
- View > Show Only Selected Survey-vs-Survey Block
- View > Show True Crossings > navadjust in NavErr window. **Set ties carefully!** Dismiss. Repeat itinerary on more detailled levels, if neccessary.
- Action > Invert
- Action > Apply Adjusted Navigation.
- File > Quit.
3) Check Quality, adjust, continue with adding a next mission.
- Navigation track is plausible and merged grid appears good: Continue with adding the next mission.
- Merged areas appear chaotic/erroneous: Carefully set some more ties.
- Renavigation causes a missfit in the survey, for which absolute navigation constrains are available: Set navigation of this survey as **good** and for the other ones as **poor**. Invert and apply navigation.
**Intermediate result**
*Enter narrative comment about navigation adjustment progress here.*
#### Mission 0XXX3
*Enter short narrative of dive areas, overlap, and available navigation references.*
**Adding data to existing mbnavadjust-project**
- Re-open mbnavajust project
- File > Import Swath Data > Choose datalistdive0XXX3
1) Set ties to keep internal navigation of each survey:
- View > Show Survey-vs-Survey Blocks > Choose Block survey 2 vs. survey 2
- View > Show Only Selected Survey-vs-Survey Block
- View > Show True Crossings > navadjust in NavErr window. Dismiss.
- View > Show Crossings with 50% overlap > navadjust in NavErr window. Dismiss.
- Action > Invert
2) Merge overlapping areas:
- View > Show Survey-vs-Survey Blocks > Choose Block with survey0 vs survey 2.
- View > Show Only Selected Survey-vs-Survey Block.
- View > Show True Crossings > navadjust in NavErr window. **Set ties carefully!** Dismiss.
- Repeat itinerary on survey1 vs survey2 block.
- Action > Invert
- Action > Apply Adjusted Navigation.
- File > Quit.
3) Check Quality, adjust, continue with adding a next mission.
%% Cell type:code id: tags:
``` python
!mbnavadjust
```
%% Cell type:code id: tags:
``` python
# process data using datalist automatically created by mbnavadjust
- Navigation track is plausible and merged grid appears good: Continue with adding the next dive.
- Merged areas appear chaotic/erroneous: Carefully set some more ties.
- Renavigation causes a missfit in the survey, for which absolute navigation constrains are available: Set navigation of this survey as **good** and for the other ones as **poor**. Invert and apply navigation.
**Intermediate result**
*Enter narrative comment about navigation adjustment progress here.*
#### Mission 0XXX4
*Enter short narrative of dive areas, overlap, and available navigation references.*
**Adding data to existing mbnavadjust-project**
Continue as described above until all dives are added and merged.
%% Cell type:code id: tags:
``` python
!mbnavadjust
```
%% Cell type:code id: tags:
``` python
# process data using datalist automatically created by mbnavadjust
- Navigation track is plausible and merged grid appears good: Continue with adding the next dive.
- Merged areas appear chaotic/erroneous: Carefully set some more ties.
- Renavigation causes a missfit in the survey, for which absolute navigation constrains are available (Check in GIS project): Set navigation of this survey as **good** and for the other ones as **poor**, then invert and apply navigation (in mbnavadjust).
**Intermediate result**
*Enter narrative comment about navigation adjustment progress here.*
#### Dive 0XXX4
*Enter short narrative of dive areas, overlap, and available navigation references.*
%% Cell type:code id: tags:
``` python
!mbnavadjust
```
%% Cell type:code id: tags:
``` python
# process data using datalist automatically created by mbnavadjust
*Enter narrative on the final result of the navigation adjustment here.*
-------
## Converting .mb88 Files into .xyz-data
To clean the navigation adjusted, shifted data, the sounding information must be exported to a file format readable by common MBES processing software, such as Qimera, or CARIS HIPS.