GPSeismic

GPSeismic Version 2010.0 Release Notes

Highlights

Highlights include QuikMap's ability to request elevations from Google for the 
purpose of either creating DEMs or elevation profiles. Other highlights include
an overhaul of the mapping portions of both GPNav and GPLocator. Both applications
feature numerous new display capabilities.

General

1) In the ASCII Import Specifications dialog, if invalid records are found, then a 
a fading message box will be briefly displayed indicating a problem and a
file is created in the same folder as the imported file with the name of 
XXX_Invalid where XXX is the name of the imported file.  This file contains the 
offending line numbers and complete records.

Requested by Dave McGibbon of EnCana.

2) Modified the Satellite Prediction Utility to accommodate different PC settings
time formats that might be selected. An error would be generated if the date
format was not 'MM/dd/yyyy'.

Spotted by Clifford Wittig.

3) Modified the 'shape polygon file to XZO file' routine so that the user is prompted
for a field in the DBF database. The field contents are used to populate each
polygon's attribute in the XZO file.

Requested by Phil Bick of Breckenridge Exploration.

4) All applications now open in normal (non-maximized) mode but will remember
and open in the same position and state when re-opened. QuikMap, QuikLoad, QuikView
and QuikEdit now have high-color icons.

5) The Bingo Card template utility now includes the ability to scale all 
offset values and define multiple offsets in one step.

6) The handling of multi-resolution images (Mr.Sid and Jpeg2000) has been completely
overhauled in QuikMap, QuikView, and QuikLoad.  Previously, the user would set a memory
limit and the applications would load the highest resolution which fit within this limit.
Now, the applications dynamically load the optimal resolution based upon the current
zoom level. GPNav and GPLocator now fully support Mr.Sid and Jpeg2000 as well.

QuikMap

1) There is a new Image menu item called Google Elevations. This utility will
allow the user to specify a cell spacing for the map extents (or zoomed extents)
and create a Digital Elevation Model (DEM). The request and replies are sent
via the Internet so you will require an Internet connection. Google does not 
require an API key for this but it does impose upper limits for the number of 
elevations requested. A general guideline is to select a cell spacing that produces 
250 rows by 250 columns or fewer. Should you exceed the upper limit, Google will block
requests for 24 hours. Our suggestion is that you use this for small areas and
make sure you specify a large time between requests (e. g. 0.5 seconds or greater).

2) A second Google related utility is available from the QuikMap Grid Inverse dialog.
When you use Home-End on two points and display the dialog, the button for profile
is now a drop down button allows several choices, one of which will display an
elevation profile between the two points and a map. The map will display the
line path and can be zoomed and panned. The map type can be terrain, road,
satellite or hybrid types. When the cursor is moved across the elevation profile 
a marker is displayed at that point on the map. This utility requires and internet
connection.

3) In GPSQL, there is a new image-related utility called QuikMap Image Point. This 
sends the points in the query to QuikMap, however in the field selected dialog,
you are required to specify a field which contains the name of an image that
is associated with the point. The GPSQL Miscellaneous dialog has a setting for
the folder where the images are located. With this additional information,
QuikMap displays the point's associated image in a bubble when it is right-clicked.

On the QuikMap Miscellaneous Settings dialog, the 'Lines/Labels' tab page now
contains settings for the size of the popup. It also has an 'off' position if you
want to suppress the image popup. There is also a control to select the folder
that contains the images. This means that this feature is available at all times,
not just when it is launched from GPSQL.

4) There is now a directional arrow that is displayed in the bottom left of the display
that indicates the current direction of the azimuth in the status bar. This is the 
azimuth that is used for all inline and crossline dependent routines.

5)  There is a new item that is available if a grid definition file is opened. 
All lassoed points are moved to their bin center based on their station names.

Requested by Mike Adrian of STI Surveys.

6) A new Miscellaneous setting has been added. This setting is on the Program
Settings tab and is called 'Do not move points on the secondary layer'. With this 
checked, the polygon capture items of "Group Traverse", "Group Rotate", and "Move 
to Station Bin Center" will do nothing for points on the secondary layer.  In 
addition, when using the interactive move mode secondary points cannot be selected 
for moving.

This was requested by Mike Adrian of STI Surveys.

7) Selecting a file from the Most Recent Files list will open that file in the
Secondary layer if points exist in the initial layer.

Requested by Vince Hanrahan of CGGVeritas.

8)The multi-resolution bands of Mr. SID and Jpeg2000 images are now supported. Previously, 
the user had to choose a specific resolution to load. The current support allows 
automatic selection of the appropriate resolution at various zoom levels. Note that
when a Mr. SID layer is displayed in the layers dialog, there is a right-click
option which allows saving a specific resolution to a PNG image. The popup menu
for other image types remains unchanged.

9) By choosing an option in the 'Point Count' mode, the results from the last polygon
capture operation can be used to filter subsequent offset, interval, and proximity reports.

Requested by Brian Marsh.

10) All images which are loaded via Image-Load are now added to the Most Recent Files list.
These images can then be loaded at anytime by simply selecting then from the list.

Requested by Brian Marsh.

QuikLoad

1) Added an option in the 2D Pattern Builder for our friends in Canada. When the dialog
is displayed, check the option at lower right that says 'Configure For Great White 
North Stagger'. Enter the parameters for the first line on the right of the dialog. 
In the one row spreadsheet, enter from left to right, the number of tracks, the 
increment, track spacing, stagger value and number of staggers. The utility
creates a standard grid, but the stagger values dictate an inline offset pattern
for the lines created. For example, a stagger value of 15 and a 2 for the number
of staggers would produce the following:

0----0----0----0----0 (line preplotted normally)
-0----0----0----0----0 (line offset inline 15 m)
--0----0----0----0----0 (line offset inline 30 m)
0----0----0----0----0 (line preplotted normally)

...and so on

Requested by Mark Erion of Raymac Surveys.

QuikView

1) Added the ability to import Leica CST post-processed files from the Specific ASCII
Import utility.

Requested by Grant Domeij of Santos Inc.

2) Added the ability to import CEEDUCER Pro files from the Specific ASCII
Import utility.

Requested by Jan Quaak of CGGVeritas.

3) Added the ability to extract HDOP and VDOP from SurvCE Carlson data should
they be present.

Requested by Glyn Barnes of WesternGeco.

4) There is now a Miscellaneous setting for suppressing the db warnings for unverified
GPS base stations.

Requested by Michael Perdue.

5) There is now support for EGG97 European geoid model.

6) There has been a change in creating a project which involves the use of a
classical datum shift (Molodensky, Bursa Wolfe, Molodensky Badekas) and how the
user adjusts the height. When a project is created or modified in Project Manager, 
one dialog is used to select the Group, System, Datum, Units and the geoid model.
On this dialog, if the datum selection is classical, an option to apply the height
change from the datum shift is enabled. Selecting this also enables a second option
to apply the height change from the datum shift as a geoid correction. If you
elect to apply height change from the datum shift, the next dialog (which provides
for user fields) will automatically be initialized to create the project database
with an additional local ellipsoid height field.

In QuikView, when you are applying height change from classical datum shift (and 
the datum shift is classical), the local ellipsoid height of every surveyed point 
will be used in determining the local height and be placed in the database. Note 
that the WGS84 heights will not be affected by the choice to apply height change 
from a classical datum shift. On the QuikView Misceallaneous dialog, when the 
'Lock Transformation Parameters' option is checked, the controls to change 'Apply 
height change from classical datum shift' and the associated 'As geoid correction'
are disabled.

Requested by Glyn Barnes of WesternGeco.

7) When populating a database, the user entered fields for 'Processor' and
'Surveyor' are now persistent.

Requested by Brian Marsh.

8) Added support for extended Leica CST files which include post-processed
number of satellites and observation times.

Requested and sample data provided by Henry Jackson of Northeast Surveys.

GPSQL

1) The ability to create an image report relies on the image name existing in a
field and that the user has specified the folder specifying the image on the 
Miscellaneous dialog. Several new capabilities have been added. One is a new
QueryB menu item called Google Earth Point/Image. When selected, the field selection
dialog requires the field specifying the image be specified as for the image report.
However, this new routine creates a KML file in the image folder. When Google Earth
displays this file, you will see your points and when clicked on, the picture will
appear in a bubble. Because Google Earth displays the image without resizing or
rotating, a new utility in the Image Report dialog can be used to create a rotated 
resized image for all images in a designated folder. This utility could be used to 
provide a consistent set of oriented images for display in Google Earth.

A second new image-related utility is also in the QueryB menu and called QuikMap
Image Point. This sends the points in the query to QuikMap. QuikMap displays the
point's associated image in a bubble when it is right-clicked.

These additions were requested by Gary Schaeffer.

2) The Google Earth KML creation capabilities have been changed so that you are
always prompted for a file name (except for a point/image file which is placed
in the image folder.) The filename is used to name the data set rather than the
word, GPSeismic_data. Another change is that the point name is always written
to the KML file and if you elect not to display the point name, the scale is
set to zero for labels. This means you can always identify the point and turn on
the labels (increase scaling) if you want.

This was the result of a great idea from Alan Stanton of WesternGeco.

3) If you mess up the panels in the main interface, you can reset to the default
configuration using the 'Reset Panels' item in the Preferences menu.

4) When you create a shape point file and create a DBF database of all fields, the
field selection dialog now allows you to specify the number of decimal points in
the Station (value) field.

Requested by Michael Schlautmann of DMT.

5) The two query proximity test has been enhanced as follows. When initiating a
2D or 3D proximity test, and you elect to only determine the nearest point within
the threshold, an additional option becomes available. This option allows the user
to create a table within the currently opened database that contains the station
names from the two queries and the delta coordinate values. A second option can
limit the table to only those points whose names don't match. So for example if
you wanted to find all points in the postplot table that were very close to points
in the preplot table, but you only wanted those whose names differed, you would
use both of the new options. This new table is hard coded to be called 
'Proximity_Table' and is rewritten each time the utility is run. The table can be 
used in a query join (on station)) to isolate and possible update postplot or 
preplot records.

Requested by Glyn Barnes of WesternGeco.

6) A new Modifications menu item has been added called 'Compare Offsets To Bingo
Template'. You are prompted for a Bingo template, then the field selection dialog
prompts for three fields, Offset Inline, Offset Crossline and Bingo_Comparison. If
the last field does not exist, it is created. The field selection dialog also
requires a proximity threshold. For each record, the utility determines which
template offset falls within the threshold. A check is also made to see if the
offsets place the point 'on target'. A number is entered in the Bingo_Comparison
field for each record. A -1 indicates that the offsets did not match any template
offset nor did the offsets themselves fall within the threshold. A 0 (zero) indicates
that the offsets fell within the threshold, that is, the point was not offset. Any
other number indicates the template offset. For example a 5 would indicate that
the point's offset was the fifth one in the bingo template.

Requested by Glyn Barnes of WesternGeco.

7) When you select Define Metadata from the Preferences menu, you may now specify
a PRJ file. This file is copied into the folder you create a shape file in, but
it is renamed to the same name as the shape file.

Requested by Paul Geneau of CGGVeritas.

8) When initiating an operation using the field selection dialog, the applicable
controls are highlighted yellow to aid in informing the user about relevant options.

9) For SSC GPSView vibe files, added ability to derive station from concatenating 
all characters appearing in columns 156-172.

Requested by Jorg Schultz of DMT

Project Manager

1) The sequence of dialogs when creating a project has changed. The new sequence
is to specify the project name, followed by a dialog for specifying coordinate system
and geoid model, followed by the user database fields dialog, and finally ending
with the miscellaneous settings dialog. The dialog on which the coordinate system
is specified allows the user to choose height change from a classical datum
shift and if this is to be used as a geoid correction. If the user chooses
height change from classical datum shift, a new optional field on the users
fields dialog, called Local Ellipsoid Height, will be checked. See item 6 of the
QuikView section for more.

Requested by Glyn Barnes of WesternGeco.

GPMonitor

1) A modification was made so that multiple instances of GPMonitor could be run
as 'talkers' and 'listeners'. The talker will relay the input position to a 
designated IP address and computer port while the listener compares its input
position to the position sent from the talker (rather than the static user
entered position). In this manner, two DGPS positions can be compared and all
satellite monitoring is accommodated. The talker can send the position to up to
two ports (meaning there can be two listeners).

There is now a separate 1 second timer that monitors the last time GPMonitor saw 
data from the port. If the Data Age QC parameters are exceeded, two new panels 
at the bottom of the application will indicate that with color changes (and a 
sound if that option is checked on the QC dialog):

There are two new buttons to save the current configuration and retrieve a 
configuration. These files have a .MBK extension for Monitor BacKup.

At the bottom of the dialog is a dropdown with the numbers 1-3 selectable, then
a textbox, then a button. You can select a number from the dropdown,
type in a name, then press the button. This can aid in identifying an instances 
role.

Requeste by CGGVeritas.

GPNav

1) There has been a complete re-write of the mapping portion of this application. 
There is one capability that has been removed, that being the ability to import
CAD layers. To compensate, a utility has been added to convert any DXF, DWG or 
DGN files to shape files. The new GPNav has numerous new capabilities. This includes
the ability to display 9 tracking objects. These include a vehicle symbol, a 
user defined vehicle outline, a secondary vehicle system, a snail trail, a target
symbol, a line to target, a target offset priority array, and two range circles 
that can be fixed to the vehicle or target.

All tracking objects are highly customizable. The vehicle outline is now user
defined and can accurately reflect any vehicle or vessel of any complexity. The
target offset array is a user defined set of points around the target that
represents alternative target locations should the primary target location be
inaccessible. A secondary target can quickly be designated as the primary target
from a drop down list. All tracking objects can be turned on or off with a single 
click.

Other new capabilities include the ability to specify the visibility of each
layer based on minimum and maximum viewing extents. Another capability is the
ability to specify selected points for labeling. Yet another is the ability to
select any shape point layer as the target layer, not just the top layer. The
map information and map ruler capabilities are greatly enhanced.

There is also a rotated map viewer which can be set up to course up, inline azimuth
up, or user angle up. There is a perspective option that rescales portions of the map
so as to provide a non-zenith viewing angle.

GPLocator

1) There has been a complete re-write of the mapping portion of this application. 
There is one capability that has been removed, that being the ability to import
CAD layers. To compensate, a utility has been added to convert any DXF, DWG or 
DGN files to shape files. The new GPLocator is capable of displaying six tracking
objects. These include a vehicle symbol, a vehicle label, a vehicle CMG indicator,
alert halos, snail trails and proximity circle. All tracking objects can be turned 
on or off with a single click. There are over 30 symbol types including full color 
icons. Vehicles can be assigned to any one of 10 different groups to easily 
display just the vehicles the user is interested in.

Other new capabilities include the ability to specify the visibility of each
layer based on minimum and maximum viewing extents. Another capability is the
ability to specify selected points for labeling. Yet another is the ability to
select any shape point layer as the layer for station tracking, not just the top 
layer. There is now provision for multiple exclusion zone layers. The 
map information and map ruler capabilities are greatly enhanced.

The user can now assign vehicles to any of 10 groups and select the group to
display.

Finally, the maximum number of supported vehicles now stands at 130. This number
can now be set by the user. The range is 10-130 vehicles.

QuikCon

1) Now include comments when importing SUV files. When importing a SOL file, the 
SST file saved (if any) has the name of the input file. Removed the check box by 
the PCOD IP code. IP PCODs need to be defined but are never displayed when
viewing a QCN.

Requested by Jan Quaak of CGGVeritas.

GPArc

1) Increased the number of unique rendering colors for polygon shape layers from 
10 to 20.

Requested by Phil Bick of Breckenridge Exploration.

2011.3 |2011.2 |2011.1 |2011.0 |2010.4 |2010.3 |2010.2 |2010.1 |2010.0