Lay ahead by number of patches
A new layahead option, Patches, has been added to Survey Parameters – Templates. This option can be used to specify that a given number of receiver patches should be laid ahead of the active patch.
New surveys will default to a layahead of one patch.
If there are not enough receivers available to lay ahead by the specified number of patches, as many lines as possible will be laid. For example, on a layahead setting of one patch, if a full patch comprises 10 x 100-receiver lines and there are at least 1000 receivers available, then a full patch will be laid ahead. Whereas, if there are just 250 receivers available, then two lines will be laid ahead.
CSV export improvements
Additional columns have been added to CSV exports: Receiver vessel task exports now include a Patch # column, listing the patch or patches in which receivers included in that task are used. Source vessel task exports now include a Number Of Shots column, listing the number of shots in that shot task.
CSV export columns have also been reordered, so that if receiver and shot tasks are copied and pasted into one file, the columns will match up appropriately.
Columns in the receiver task CSV export are now:
- 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 (m)
- Number of recievers
- Patch #
Columns in the shooting task CSV export are now:
- Vessel (vessel ID)
- Task type (‘Shot’ or ‘Shot transit’)
- Source line
- Shot range
- Start time
- Finish time
- Duration
- Cost
- Distance travelled
- Start easting
- Start northing
- End easting
- End northing
- Task heading
- Source line length (m)
- Number of shots
- Patch #
CSV exports can be made from the file menu, and list all receiver tasks or all shooting tasks in the survey, in chronological order.
Bug fixes and usability improvements
- Usability: Greater tolerance for SPS files with empty lines, lines longer than 80 characters, and lines with no/minimal data.
- Usability: If tiling is on, tiles are now automatically recalculated if receivers or receiver positions are changed.
- Usability: When loading SPS or RPS files, points are now automatically sorted on each line (to achieve geometric order), and lines are sorted geometrically according to their midpoints. XPS surveys don’t sort/reorder, and still obey the relationships specified in the XPS file.
- Usability: Obstructions are now obeyed even when they don’t obscure shots or receivers.
- Usability: Receiver task tooltip (shown when hovering a receiver task in the timeline) now includes receiver numbers in this task.
- Usability: Shot task tooltip (shown when hovering a receiver task in timeline) now includes shot numbers in this task.
- Usability: Receiver range and patch number added to Selection Properties display for receiver tasks.
- Usability: Source line, patch number and shot range added to Selection Properties display for shot tasks.
- Usability: Datetime format in display panels adjusted to improve Excel compatibility.
- Usability: Improved syncing of tiling settings between Tile Configuration dialog and Survey Parameters dialog.
- Usability: Survey can now be zoomed out further than the survey area.
- Usability: Background image adjustments and obstruction name changes no longer require a plan rebuild.
- Usability: Downtime and start date changes no longer require a plan rebuild (statistics are still updated appropriately).
- Usability: Shot and receiver interval values now rounded to two decimal places internally when calculating mode intervals.
- Usability: Patch shot outline and patch shot areas are sometimes inaccurate when source lines are imported from SPS.
- Usability: Optimisations to speed up survey plan calculations, when dealing with surveys involving a large number of shot or receiver points.
- Usability: More accurate error message when attempting to use obstructions in XPS files.
- Fixed: Source offset not saved – reverts to 20 on closing and reopening project.
- Fixed: Receiver line column occurs in CSV export twice.
- Fixed: Crash when a vessel’s last action is a single-point task.
- Fixed: Obstructed turns occur too frequently for source vessels operating around obstructions.
- Fixed: Undo/redo dropdowns sometimes undo/redo fewer actions than expected.
- Fixed: Slow and sometimes inaccurate source line azimuth calculations, when importing lines from SPS and azimuth is near 0 degrees.