GPSeismic Version 2007.3 Release Notes General 1) Both GPMap and GPTrack have been modified to show a deprecation notice. This notice indicates that these two applications will not be part of GPSeismic Version 2008 when it is released next year. GPArc, which is based on ArcObject libraries, will be the sole presentation mapping application and GPNav will be the sole single-vehicle navigation application. If you currently use GPMap or GPTrack, you are encouraged to make the transition to the newer applications as soon as possible. Similarly, a deprecation notice has been added to the Multiple Map (classic) utiity. You need to transition to the 'modern' Multiple Map utility which has more capabilities including the ability to use tables other than Postplot and Preplot. 2) The Multiple Map utility can now write DXF files without blocks. This is a preference in the Preferences menu. If you elect to do this, note file creations takes a very very long time. 3) The automatic grid definition builder could hang up on some brick patterns. This has been corrected. 4) The township utility has been re-written. This was done in an effort to migrate the utility to a newer programming language and also streamline the user interface. So that users can test the new utility, an option in the Project Manager Utilities menu that says, 'Use 2008 Township Utility' can be checked or unchecked to toggle between the use of the old and the new. Note that the new utility uses the new geodetic transformation library so you must have installed that (and added any desired coordinate system and datum transformation). If you encounter any problems or require additional capabilities, please let us know as soon as possible. The old utility will be dropped for the GPSeismic Version 2008 Release next year. 5) The number of user defined formats in both the ASCII Import and ASCII Export dialogs has been increased from 10 to 20. This was requested by Brian Marsh. 6) A number of DXF related loading and rendering issues have been fixed in QuikMap, QuikView, and QuikLoad. QuikMap 1) When performing a two-layer proximity test, after you have selected that item from the File menu, a dialog will be displayed which prompts for minimum separation and a new option that allows you to limit the proximity points to the single nearest point. With this option a DXF layer of connecting arcs is drawn between the initial point and the nearest secondary point. This was requested by Brian Marsh. 2) When choosing the Grid/Title Block option when zoomed in, you will have the choice of configuring the subsequent dialog for the current or full extents. This was requested by Brian Marsh. 3) When pressing the Delete key, you will be prompted to delete all Hit points that might exist. This was requested by Scott Van Metre of ConocoPhillips. 4) In addition to the initial layer and grid definition file names, the title bar nows displays the secondary layer and top-most image file names. This was requested by Scott Van Metre of ConocoPhillips. 5) All proximity spreadsheets now display the point offsets in terms of delta inline and delta crossline along with delta easting and delta northing. This was requested by Rick Irving of Geokinetics. 6) QLD files can now be created via the polygon capture mechanism. 7) A miscellaneous option has been added to confirm the currently selected transformation parameters against the project parameter file. Items 6 and 7 were suggested by WesternGeco surveyors after a recent GPSeismic course. QuikView 1) A code substitution feature has been added to replace short codes in either the descriptor or comment with longer codes found in a specified table in the project database. To implement this, you would first add a table in the project database that would contain two fields. The fields can be called whatever you want but they should be arranged so that the name to be searched for is the first field and the second field represents what you want substituted. The field types can both be string types. In QuikView, on the Processing Settings tab page of the Miscellaneous Settings dialog, there is a checkbox labeled 'Code Substitution' which must be checked. There are two options that allow you to specify Descriptor or Comment for substitution, and a button that allows you to specify the table in the project database to use. As long as this item is checked, QuikView will attempt to make the substitutions each time a download file is opened and will inform you of the number of substitutions made. This was requested by Gustavo Rincon. 2) Protection for Leica files that have points time tagged for the distant future has been added. QuikLoad 1) A utility has been added to create a GPS Exchange GPX file. There apparently are some Garmins which have data cartridges that can be uploaded with these GPX files but using MapSource only. There are some Magellans that also take these type of files but have card readers that function as logical drives so you should be able to copy the GPX files to them directly. This was requested by Jan Quaak of CGGVeritas. GPSQL 1) The latest version of Google Earth supports the depiction of many points fairly well (e. g., no problem with 50K points and cable modem speeds). With this in mind, the point number restrictions were removed from the Google Earth points utility. The Google Earth utility has been changed to a 'place mark' technique which allows you to click on the point to reveal its station number and up to two optional pieces of information (selected on the field selection dialog and defaulting to Descriptor and Comment). Interestingly, this method allows a 'clamp to ground' mode which depicts the point intelligently in a height sense so it works well in mountainous areas when viewing from non-overhead angles. On the Miscellaneous Options dialog, you will see several new options including: Symbol Type (there are six possibilities) Symbol Scale - symbols are depicted in points so you will have to experiment with this to see what meets your needs. Include Labels Option Initial View Angle and Initial View Altitude Selections Line Width (when viewing lines) The enhancement were requested by Lisa D'Ambrosia of Lockhart Geophysical. 2) Added the ability to apply an HI to imported Pelton or Sercel vibe data. Changed Sercel field names "Aquisition Nb" and "Vibrator id" to "Sweep" and "Vibe ID" respectively so as to make it consistent with Pelton. If you have an existing table of Sercel data, after updating to Version 2007.3, you should manually change the names of the fields. This was requested by Brian Marsh. 3) The Multiple Map utility can now write DXF files without blocks. This is a preference in the Preferences menu. If you elect to do this, note file creations takes a very, very long time. There is also a preference to initialize with the last opened database in GPSQL. This was requested by Rob Irwin of Bearpaw surveys. 4) There was a problem in height interpolation in the 'Interpolate All' utility that would manifest itself if you attempted to interpolate many consecutive stations. This has been fixed. This was spotted by John Spreen of Paladin Positioning. 5) Added the Julian Day for averaged tables. Should the user not specify the GPS Serial time at the time of field selection, GPSQL will default to inserting the current JD for each record. Should you have a averaged table you have already created with a pre-2007.3 version, and you want to append to it, you will have to add a field to your existing table that is a long. It can be named whatever you want, but 'Julian Day' would bbe a good choice. This was requested by Brian Marsh. 6) Added a SHP line option on the field selection dialog that says 'write one line for each proximity hit'. When this option is selected, a second dialog appears which allows you to specify a proximity maximum and minimum. If the distance between two points is within these values, they become a candidate pair for creating a line. There are also two angles you can specify and a tolerance for each. For example, you could specify 45 degrees and a 5 degree tolerance. No lines will be created between any two points where the direction between the two were within 5 degrees of 45 degrees (or its compliment of 225 degrees). Finally, there is an option to limit any point to two connecting lines. The purpose of this line creation utility is an attempt at trying to make SHP line files for features such as roads or fences when those features were not surveyed continuously. For example, if during a project, your surveyors recorded fence or road positions each time they encountered one as they staked out normal production shots, you could write a query to isolate just the fence or road shots and use this utility to create a SHP line file. While its not a complete solution to the problem, it could jump start the process of 'connecting the dots' for you. Requested by Justin Brown of Maverick Surveys 7) Added an option to warn the user (during field selection) if he/she has not turned on the option to allow QuikMap to edit the database. 8) The 'Fill Postplot Fields' utility now works with any table that has the same twenty five key fields as the Postplot table. Those key fields are the ones that are listed in gray on the 'Fill Postplot Fields' dialog. Items 7 and 8 were suggested by WesternGeco surveyors after a recent GPSeismic course. GPArc 1) IMPORTANT - GPArc Version 2007.3 has been compiled using ArcGis Engine Version 9.2 Service Pack 2. If you are not using this Service Pack, you might experience errors, especially at program exit. Current ArcGis Engine 9.2 users can download the Service Pack 2 update on the following ESRI web page: http://support.esri.com/index.cfm?fa=downloads.patchesServicePacks.viewPatch&PID=17&MetaID=1270 Make sure and get the 'ArcGISEngine92sp2.msp' file and install. It's about 68MB. 2) Added splitters at the right and below the map so it could be adjusted to a size which might be better suited for printing. 3) On the page layout control, four load options were added. The default is 'exact' which produces an output of exactly what you see on the map and fills the page extents from left to right. The second is 'fill' which was how GPArc was always loading the map. In this mode, GPArc tries to fill the page layout control to eliminate whitespace. The third option is square. This was put in just in case you have a square page layout defined and wanted it completely filled. The fourth option is 'exact to scale'. In this mode, you specify a load scale before loading the page and what you get is an exact copy of the map display but at the specified scale. 4) Added a user defined grid overlay (in decimal inches) to the page layout control that you can use to snap the selected image to. You can turn snapping off if you want. Also if you loaded an image and have not set the scale explicitly, then when you resize using the handles, every time you release the mouse button, a small text box will show you the current scale as a result of the resizing. Remember that once you set the scale explicitly, resizing does NOT change the scale. You just see more or less image at the same scale. 5) When you move a layer up, down, to bottom, to top, or swap layers, the selected row of the layers list now follows suit. 6) Added the ability to specify three default paths rather than one. You can now specify a path to GPA map files, layer files (Shp, Cad and image), and style files. 7) When you save a 'style' and the layer incorporated assigned colors based on strings in the underlying database, these colors were being lost. This has been fixed. 8) Added a 'quick line style' item to the Layers menu. When selected, it allows the user to quickly configure the line layer for one of sixteen predefined types. The line style could be tweaked with the normal renderer if required. All items above were requested or noted by Justin Brown. 9) Added a 'Find' toolbutton to the Map. Pressing this will display a Find dialog with extensive capabilities. You will need to read the help file closely to determine all of the capabilities. 10) Added the ability to add yellow halo to text you place on the map. Requested by someone from Exterra Surveys whose name I can't recall. 11) You can now save all layer styles in one step. Look for the 'Save All Styles' item on the Layers menu. The styles are saved in the designated styles folder. This was requested by Peter Hall of Katy Geophysical. QuikCon 1) If you shoot one or more TI points and you know the foresight azimuths for these shots, its now possible to use this information to fix backsight azimuths during processing. You must place the known azimuth to the TI point in the Comment column of the TI record in the DCO editor (Face 1 if there are 2 faces). The entry must be in the form of 'TI=DDD.MMSS'. For example, if the foresight azimuth to the TI point is 90 degrees 12 minutes, 11 seconds, the entry would be: TI=090.1211 When processing the QCN file, you must elect to fix backsight azimuths and you must have specified a QCC file (even if you are not using any stations in it). The difference between the computed azimuth to the TI and the known azimuth to the TI will be applied to the backsight azimuth of the next setup in the traverse. For all essential purposes, the appearance in the spreadsheet will be exactly like a fixed backsight azimuth and the difference can be prorated if required. This was requested by Oscar Calderon. 2) There is a new DCO editor Import menu item called 'Topcon (Goh)'. It will import a file as below: STN 1,1.537,STN BKB 2,0.00000,0.00000 BS 2,1.535 HV 0.00000,89.44550 BS 2,1.535 SD 179.59500,270.15300,5.1170 FS 3,1.900,STN SD 144.00050,276.13000,4.3020 FS 3,1.900,STN SD 323.59500,83.47200,4.3030 SS 4,1.600,TREE,1 SD 25.47550,90.07350,5.3250 Here is a description of the records as relayed to me in an email: STN - Used to indicate a new setup. The first of the three comma delimited items are the setup ID. The second is the HI. BKB - Used to indicate back sight ID (first delimited item) and bearing to the back sight (second comma delimited item). BS - The second comma delimited item is the HR of the back sight HV - The first and second delimited items are the horizontal angle and zenith angle of the back sight face 1 BS - Seems redundant but again, the second comma delimited item is the HR of the back sight SD - The first and second delimited items are the horizontal angle and zenith angle, and the third is the slope distance. These items are for back sight face 2 FS - The first delimited item is the fore sight ID, the second is the HR, and the third is the code. SD - The first delimited item is the horizontal angle, the second is the zenith angle and the third the slope distance of the fore sight face 1 FS - The first item is the foresight ID, the second is the HR and the third is the code SD - The first delimited item is the horizontal angle, the second is the zenith angle and the third the slope distance of the fore sight face 1 SS - The first item is the sideshot ID, the second is the HR and the third is the code. I have no idea what the fourth item is. SD - The first delimited item is the horizontal angle, the second is the zenith angle and the third the slope distance of the sideshot Notes - There doesn't appear to be a back sight slope distance for face 1 so it would appear reciprocal data can't be reliably computed.
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.
