New releases, Seafloor Planner, SFP releases

Seafloor Planner 2.3: What’s New?

Export receiver and shot tasks to CSV

Receiver tasks and shot tasks can now be exported to CSV format. These new export options are available in the File menu.

For shot tasks, columns exported are:

  • Vessel (vessel ID)
  • Task type (‘Shot’ or ‘Shot transit’)
  • Shot range
  • Patch #
  • Start time
  • Finish time
  • Duration
  • Cost
  • Distance travelled
  • Start easting
  • Start northing
  • End easting
  • End northing
  • Task heading
  • Source line length

For receiver tasks, columns exported are:

  • Vessel (vessel ID)
  • Task type (‘Lay receiver’, ‘Lay transit’, ‘Collect receiver’, or ‘Collect transit’)
  • Receiver line
  • Receivers (receiver range)
  • Start time
  • Finish time
  • Duration
  • Cost
  • Distance travelled
  • Start easting
  • Start northing
  • End easting
  • End northing
  • Task heading
  • Receiver line length
  • Number of recievers

Export CSV

New properties for multirole vessels

Multirole vessel speeds and other properties can now be configured separately for the vessel’s receiver tasks and the vessel’s shot tasks.

For laying and collecting receivers, available properties are: Turn Radius, Run In, Run Out, Transit Speed, Turn Speed, Laying Speed, and Collect Speed.

For shooting, available properties are: Turn Radius, Run In, Run Out, Transit Speed, Turn Speed, and Shooting Speed.

The vessel’s Cost Per Day applies at all times, regardless of whether the vessel is working with receivers or shooting.

Multirole vessel dialog

Import a source area from a polygon

Source locations can now be defined by importing a polygon. File format is the same as receiver polygon file format:

  • A polygon must be defined in a text file (.txt).
  • Vertices are listed in terms of easting, northing coordinates (in meters).
  • Vertices may be separated by commas, tabs or spaces.
  • One vertex per line.
  • Comment lines must be prefixed with a hash (#).

Example (a five-vertex polygon):

# Shot area polygon
500000.00, 500000.00
500000.00, 505000.00
510000.00, 515000.00
515000.00, 515000.00
515000.00, 500000.00

SFP will generate source lines within the polygon according to specified properties, such as line spacing and azimuth.

This new source location option is available on the Templates tab of the Survey Parameters dialog, and adds to the three existing options: Generate source lines based on reciver-source offsets, import source lines from a file, and generate source lines in patterns relative to specific receiver lines.

Source area polygon import

New progress bar while survey is building

A progress bar is now displayed while a survey is being generated. The progress bar provides helpful information regarding the steps that SFP is following, particularly on large/complex surveys that may take some time to build.

Progress dialog

New method of calculating polygon area

Previously, receiver area and shot area were calculated using: mean average line spacing * sum of line lengths. This resulted in unexpected area figures when line spacing or receiver / shot spacing was affected by obstructions or gaps.

Now, area is calculated by finding the area around each individual receiver or shot, and merging those individual areas to find the full receiver polygon or shot polygon. The area of a single receiver or shot is considered to be 1 line spacing * 1 receiver or shot spacing. The mode average spacings, rounded to the nearest integer, are used.

This affects area statistics shown in the Summary statistics display, area statistics shown in the Selection Details display when a patch is selected, as well as the Patch Shot Outline and Patch Receiver Area shown on the survey map.

Patch area and statistics

Bug fixes and usability improvements

  • Usability: Status bar now shows full CRS name where available, rather than projection type.
  • Usability: Status bar now displays correct UTM CRS, if an SPS import file includes both UTM and transverse mercator projection headers.
  • Usability: A custom CRS can now be specified for an input file, whereas previously only CRSes available in the SRS Picker could be used.
  • Usability: SFP now retains line and receiver or shot numbers when importing these from SPS files, instead of generating new numbers.
  • Usability: Allowable range for easting and northing coordinates in receiver and source polygons has been expanded to (-2,000,000, 12,000,000).
  • Usability: Clearer Alerts panel message when attempting to import a shot point (from XPS) that has already been imported.
  • Usability: Title added at top of Summary or Simulation data when copied to clipboard.
  • Usability: New statistic, Cost Per sq km Receivers, added to Summary display.
  • Usability: When reading SPS files, SFP attempts to interpret them as SPS format 001, and if that fails, as format 2.1. Alerts panel now displays any errors encountered from both attemts, rather than only errors from the second attempt.
  • Usability: Task start time and end time added to Selection Properties display, when a vessel task is selected.
  • Usability: Clearer Alerts panel message when survey tasks are not built because source area/lines and receiver area/lines are too far apart.
  • Usability: When receiver lines are one receiver long, vessel now lays and collects in the crossline direction rather than switching to the inline direction for each single receiver.
  • Fixed: Area statistic and/or rendered polygon is sometimes inaccurate when receiver or shot area polygon is concave or has a hole in te middle.
  • Fixed: Patch optimizer sometimes doesn’t recognize that a single patch is the best solution.
  • Fixed: Number of Sources property is shown in Templates dialog, when source lines are being imported from a file.
  • Fixed: When exporting to SPS format, CRS is not exported corrrectly from projects that were created in older versions of SFP.
  • Fixed: When exporting to SPS format, generated shot point indices were starting at 0 not 1, and receiver line numbering was incrementing by 10000 on each line.
  • Fixed: Negative coordinates in receiver polygon files being interpreted as positive.
  • Fixed: Non-consecutive shot and receiver numbering when SPF-generated shot points and receivers are exported to SPS
  • Fixed: XPS exports: Shot points not in chronological order
  • Fixed: Patch Selection Details sometimes displays a negative patch area.
  • Fixed: Descriptive text is not shown when hovering over an item in the Summary or Simulation panels.
  • Fixed: No survey tasks created when patch sizing (lines) is greater than or equal to (number of receiver lines in survey + number of roll-by lines).
  • Fixed: SFP ignores Lay Ahead settings when laying out the first lines of a rolling spread survey.
  • Fixed: Run-outs are travelled at transit speed rather than shooting, laying or collecting speed.
  • Fixed: Crash on clicking just before the start of the timeline, while the simulation is playing.
  • Fixed: Crash on clicking Cancel while loading SPS files.
  • Fixed: Crash on attempting to load an XPS file that contains a shot point that does not exist in the matching SPS file.
  • Fixed: First Lay statistic in Selection Properties when a patch is selected is wrong.
  • Fixed: Progressive line indent is not indenting as expected.