GPSeismic

GPSeismic Version 2009.3 Release Notes

General

1) A problem in selecting a geoid model from some applications on Windows XP
systems was fixed.

Spotted by Earl Dahl of WesternGeco.

2) In the COGO utility, added ability to compute center of a circle and radius 
of a circle given the coordinates of three points along the circumference of the 
circle.

3) Added a Swiss Oblique Mercator group and system to the geodetic database. As
well, we have added the ability to create a Swiss Oblique mercator projection
should there be any need to alter the normal defining parameters.

QuikLoad

1) Added ability to create a line production report using all uploaded points. When
initiated, the production parameters dialog is displayed which allows the user
to specify units, distance calculation method, station gaps to ignore, and whether 
to add an interval per line (e.g., a two point line could be equivalent to one
interval or two). The user can also elect to enter a specific text for comment
and whether to include a summary total line. The production report is then displayed
in the modern spreadsheet. The modern spreadsheet has been modified to allow a CSV
file of the spreadsheet contents to be created or appended. In this manner, it
would be possible to create a concise line summary of all points uploaded for a 
given day. If creating a CSV, the column headers are included. If appending, they 
are not.

Requested by Paul Geneau of CGGVeritas.

2) Added ability to batch transform files that have additional infomation in
the records. For example, you might have files that have station and coordinate
information, but also have numerous other information fields you want to preserve.
The new utility is call 'Batch Transform (in situ)' and is in the File Menu. You
are prompted with input folder, then output folder. Next the ASCII Import
Specifications dialog is displayed. On this dialog, you would specify the card
columns for station and coordinates. You would also check the 'Transform Data'
checkbox and specify input and output coordinate systems. Once that is done,
you will see the ASCII Export dialog where you specify the format of the output
file (typically, the same as the output). Except for the coordinates, all other
record data is preserved. Note that if no transformation is specified on the
ASCII Import Specifications dialog, then the user is prompted for the coordinate
system of the input coordinates so that local geographic coordinates can be 
computed if desired.

Requested by Glyn Barnes of WesternGeco.

QuikView

1) Added ability to create a line production report using all downloaded points. 
See Item one of the QuikLoad topic for details. Using this new feature, it
would be possible to create a concise line summary of all points in a download
file.

Requested by Paul Geneau of CGGVeritas.

2) When processing a Zupt file, after the adjustment and before importing into
the main QuikView interface, you can create a shape file of all coordinates. The
user specifies a name for the file and a point shape file and line shape file is
made. The underlying DBF database of the point file has all spreadsheet fields.

Requested by Jim McCarty of PGS Onshore.

QuikMap

1) A new Tools menu item has been included in the DEM Conversions dialog. It will 
take a LAS Lidar file as input and create a Surfer 7/8 binary DEM from it in the 
same folder, with the same name, but an extension of 'grd'. If this new utility
detects that the data is not regular, it prompts to see if the user wants to 
create an XYZ ASCII file from the LAS data or regularize the data using the Couthard
gridding method and create a GRD file.  If the user elects to do the latter, a 
dialog is presented that allows the user to specify the cell spacing.

Associated with this, if you convert Lidar XYZ data from the DEM dialog,
you will have the option of regularizing the data if it is determined that it isn't.

Requested by Tim Green of Destiny.

2) The Specific ASCII output is now available on the Outputs dialog. This will allow
the user to create any format file available in that utility (which currently are
POI, GPX, KML, GSI, and PCX.

Requested by Edgar Garcia of Geokinetics

3) Added ability to view the intermediate MP file. This is the file that is created
before creating the Garmin IMG file.

GPSQL

1) Added a thumbnail preview to the main user interface.  If a query is a single 
table query and there are two fields with the characters 'easting' in one and 
the characters 'northing' (case insensitive) in the other, then these fields are 
used to create a thumbnail map. The preview is created when the user double 
clicks the Count button. The only other requirement for the fields are that both 
are of type, double. In the case where there are more than one set of fields 
satisfying these conditions, the first fields encountered in the table are used. 
There is a Miscellaneous Options setting that allows you to prevent the operation 
should the number of records in the query exceed a value you specify (default 
is 30,000). Right clicking the preview allows you to send the query to QuikMap.

Requested by Bill Belichik

2) When creating DEM heights, the field selection dialog will now allow you to 
name the DEM height field.

Requested by Michael Schlautmann of DMT.

3) Fixed problem in Custom Report utility in variable width columns mode when
justifying to the selected column. Left justification was not being recognized.

Spotted by Edgar Garcia.

4) Fixed problem with the re-calculate offsets routine. When specifying text fields,
the utility would fail with certain criteria.

Spotted by Aaron Totten of STI Surveys

5) If you select multiple query name rows and right click, you are now prompted
for whether you want to change the color of those rows.

Requested by Snifford.

Project Manager

1) You can now add up to twenty user defined database fields when creating a
project. The previous number was ten.

Requested by Michael Schlautmann of DMT.

GPNav

1) Added ability to open a grid definition file. When open the nav data panel
will display cursor to bin center values and bin station. When navigating, the
vessel location to bin center and bin station are displayed.

2) Switched sub-title and main-title in pilot deviation indicator. Now, the offline
values appear as the large main-title and the sub-title displays mode.

Requested by Trace Maurin.

3) Added depth and height multipliers. These values are entered on the communications
dialog and are used to scale the heights and depths that are input. The values are
included in the log file. GPSQL has been modified to import these values if they 
exist.

4) Changed vehicle display method so that if a new position is not available, the old
position would continue to be displayed until a new position was available. Previously.
if the user had a fast data request rate yet the positions on the port were 
infrequent, the vessel position would not be displayed or flicker rapidly. This was also
done for the freeware QNav program.

5) Added support for Trimble $GPHDT heading message. In conjunction with this, the
user can now specify a value on the comms dialog that indicates how many headings
can be missed before GPNav reverts to CMG. For example, if the data request rate is
one second but the heading is available every 5 seconds, the user could elect to
specify 5 or 6 allowable missed headings. In this case GPNav will continue to use
the last valid heading until a new one is input.

Requested by Jan Quaak of CGGVeritas.

GPArc

1) There is a new utility menu item that says 'Create User Positioned TitleBlock'.
This action brings up a translucent dialog that allows the user to position and
size a representation of the title block.

Requested by Eric Collins.

QuikCon

1) Added Exit, Control Station Manager and Import DCO tool buttons. At the bottom of 
the preferences menu, an option to change the visibility of any tool button has
been added. The visibility of the PCOD number assignments were defaulted to
invisible.

Requested by Jan Quaak of CGGVeritas.

2) If trying to use 'Cut' after selecting a row, an error would result. Changed 
this to instruct user to select individual cells for any cut.

Spotted by Cliff Wittig.

3) The sunshot utility had a problem in computing the average grid azimuth,
however the individual grid azimuths were correct.

This was spotted by Edwin Trino.

GPLocator

1) Added a speed alert. GPLocator previously had only five alerts (checksum, 
data age, proximity, exclusion zone and stale position) and speed was not included. 
This new alert is configured on the Alerts tab page. The entered value represents 
the speed at which the alert comes on. The units are in whatever speed units you 
have selected on the General tab page. Note that the alerts have been re-arranged 
so they are more easily configured.

GPMonitor

1) Added a 2D scatter plot with configurable range rings.

Requested by Jan Quaak of CGGVeritas.

2010.4 |2010.3 |2010.2 |2010.1 |2010.0 |2009.4 |2009.3 |2009.2 |2009.1 |2009.0