MB-System Unix Manual Page

mbpreprocess

Section: MB-System 5.0 (1)
Updated: 28 November 2018
Index
 

NAME

mbpreprocess - performs preprocessing of swath sonar data as part of setting up an MB-System processing structure for a dataset.

 

VERSION

Version 5.0

 

SYNOPSIS

mbpreprocess [
--verbose --help --input=FILE --format=FORMATID
--platform-file=FILE --platform-target-sensor=RECORDID
--output-sensor-fnv
--nav-file=FILE --nav-file-format=FORMATID --nav-async=RECORDTYPE --nav-sensor=SENSORID
--sensordepth-file=FILE --sensordepth-file-format=FORMATID --sensordepth-async=RECORDTYPE --sensordepth-sensor=SENSORID
--heading-file=FILE --heading-file-format=FORMATID --heading-async=RECORDTYPE --heading-sensor=SENSORID
--altitude-file=FILE --altitude-file-format=FORMATID --altitude-async=RECORDTYPE --altitude-sensor=SENSORID
--attitude-file=FILE --attitude-file-format=FORMATID --attitude-async=RECORDTYPE --attitude-sensor=SENSORID
--soundspeed-file=FILE --soundspeed-file-format=FORMATID --soundspeed-async=RECORDTYPE --soundspeed-sensor=SENSORID
--time-latency-file=FILE --time-latency-file-format=FORMATID --time-latency-constant=SECONDS
--time-latency-apply-nav --time-latency-apply-sensordepth --time-latency-apply-heading
--time-latency-apply-attitude --time-latency-apply-altitude --time-latency-apply-all-ancilliary
--time-latency-apply-survey --time-latency-apply-all
--filter=SECONDS
--filter-apply-nav --filter-apply-sensordepth --filter-apply-heading
--filter-apply-attitude --filter-apply-altitude --filter-apply-all-ancilliary
--recalculate-bathymetry --no-change-survey --multibeam-sidescan-source=RECORDID --sounding-amplitude-filter=THRESHOLD --sounding-altitude-filter=THRESHOLD --ignore-water-column --head1-offsets=X/Y/Z/HEADING/ROLL/PITCH --head2-offsets=X/Y/Z/HEADING/ROLL/PITCH
--kluge-time-jumps=SECONDS --kluge-ancilliary-time-jumps=SECONDS --kluge-mbaripressure-time-jumps=THRESHOLD --kluge-beam-tweak=FACTOR --kluge-soundspeed-tweak=FACTOR --kluge-zero-attitude-correction --kluge-zero-alongtrack-angles --kluge-fix-wissl-timestamps
]

 

DESCRIPTION

MBpreprocess handles preprocessing of swath sonar data as part of setting up an MB-System processing structure for a dataset. This program replaces the several format-specific preprocessing programs found in MB-System version 5 releases with a single program for version 6. In many cases the preprocessing consists only of creating the ancillary files parallel to the raw files, but in others the data must be translated to different formats. The proprocessing step can also be used to merge navigation, attitude, sound speed, or other ancillary data with the survey data.

 

MB-SYSTEM AUTHORSHIP

David W. Caress

  Monterey Bay Aquarium Research Institute
Dale N. Chayes

  Center for Coastal and Ocean Mapping

  University of New Hampshire
Christian do Santos Ferreira

  MARUM - Center for Marine Environmental Sciences

  University of Bremen

 

OPTIONS

--help
This option causes mbconfig to print out its usage options and exit.
--verbose
By default mbpreprocess outputs minimal information to the shell. This option causes the program to indicate it's progress as it runs.

--input=FILE
Swath data file from which the input data will be read, or a datalist file containing a list of input swath data files and/or other datalist files. If FILE is a datalist file, then mbpreprocess will attempt to preprocess all data files identified by recursively reading the datalist structure referenced in FILE.
--format=FORMATID
Sets the MBIO integer format identifier for the input file FILE specified with the --input option. By default, mbpreprocess infers the format from the "*.mbXX" MB-System suffix convention.
--platform-file=FILE
--platform-target-sensor=SENSORID
--output-sensor-fnv
Causes mbpreprocess to output "fast navigation" or *.fnv files for each of the sensors described in the platform file specified with the --platform-file option. These *.fnv files will be corrected for the lever arms specified by the positional and angular offsets defined in the platform file.
--skip-existing

--nav-file=filename

Specifies an external file from which to merge sonar position (navigation), replacing any navigation data included in the input time series sidescan files. By default mbsslayout attempts to use navigation values included in the input data.
--nav-file-format=format_id

Specifies the format of an external navigation file from which position values are derived (as defined with --nav-file). Options for the format_id value are:

   1: ASCCI text file with lines of the form:
        time_d longitude latitude speed
      where time_d is time in decimal epoch seconds (seconds since 1970), longitude
      and latitude are in decimal degrees, and speed is in km/hour (and is optional).
      South latitudes are negative. Longitude may be defined on either the
      -180.0 to +180.0 or 0.0 to 360.0 domains.

   2: ASCCI text file with lines of the form:
        year month day hour minute second longitude latitude
      where year, month, day, hour, and minute values are integers, the second
      value is decimal, and longitude and latitude are in decimal degrees.
      South latitudes are negative. Longitude may be defined on either the
      -180.0 to +180.0 or 0.0 to 360.0 domains.

   3: ASCCI text file with lines of the form:
        year julian_day hour minute second longitude latitude
      where year, julian_day, hour, and minute values are integers, the second
      value is decimal, and longitude and latitude are in decimal degrees.
      South latitudes are negative. Longitude may be defined on either the
      -180.0 to +180.0 or 0.0 to 360.0 domains.

   4: ASCCI text file with lines of the form:
        year julian_day day_minute second longitude latitude
      where year, julian_day, and day_minute values are integers, the second
      value is decimal, and longitude and latitude are in decimal degrees.
      South latitudes are negative. Longitude may be defined on either the
      -180.0 to +180.0 or 0.0 to 360.0 domains.

   5: ASCCI text file in the 1990's era L-DEO processed nav format with lines
      of the form:
        yy+jjjhhmmssNddmmmmmmEdddmmmmmm
      where yy is the two digit year (after 1999 the "yy+" was replaced by a four
      digit year "yyyy"), jjj is the julian_day, hh is the hour, mm
      is minutes, and ss is seconds. The latitude is given as
      Nddmmmmmmand where N is 'N' for north and 'S' for south, dd are integer
      degrees, and mmmmmm is minutes * 10000. The longitude is given as
      Edddmmmmmmand where E is 'E' for east and 'W' for west, ddd are integer
      degrees, and mmmmmm is minutes * 10000.

   6 or 7: NMEA 0183 position strings
      Several NMEA and NMEA-like strings containing position are recognized,
      and can be parsed with and without line break characters. These strings
      include ZDA, GLL, GGA, DAT, and UNX.

   8: Simrad 90 format navigation files with lines
      of the form:
        ddmmyy hhmmssss ddmmmmmmmN dddmmmmmmmE
      where dd is day of the month, mm is the month, yy is the two digit year,
      hh is the hour, mm is the minute, and ssss is seconds * 100.
      The latitude is given as ddmmmmmmmN where dd are integer degrees,
      mmmmmmm is minutes * 100000, and N is 'N' for north and 'S' for south latitude.
      The longitude is given as dddmmmmmmmE where ddd are integer degrees,
      mmmmmmm is minutes * 100000, and E is 'E' for east and 'W' for west longitude.


      day_minute values are integers,
      the second value is decimal, and longitude and latitude are in decimal
      degrees. The longitude is given as
      Edddmmmmmmand where E is 'E' for east and 'W' for west, ddd are integer
      degrees, and mmmmm is minutes * 10000.

   9: ASCCI text file with white-space delimited lines of the form:
        yr mon day hour min sec time_d lon lat heading speed sensordepth*
      where yr is the four digit year, mon is the month, day is the day of the
      month, min is the minute, second is the decimal seconds, time_d is time in
      decimal epoch seconds (seconds since 1970), lon is the longitude
      in decimal degrees, lat is the latitude in decimal degrees, heading is in
      decimal degrees, speed is in km/hour, and sensordepth is in meters.
      South latitudes are negative. Longitude may be defined on either the
      -180.0 to +180.0 or 0.0 to 360.0 domains.

   10: R2R (Rolling deck to Repository) navigation format with ASCCI text lines
      of the form:
         yyyy-mm-ddThh:mm:ss.sssZ lon lat quality nsat dilution height
      where the lon and lat fields are in decimal degrees with south latitudes
      and west longitudes negative, and the last four quantities relating to
      GPS fix quality.

--nav-async=record_kind

Specifies the type of data records from which position values are derived (as defined with --nav-file-format). Options for the record_kind include:

    MB_DATA_DATA:  1 (survey data)
    MB_DATA_NAV:  12 (navigation data)
    MB_DATA_NAV1: 29 (navigation data from navigation system 1)
    MB_DATA_NAV2: 30 (navigation data from navigation system 2)
    MB_DATA_NAV3: 31 (navigation data from navigation system 3)
What types of data records are present is format-dependent, as is the default choice of which record type is used as the navigation source by default. The program mbinfo can be used with the -N option to determine the numbers of different record types present in a data file.
--nav-sensor=SENSORID

--sensordepth-file=FILE
--sensordepth-file-format=FORMATID
--sensordepth-async=RECORDTYPE
--sensordepth-sensor=SENSORID

--heading-file=FILE
--heading-file-format=FORMATID
--heading-async=RECORDTYPE
--heading-sensor=SENSORID

--altitude-file=FILE
--altitude-file-format=FORMATID
--altitude-async=RECORDTYPE
--altitude-sensor=SENSORID

--attitude-file=FILE
--attitude-file-format=FORMATID
--attitude-async=RECORDTYPE
--attitude-sensor=SENSORID

--soundspeed-file=FILE
--soundspeed-file-format=FORMATID
--soundspeed-async=RECORDTYPE
--soundspeed-sensor=SENSORID

--time-latency-file=FILE
--time-latency-file-format=FORMATID
--time-latency-constant=SECONDS
--time-latency-apply-nav
--time-latency-apply-sensordepth
--time-latency-apply-heading
--time-latency-apply-attitude
--time-latency-apply-altitude
--time-latency-apply-all-ancilliary
--time-latency-apply-survey
--time-latency-apply-all

--filter=SECONDS
--filter-apply-nav
--filter-apply-sensordepth
--filter-apply-heading
--filter-apply-attitude
--filter-apply-altitude
--filter-apply-all-ancilliary

--recalculate-bathymetry
--no-change-survey
--multibeam-sidescan-source=RECORDID
--sounding-amplitude-filter=THRESHOLD
--sounding-altitude-filter=THRESHOLD
--head1-offsets=X/Y/Z/HEADING/ROLL/PITCH
--head2-offsets=X/Y/Z/HEADING/ROLL/PITCH

--kluge-time-jumps=SECONDS
--kluge-ancilliary-time-jumps=SECONDS
--kluge-mbaripressure-time-jumps=SECONDS
--kluge-beam-tweak=FACTOR
--kluge-soundspeed-tweak=FACTOR
--kluge-zero-attitude-correction
--kluge-zero-alongtrack-angles
--kluge-fix-wissl-timestamps

 

EXAMPLES

To be written.....

 

SEE ALSO

mbsystem(1), mbdatalist(1), mbprocess(1)

 

BUGS

Oh yeah.


 

Index

NAME
VERSION
SYNOPSIS
DESCRIPTION
MB-SYSTEM AUTHORSHIP
OPTIONS
EXAMPLES
SEE ALSO
BUGS


Last Updated: 28 November 2018