GPSeismic

GPSeismic Version 2009.0 Release Notes

Highlights

One highlight of the 2009 release is the ability to quickly retrieve map information
from Google and create and display a registered image in the background of your
application. You can specify road, satellite terrain or hybrid map types. You can
take a look at this on the following page:

http://www.gpseismic.com/google_maps.htm

A second often requested feature has been realized. It is now possible to create
and upload Garmin IMG files from QuikMap and GPSQL. QuikMap is capable of point
IMG files and creating IMG files from any vector file. GPSQL can create point, 
line or polygon IMG files from any query.You can
take a look at this on the following page:

http://www.gpseismic.com/img_maps.htm

General

1) As mentioned in the highlights, you can now quickly create a registered image
from map imagery obtained from Google. You can specify the resolution you want
as well as the map type (satellite, road, terrain or hybrid). For a closer look
at how this works, go to:

www.gpseismic.com/google_maps.htm

This feature is available in all applications that have a map interface.

This feature was requested by Steve Overmeer of Destiny

2) Again, as mentioned in highlights, it is now possible to create IMG files
from the GPSQL and QuikMap applications.

3) GPSeismic now includes a GPS monitor application. The monitor utilizes GGA, GSV
and GSA NMEA messages. It computes the difference between the the known and GPS
receiver coordinates and can log or relay these differences. 2D and 3D graphs
provide the user a unique perspective on the position and satellites.

4) Both QuikView and QuikLoad now support Leica System 1200 version 7 firmware.

5) QuikView, QuikLoad and QuikMap Layers/Image menu options now include the 
ability to set white as transparent for raster images.

6) The coordinate system transformation routine of the image registration utility
has been changed completely. When selected, you will be prompted for an image to
transform. A world registration file for the image must exist in the same folder
or you cannot proceed. You are prompted for the 'from' and 'to' coordinate'
systems and then a completely new image is created in the same folder as the 
original. This new routine compensates not only for rotation, but for any scale
factor differences between the two systems.

7) A new File Menu item has been added in the image registration utility. This is
called, "Remove Rotation From An Image (No Clipping)...". In the registration 
utility, when you click on several points and there is rotation present, you
have been able to rotate the image and save both the new image and a world file
for that rotated image. The same utility would prevent you from resizing the 
image during the rotation. This is still the case but the utility will now suggest
that you save the world file (with the rotation values) and use the new File Menu 
item. This new rotation utility prompts for the image to rotate and a new file 
to create. It uses the world file of the original image (with its rotation values) 
to create the new non-rotated image. This new image will not be clipped off due to the
rotation process.

QuikMap

1) QuikMap now has the Google image feature described in the General section.
Once any file is loaded, you can press the new Google Maps tool button or that
item from the Image menu. From there, follow steps indicated by the dialog. Once
you complete the steps, a registered image will appear in the dialog and you can
use this image in any application that support one.

2) QuikMap can now output points to an Garmin IMG file. This option is on the
Outputs dialog and can be used for any category of points. Also, when a vector
file is loaded, you can display the Layers dialog, then select and right click
on this layer. You will see a menu item that says Send To Garmin. Once selected,
you will be prompted for your coordinate system and what entities of the vector
file to use.

3) QuikMap now has a utility called Superimpose Images. This utility requires a 
COL file as input. The COL file contains the full path of each image and its 
accompanying registration file. Once a COL file is selected, it uses all images 
that the COL references and creates a single TIF image which covers the full 
extents of all images. The resolution of the new image will be the smallest
resolution of all input images. While  this function can be used to tile adjacent 
images together, one important feature of this utility is that it honors the 
transparency information in the COL file so that if images overlap, transparent 
colors will not step on non-transparent colors. Another possible use is that 
since you have one image rather than several, you can more easily perform 
routines such as raster search.

4) QuikMap now has a utility called Transplant Image Data. The utility requires a
recipient image, an XZO file, and, possibly, a donor image.  If a donor image is 
used, for each zone in the XZO file, it will copy the image from the donor image 
to the corresponding regions of the recipient image.  If a donor image is not 
used, for each zone in the XZO file, it will copy the colors from each zone to 
the corresponding regions of the recipient image. A new image is then created 
in the same folder, with the same extension, extents, registration, and of the 
same type of as the recipient image.  This routine can be used to eliminate 
repeating logo information or to color exclusion zones a solid color to use with 
the raster search technique.

5) Fresnel and curvature/refraction options have been added to the view shed 
analysis tool.

This was requested by Glyn Barnes of WesternGeco

6) The DEM conversion utility now has batch processing capabilities.

This was requested by Michael Schaultman of DMT

QuikView

1) QuikView now supports Leica System 1200 version 7 firmware.

2) The QuikView Layers/Image menu options now include the ability to set white 
as transparent for raster images.

3) Trimble Note records are now handled a bit differently. When QuikView sees a 
note record which contains the colon symbol (:), it will only use the text to the right 
of the colon and then strip leading and trailing spaces. QuikView will now ignore 
all comments which contain the text 'data copied from'. Finally, when multiple note 
records are found, QuikView will concatenate them using a semicolon as a delimiter 
for use as the Comment. Note that GPSQL has the ability too deal with delimited 
Comment fields.

These changes were requested by Didier Habert of CGGVeritas

QuikLoad

1) QuikLoad now supports Leica System 1200 version 7 firmware.

2) The QuikLoad Layers/Image menu options now include the ability to set white 
as transparent for raster images.

3) QuikLoad's Utility menu now includes an item called Specific ASCII. This new
item allows the user to create several ASCI format files from selected preplot
points. This includes POI Points Of Interest, GPX (GPS Exchange Format, "KML 
(Google Earth Keyhole Marup Language), GSI (Leica GSI 16 Conventional) and 
PCX (Garmin PCX5 Waypoint) formats. This new utility will allow for future
support of miscellaneous ASCII formats.

The POI output was requested by Jan Quaak of CggVeritas.

GPArc

1) GPArc is now compiled around ArcGis Engine 9.3.1. However, if you are still
using ArcGis 9.3 Service Pack 1, you can still run the new GPArc version.

2) The user entered angle for point labels will now be given priority so that they
will not turn to avoid polygon border crossings.

3) A new Utility item has been added to immediately insert Google Maps into the
background.

GPSQL

1) Added a new tab page in the Update Field(s) dialog which is called Flag Duplicates.
On this tab page, you select a field to base the duplicates on. For example, if you
select Station (value), then the utility will flag all points that have a duplicate
Station (value) in the query. The field to be modified can be a string, double, or
long field type. The only precaution is that if it is a string type, make sure the
entered text has the same or fewer characters than the size of the field.

The utility will insert the user text (or value) into the field of each record that
has a duplicate and report the number of duplicates at completion. In this case,
the complete number of duplicates is given. For example, if there are two stations
called ABC, then the number displayed at the end of the routine will be two, not
one.

One final note is that the routine will not place anything in or alter the field 
of a record that is not a duplicate. This means you might want to change all
records to some value or text prior to each use.

Requested by Peter Hall of Katy Geophysical.

2) The number of Query menu items was becoming too large so two menus were created.
These are called QueryA and QueryB.

3) Added the ability to create Garmin IMG point, line and polygon files from a
query. On the Miscellaneous options dialog you will find a button that launches 
a dialog that allows you to set the IMG parameters. These parameters include 
point, line and polygon codes as well as view levels.

4) GPSQL has been modified to warn the user if they try to add a field or 
change a field's name to a name that is used by another routine.

5) Added a GPNav import utility to the Import menu to facilitate data management
of that system.

GPLocator

1) Added ability to display all currently tracked vehicles in Google Earth.

2) A new Utility item has been added to immediately insert Google Maps into the
background. See the General section for details.

GPNav

1) On the Map Settings dialog, you will notice that the option to save the user
interface panel locations on next startup has been modified to include all menu and
toolbar settings.

Requested by Chris Steuck of Darby Services Inc.

2) Made a slight change to a log record. The first delimited item in "$GPNAV"
and the second is a complete date/time string. Previously, the first item was
the Julian day and the second was a time string. This was done to accommodate the
new import mechanism in GPSQL (see GPSQL topic).

3) Added an option on the Logging Parameters dialog to make a backup of the log
file. If this is enabled, a file in the GPSeismic folder is created called
GPNavBackupLogFile.csv. This file is appended to when logging in any mode. When
closing the program, the user is provided the current size of this file and asked
whether it should be deleted.

4) Added the ability to add a value to the depth value. This could compensate
for something like a transducer offset. The value is entered in the Depth Groupbox
of the Communications dialog.

Items 3 and 4 were requested by Andre Luttmann of DMT.

5) Fixed a problem in both GPNav and the freeware QNav which affected communications.
Specifically, the selection of stop bits from the drop list was being used
incorrectly in opening the port. For example, if you selected 1 stop bit, the port
was opened using 2 stop bits.

Thanks to Jan Quaak for spotting this.

QuikCon

1) Fixed a problem in the sunshot utility. If one or more of the sunshots were
on either side of 360, the average sunshot was incorrectly computed.

This was spotted by the very cool and savvy Jan Quaak of CggVeritas

2) In Control Station Manager, the last edit is now automatically saved when 
creating a QCC file. If you opened a QCC file (or saved one), the next time you
make an edit and save the existing data, you are asked whether to replace the last 
file opened. On the main QuikCon interface, the most recent file list would not 
place the last file opened as the one currently viewed. This has been fixed.

These modifications and fixes were requested by Cliff Wittig.

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