GPSeismic Version 2007.0 Release Notes General 1) Version 2007 includes a new application called GPNav. This application replaces GPTrack, but GPTrack will remain in the GPSeismic suite until the end of this year. GPNav features enhanced real time graphics for depicting height, depth, DOP, Sats, Pitch and Roll. It also features a steering indicator which can be configured in three ways(left/right steering, distance to go, and inline/cross line depictions). The graphical interface can be customized in many different ways to suit the job. GPNav supports SHP, CAD and registered images just like GPTrack. However, GPNav uses SHP files as the basis for tracking. Any SHP point can be the single current target. The user can click on the point he wants to be the target, specify the target by name or press a button to increment the target. When logging, the user can have the next target automatically be selected once the current target is logged. The user can also follow a script, which is a simple file containing the stations to be shot (in the order they appear in the file). GPNav has support for the following IO: Primary position - (NMEA $GPGGA format message) Secondary position - (NMEA $GPGGA format message or defined by offsets to primary) Heading - NMEA $HCHDM or $PTNHTM) Depth - (NMEA $DDBS) It also supports a port for outputting the vessel position (for example, if relaying the position). Logging can be on time, distance, zero inline to target, serial line event or automatically when certain criteria are met (within a specified distance to target, speed has dropped below a certain value, and a specified time has elapsed). In the zero inline mode, you can elect to raise a serial line in advance of the zero inline shot and raise a second line at the exact time of the shot. This could be used for applications such as shallow marine seismic. To this end, second order predictive filtering for position and/or velocity has been added. In summary, GPNav provides all the capabilities of GPTrack, but with enhanced graphics, targeting and the ability to support shallow marine surveying. 2) When modifying aliases using the query builder, if the aliases were part of a table join query, there would be a duplicate set of aliases. Bizarre but true. This has been fixed. This was spotted by power user Michael Schlautmann of DMT. 3) The Geodetic Settings dialog can now be launched from the QuikLaunch program, which is the tray area notification utility. The item will be enabled after launching any security protected application so if it doesn't seem to do anything, just start any GPSeismic application once. This was requested by Jan Quaak of CGGVeritas. 4) Several text fields in the Postplot table have been increased with regards to size. QuikView has been modified to populate this new structure or the older structure. This was requested by Glyn Barnes of WesternGeco. 5) In the image registration utility, the ability to define a region by coordinates has been added. Using this feature requires you have an image loaded, and you have either defined two (or more) registration points or have retrieved registration values. In the 'Region' menu you would select 'Define By Coordinates'. This displays a dialog in which you can define up to 100 points. Each point is defined by entering an easting and northing separated by a comma into a text box and then pressing the button with the '>' on it, an action which inserts it into a listbox. There are up/down and item removal buttons to assist in developing the list. You can save the list to a CSV file or you could retrieve a CSV file to populate the list. The final list must be in order, that is, moving from point to point in the list would define the sides of the polygon. Once you press 'Close/Define' on the dialog, the region will appear. This was requested by Darstaru Constantin of Prospectiuni SA. 6) You can now strip specific characters from any field in the modern spreadsheet. For example, suppose you were processing data in QuikView and found that the surveyors put an alpha character in front of each station. This utility could be used to strip it off. Look in the Edit menu for this utility and note that you don't have to press 'Save changes' after you have completed the operation. Added this as a result of a discussion with Dave Jones of Santos Geomatics. QuikLoad 1) A problem was fixed where deselecting the "Use UHF File" option did not automatically allow all points to be selected for uploading without reloading the QLD file. This was spotted by Alan Stanton of WesternGeco 2) An option was added for 'Project Height' for Trimble DC v10 files and later. This textbox entry is located on the same dialog that allows you to specify the TSC version. Prior to this option, a warning would appear on the TSC that said "A Project height is required". The user had to enter the Projection menu and enter an average height to get the job started. This was requested by Noel Mcloughney of WesternGeco. 3) When you create a UHF query from the Miscellaneous dialog, you can now choose any table in the project database as long as the first two fields are Station (text) and Station (value) respectively (previously, it was only the Postplot table). In addition to the Preplot and Postplot tables, all Import tables are created with this structure. 4) The Endpoint preplot tool accepts files in which each record has a station and coordinates for this point and ending coordinates for the opposite end of the line. This utility has been modified to accept line extensions. The user enters the number of additional stations desired at the ends of the line. The utility also can assign unique Descriptors for each line. If you elect to do this, you enter a value to increment by and for each line, the Descriptor will be the concatenation of what you placed in the Descriptor text box and the value (which increments for each line). In this manner, you could potentially create a number of 2D lines which have the same numbering, but still have a way of uniquely identifying each. This was requested by Brian Marsh. QuikMap 1) Viewshed analysis capabilities have been added. A viewshed is an area of land, water, and other environmental elements that is visible from a fixed vantage point. Within the survey industry, it can be significant when it comes to trying determine where conventional surveying can be conducted and where GPS surveying can be conducted when using a low power high frequency (line of sight) differential link. You compute a viewshed analysis by first selecting a tracking DEM from the DEM dialog. Once you have a tracking DEM, there must exist two points somewhere in the DEM area. At least one of these must be location that represents the fixed vantage point, that is, the point at which you want to determine everything that is visible. The location of the second point is not necessarily important if your goal is to create an image depicting all visible areas. It is important if your goal is to make a simple check between the two points to see if one is visible from the other. Once you are at this point, you perform an inverse between these two points. There will be a button on the inverse dialog that says 'LOS'. Press it and a subsequent dialog allow you to compute the viewshed by entering height above the DEM at the fixed point and all points you want to view. 2) The fundamental inline and crossline entries for Automatic Offset have changed. For regular incrementing offset test locations on both the positive and negative sides, simply enter the value as a positive number. To force the offsets to the positive side only, precede the value with a plus sign '+'. To force the offsets to the negative side only, precede the value with a minus sign '-'. To fix the offset to a specific value on the positive side precede the value with both an equal sign and a plus sign '=+'. To fix the offset to a specific value on the negative side precede the value with both an equal sign and a minus sign '=-'. To allow fixed test offset locations on both the positive and negative sides, precede the value with a plus sign, a minus sign, and an equal sign. 3) The Polygon capture delete operation allows choice of All, Primary, Hit, or Secondary points to delete. Previously, all points inside the polygon were deleted. Now, after the lasso operation, a dialog appears which allows you to make your choice. 4) A new item has been added to the Edit menu to perform an operation on the last selected polygon capture points. After you have performed your operation on a selection of points using the lasso technique, you can use this new Edit menu item to display the lasso menu which allows for the selection of the new operation on the previously selected points. This was requested by Alan Stanton of WesternGeco. 5) Fixed a bug in the LIDAR conversion routine when processing comma delimited data. This was spotted by Scott Van Metre of ConocoPhillips. 6) You can now toggle use of multiple GDF (grid definition) files. After you open your second GDF file, the next time you choose File-Open Grid Definition File you will be presented with a dialog listing the previous GDF files you have opened in this session of QuikMap. You can either select one (which will then be immediately opened) or choose the Select New button to choose a new file. There is also a new 'Open GDF' toolbutton.' This was requested by Lisa D'Ambrosia of Lockhart Geophysical. 7) During a polygon capture operation, a "rubber band" has been added from the polygon cursor to the last point, so you can see where your line will be before you click. This was requested by Lisa D'Ambrosia of Lockhart Geophysical. 8) On the DEM dialog, you will now see a new data conversion utility which will allow you to create an XYZ ASCII file for a specified DEM. This was requested by Michael Bonnici. 9) On the DEM dialog is a new utility which will allow you to mosaic multiple DEMs into one large DEM. This function can also resample a single DEM to new spacings. When selected you will notice X and Y grid spacing text boxes in which you specify the spacings for the new DEM. This was requested by several users. 10) Yet another feature on the DEM dialog is a button to display the DEM extents and spacings for a selected DEM. It is enabled once an input DEM is selected. 11) The Transform DEM feature has been completely re-written and will directly create a DEM in the target system without requiring the creation of an intermediate ASCII file for subsequent import. 12) When displaying a 'Tracking DEM', a new color mode called 'Atlas Colors' has been added. This supplements the 'User' and 'Ramp' color options. 13) Added a DEM <-> ESRI ASCII Raster conversion utility. GPArc now has a new ASCII conversion utility to convert this file to an ESRI format TIF DEM (or vice versa). Requested by Glyn Barnes of WesternGeco. QuikView 1) You can now display and edit Leica (or other supported) Attributes. Look for the 'Grid Display (Attributes)' in the View menu. This was requested by Glen Rideout of Wolf Survey and Mapping. 2) Support has been added for version 6 of the Topcon TopSurv databases. This includes the importing of DOPs, number of satellites, and user codes. TopSurv support remains backward compatible to versions 4 and 5 as well. 3) Added the ability to import Carlson RW5 GPS files. The steps involved are to first start QuikView and select Generic ASCII from the Utilities menu. On the resulting dialog, the very first thing you want to do is check a new item in the Preferences menu that indicates you are supporting Carlson. This setting is persistent. Now select 'Configure For SurvCE CSV Files' in the tools menu. It will configure the entire interface for subsequent imports of files minus the tweaks described below. One tweak is how to specify the mode of shots. Because these files have text and not numeric codes for the type of position, you must match the text to what is to be encountered in the file. QuikView will auto configure for 'AUTONOMOUS' and 'DGPS' but there might be other text for other modes. Another tweak is what units the HI's are in and if you want that subtracted from the recorded height. The final tweak is for you to indicate what units and sigma value the RMS values are in. Once all these tweaks are made, you can choose 'Convert/Import' SurvCE File' from the Tools menu to import a file. Remember that once the interface is configured, it is persistent so that the next time you use the utility, simply display the dialog and go right to this menu item. This was requested by Kevin Crozier of PGS Onshore. 4) Fixed bug where base station summary dialog when shown immediately after opening a DC file did not report the control QLD comparisons. This was spotted by Alan Stanton of WesternGeco. GPSQL 1) There is a new query item that allows the user to generate a seismic file of points relative to the points in the query. This utility uses a template file (TPL) as the definitions of the offset locations. You could use this utility to preplot vibe positions given the original source positions, or you could use it for any preplot (or postplot?) requirement where the desired points are relative to a set of 'origin' points. This utility is run by first selecting a desired query, then selecting 'Seismic Report (Vibes)' from the 'Query' menu. You will first be prompted for a TPL file. Once selected, a dialog will be shown that displays the defining offset parameters. There are checkboxes that allow you to select one, several or all offsets for creation. There are also text boxes that allow you to enter text that will suffix the point created. For example, if the point in the query has a name of 101501, then if you enter 'B', that offset point will have the name, '101501B'. Once you OK this dialog, you will be asked to specify a name for your new seismic file. Next, the field selection dialog will allow you to confirm the fields to be used. The next dialog allows you to confirm the coordinate system. This is an important dialog since it is required for converting the new grid coordinates to their geographic counterpart. The final dialog is the ASCII Export Specifications dialog which allows you to select what type of seismic file you want to create. This was requested by Kevin Crozier of PGS Onshore. 2) There is a new Utility menu item called 'Calendar Of Start Times'. This utility is hard coded to work with the entire database and produces a calendar of the first recorded position(s) of each day. The user is prompted only for a field which defines the ID of the pack operator. For example, if you used 'Collector Job Name' as the field, the utility will provide the first recorded time for each unique Collector Job Name. So for a given day in the calendar you might see something like: 08:40/Jim 09:20/Pete 07:20/Bill 06:01/Amy The first item is the first shot of the day and the last would be the Data Collector Job (or specified field). Its obvious here that Amy is on the ball and Pete needs a scolding. As stated, the utility is hard coded meaning it assumes some things. The first is that it is working with the entire POSTPLOT table. The second is that it is to use the Local Time field for dates and time. It also relies on the fact that the POSTPLOT table has an 'Elapsed Time' filed. This field is the difference between the time of the recorded position and the one previous. Only on the first field is this value zero. The utility also does not use any records where the Local Time field or the specified ID field is empty. While the calendar can be printed, it is not capable of providing a CSV or other report. This can be accomplished however by making your own query. Just remember that you are looking for all records where the 'Elapsed Time' is zero. This was requested by Tim Green of Destiny. 3) On the 'Add Field' dialog, you will now see a checkbox that will allow you to initialize the new field with unique values. This new field will not be an auto incrementing type. This was requested by Michael Perdue of Mercedes Surveys. 4) GPSQL now writes the setting to save toolbar changes to the registry. In this way, when changing projects in Project Manager, you may elect not to replace Shared Settings, thereby preserving the toolbar changes. This was requested by Eric Amedee of Pioneer Surveys. 5) Selected point annotations can now be made. When a query is selected and this item is selected from the Modifications menu, the Field dialog is displayed which prompts for two fields. The defaults are Station (value) and Descriptor. The options for selected points are also enabled. Once run, the Descriptor (or other selected field) is annotated with 'BOL' for the specified beginning of line points, 'EOL' for the selected ending of line points, and 'BOX' for all others. This request by Glyn Barnes of WesternGeco is so that specific points can be flagged in a GIS system for special labeling. 6) In the new Multiple Map utility, you can now specify a SHP file of connecting lines. There is the assumption that the query being pointed to is a Postplot query and that there exists a Preplot table in the database. This map layer will create a SHP file of lines that connect the Postplots to the Preplots. There is an option in the Preferences menu that allows you to select straight or elliptical lines. This was requested by Peter Hall of Katy Geophysical. 7) You can now select a field in the database structure spreadsheet and change its field length. This works with string fields only. If a field in the Postplot or Preplot tables is chosen you will receive a warning since altering any of the standard fields will prevent QuikView or QuikLoad from inserting any more data. A field the user has added could be changed however. 8) In the Excel Import utility, you can now specify string, integer, long, double, date/time and single field types. Previously, you could only specify string or numeric. This was requested by Michael Schlautmann of DMT. 9) You can now do a search and replace for all queries. This new feature is in the Define menu and prompts for search and replace strings. It also allows the range of query numbers to be specified (default is 1-99). It is a good tool if you have many queries that have a Julian Day specified and you want to change them in one step. This was requested by Donn Gaddis of PGS Onshore. 10) In the Duplicate Manager, some settings were made persistent, the number of unique sweeps was added to the summary, some mystery map numbers were eliminated and the line depicting a template line azimuth was tweaked ( if the form was not sized so as to make the map square, it would be skewed.) 11) Slightly rearranged Duplicate Manager statistical summary. Requested by Brian Marsh. QuikCon 1) Added import/processing capabilities for Topograph conventional files. These files have an extension of MED. A typical file of a setup is as follows: &E|A2 ||1530 ||||||| &R|A1 |RE |1500 |3503947|0873948|146948 |146826 ||| &N|A1 |REI |1500 |1704013|2722013|146948 |146826 ||| &I|LR001-137 |PASTO |1500 |2545329|1005335|207592 |203853 ||| &I|LR001-138 |PASTO |3500 |2434337|1005809|197671 |194061 ||| &V|A3 |VANTE |1500 |2545103|1005326|207484 |203748 ||| &M|A3 |VANTEI |1500 |0745115|2590640|207484 |203749 ||| A description of the records follow: &E - a new setup. The second pipe delimited item is the setup ID and the fourth item is the HI multiplied by 1000. &R - back sight face 1; The second item is the back sight ID, the fourth the HR multiplied by 1000, the fifth, sixth and seventh are the horizontal angle, zenith angle and slope distance respectively. &N - back sight face 2; format as above &I -sideshot(s); format as above &V - fore sight face 1; format as above &M - fore sight face 2; format as above Other notes - The eighth delimited item is a 2d distance and is unused. The third delimited item is placed in the Code field. The distances are multiplied by 10000. This was requested by Brian Davies of Grant Geophysical. GPLocator 1) GPLocator now supports Fleet Management Solutions (FMS) web requested data. FMS provides equipment that consists of a GPS receiver and an Iridium phone that sends a vehicle's position back to the FMS web site. After entering your password and specifying the numbers that represent the unique identifiers for your vehicles, GPLocator will continually request all current positions for mapping and/or logging purposes. This was requested by Kevin Crozier of PGS Onshore. 2) Streamlined user interface by placing all data input types on the Communications tab page. This now includes Serial Comms Data, UDP packets and web requested data from the Fleet Management Solutions. 3) Corrected some problems with the portable backup mechanism. Specifically, image registration files were not being included in the backups. 4) GPTracker files are now handled by converting one or more into an LGM log file. Previously, you handled these flat ASCII files as a serial input in order to create a log file. What the heck was I thinking? GPArc 1) In the new Multiple Map utility, you can now specify a SHP file of connecting lines. There is the assumption that the query being pointed to is a Postplot query and that there exists a Preplot table in the database. This map layer will create a SHP file of lines that connect the Postplots to the Preplots. There is an option in the Preferences menu that allows you to select straight or elliptical lines. This was requested by Peter Hall of Katy Geophysical. 2) In the edit mode, its possible to select a number of polygons by dragging a box around them. Then its possible to hold down the left mouse button and drag them where you want (Its also possible to select polygons by holding down the Shift key and clicking on each desired polygon.). However, there is no rotation of polygons in the edit mode. Therefore, in the Utility menu, a new item was added that allows you to rotate a SHP file (polygons, lines or point type). When selected, you must first enter the coordinates for the point of rotation and the rotation angle. This is done in one input box. You enter the information as three comma delimited items. So if the point of rotation is 500000,2000000 and the rotation is 10 degrees, you would enter '500000,2000000,10' (without the single quotes). You are then prompted for the input SHP file and the new rotated SHP file. Note that if you have a layer open, the input box will have a default set of coordinates that represent the center of the current view. 3) Added a TIF DEM <-> ASCII conversion utility. Apparently, ESRI has some strange TIFF format that they utilize much like a DEM in which each cell of the image can hold elevation information. QuikMap now has a new DEM conversion utility to convert the a DEM to the ESRI format ASCII and vice versa. Requested by Glyn Barnes of WesternGeco.
2008.2
|
2008.1
|
2008.0
|
2007.4
|
2007.3
|
2007.2
|
2007.1
|
2007.0
GPSeismicŪ is a registered trademark of Dynamic Survey Solutions, Inc. See the
sitemap
for a comprehensive listing of all site pages and links.
