GPSEISMIC FAQS Simply put, what is GPSeismic and what can it do for me? GPSeismic is a suite of Windows software that allows you to process and manage GPS, Inertial and Conventional data. There are five main applications: QuikLoad - generate preplots and uploads to any of twenty-five GPS, INS and conventional systems. QuikView - processes survey data from any of forty-five GPS and INS systems. QuikCon - processes raw conventional data in any of thirty-five formats. GPSQL - sophisticated data management tool for all preplot and processed survey data. QuikMap - a key problem solving application which provides the user capabilities which range from simple preplot redesign to fold analysis. Four other applications are provided for specialized needs. These include vehicle tracking, fleet tracking, presentation mapping and project management. -------------------------------------------------------------------------- What other software do I need to use GPSeismic? No extra software is needed with the following two exceptions: 1) If you are a Trimble user, you probably will need their Data Transfer program. It is required to convert a Trimble data collector file to a binary format that the Trimble data collector can read. Its a free utility that you can get from their site. 2) If you need a mapping application, GPSeismic includes a program called GPArc which requires that you purchase a set of libraries from ESRI called ArcGis Engine. If you already have a favorite mapping application or you require simple mapping requirements, you won't need these ESRI libraries. Note: Potential clients often ask us if Microsoft Access is required and the answer in No. All required database access libraries are installed when you install GPSeismic. -------------------------------------------------------------------------- What are the network capabilities of GPSeismic security keys? The security keys we now use are network compatible. This means that a user is not required to have the security attached to his computer and can access a key (license) across a local network and even via terminal services. Please note however that each security key tracks its use and ensures that only one user can access it at a time. So, multiple users can access the same security key and the only restriction is that one user must finish using GPSeismic with the key before another will be granted access to it. Each key has a hard limit of one license; however, we do have clients with multiple licenses (keys) who place all of their keys on a single server. Their office staff with local IPs and remote staff via terminal services regularly access licenses (as long as one is available) from the server. License restrictions are as follows: 1) For local users where the key is connected directly to the workstation or where the key is accessed from a server via a local area network, each license (key) allows multiple instances of any combination of the GPSeismic applications for the same user. Regardless of which applications are running, this user would consume one license. 2) For remote users via terminal services, a single instance of any GPSeismic application will consume one license (key). Note that GPSeismic does not need to be installed on the server. The software that must be installed on the server is the security key driver and server software. This installer is available as a single executable which can be downloaded from our site via: http://www.gpseismic.com/download/security/Sentinel_Keys_Protection_Installer.exe Download and run the sole file in this folder (Sentinel_Keys_Protection_ Installer.exe) on the server. Once this is complete, you can then attach as many GPSeismic USB security keys to the server as you like. Then on each workstation which has GPSeismic installed, you will need to modify a small XML file in the GPSeismic installation folder (typically C:\Program Files\GPSeismic) called sntlconfig.xml. In this file, between the ContactServer tags you will need to replace localhost with the local IP address of your server. This will tell that installation of GPSeismic to look for a key (license) on the system with the entered IP address. -------------------------------------------------------------------------- Several programs will not run. I know the security drivers are installed. 2000 and XP is like Windows NT in that you log on with administrator privileges or as a user. If you log on as administrator and install the software,'you will experience no problems each subsequent time you log on as administrator. If logging on as a user on the same system, several programs will refuse to work. This is because these programs will look in the system's registry (you can think of this as a repository of system operating parameters) for the directory where GPSeismic is installed. This information, called the current user key, will be present when logged on as administrator but will have to be written to the correct registry key appropriate for the logged on user. There is a program in the GPSeismic folder called GPSeismicShortcutManager.exe. Its actually there so you can customize what you want to see on the desktop, etc. However, one thing that it does upon startup is to write the installation path to the current user key. So if you are experiencing the problems described here, log on normally as whatever user you are, then start this program and then exit. The application path will be written to the current user key and everything should then function normally. -------------------------------------------------------------------------- Some menus are missing and disabled. What do i do? If tool buttons or menu items go missing, you could find the menu or miscellaneous setting that preserves your tool bar settings and turn this off. Re-starting the program should fix it. However, if the situation is so bad, you can't do this, you can simply delete the file that saves these changes. Each applications creates and subsequently uses its own configuration files. If you need to, you can delete these files manually through Explorer, but make sure you delete the right ones. Here are the applications and the file(s) you should delete: GPSQL - gpsql_mnu.xml and gpsql_dock.xml QuikCon - quikcon_mnu.xml and quikcon_main_mnu.xml GPArc - gparcnet_mnu.xml Caution - If you definitely must delete the files for the applications below, note first that these INI files are located in the Windows folder. Note also that these files contain all settings for the respective application. You might want to consider emailing or calling us for assistance. QuikLoad - quikload.ini QuikView - quikview.ini QuikMap - quikmap.ini -------------------------------------------------------------------------- Can GPSeismic be installed on a Mac? Unfortunately the answer is not simple. We have a client that installed and tested GPSeismic version 2008 on his MacBook Pro. He has VMWare Fusion installed on the Mac with Windows XP Professional running under this as a virtual machine. His tests indicated that routines would run albeit slower. However, we have not had anyone run any extensive tests which span all applications so we advise against using a Mac for now.

QUIKLOAD FAQS What is QuikLoad what does it do? QuikLoad has preplot capabilities and is the application for selecting and uploading stakeout points to any of twenty five devices. This includes GPS, INS and conventional systems. Selecting your stakeout points is graphical and can be done against a selection of image or vector backgrounds. The preplot capabilities include any design you might encounter including simple 3D, zig zag and brick. ------------------------------------------------------------------------ I use Trimble. My upload tool button and 2D tool button are both disabled. What should I do? To enable the upload tool button, you need to install Trimble's Data Transfer program. Its a free utility that you can get from this link: http://www.trimble.com/datatransfer.shtml In order to enable the 2-D button, you will need to enter zero for the number of Bin Digits in the status bar panel. ------------------------------------------------------------------------ I am selecting USB to connect to my Garmin, but it doesn't work. The most common problem here is that you have not installed the Garmin USB drivers that came with your unit.

QUIKVIEW FAQS What does QuikView do? QuikView downloads surveyed data from any of forty-five systems, transforms the data to a desired coordinate system and if required, converts ellipsoid heights to orthometric heights using a selected geoid model. Preplot and surveyed coordinates are displayed on a user selection of image or vector backgrounds. ------------------------------------------------------------------------ How can I compute offset information in QuikView for surveyed points that had no corresponding uploaded preplots? You would select the corresponding preplot QLD file in the QuikView/ Preferences menu. When you import the download file, QuikView will compute and display the comparisons using the QLD file as if the preplots were uploaded. Also, you can now specify a source and receiver grid definition file on the Offsets dialog of QuikView. When a point has no preplot, the Changes dialog will display a Compute Preplot button for it. ------------------------------------------------------------------------ How does QuikView handle Glonass? The requirement for a new GPS/GLONASS survey mode first came up with Leica System 1200 in 2006. At that time, our directive was to add a new survey mode to indicate that both GPS and GLONASS satellites were used in the solution. So, early in the v2006 release period this new mode was created. If QuikView sensed a hybrid solution, the mode became GPS/GLONASS. Months later, some of our clients who were using this indicated that if the solution is of the Phase type, then it should be reported as such. We then pursued what the actual nature of a combined solution was and learned the following from a Leica technical representative with the understanding that Trimble and Topcon do the same: GLONASS satellites are used to assist in determining the integer ambiguities of the GPS L1 phase observations and in the monitoring processes. The determination of integer ambiguities for GLONASS satellites is not pursued. Therefore, a fixed integer solution where Glonass satellites are also tracked is actually a GPS L1 fixed integer solution. So, with our release of GPSeismic in October of 2006, the reporting was changed so that the survey mode will be GPS/GLONASS if 1) The solution type is NOT phase and 2) Glonass satellites were used in the solution. ------------------------------------------------------------------------ I manually added a field to the Postplot table using Access. I placed it at position 5 instead of having GPSQL add it on the end of the table. QuikView cannot now populate the Postplot table anymore so I removed the column and all is well again. However, is it possible to move fields around and still have QuikView recognize them no matter what ordinal position they might occupy? QuikView and QuikLoad bind to the databases based upon the ordinal positions of the fields in a table. That is, they require that the first so many fields of each table have pre-determined types and widths. If this check fails, you will see an error. You may add as many fields as you like at the end of each table for this is beyond the validation zone, but you cannot insert fields in the middle. The alternative to ordinal binding is name binding, however it is much slower, inefficient, and more restrictive than ordinal binding. ------------------------------------------------------------------------ Should I be using the Alternate Datum in the Miscellaneous dialog? In general, no. QuikView assumes that the data is to be transformed from the WGS84 datum. This Miscellaneous dialog item allows the user to specify a second datum transformation. This allows the user to 'cascade' datum transformations as might be required for use of a state HARN system. The button to the left of the checkbox is used to evoke the dialog from which the user can select the second transformation method. The US has a number of local high accuracy reference networks. The only way to convert from HARN to local datum is through a two step datum transformation process (HARN to WGS84 then WGS84 to local). This said, most datum transformations are a one step process so there should rarely if ever be a need for this. In fact, under project manager settings, we alert you about it when you display project settings in Project Manager by inserting a red colored warning. ------------------------------------------------------------------------ I've finally created the masks I want to use in QuikView. Why isn't there a quick way to switch from one to the other There is. Click on the small Mask item in the status bar. and you will get a popup menu of all masks. you can rapidly switch from one to another here. ------------------------------------------------------------------------ What is the significance of the information given when a transformation of raw data is completed and the screen comes up with: The RMS of the difference between the radial geographic and grid offsets is 0.00 meters. Preplot versus postplot transformations seem to be consistent. QLD files contain the coordinates of each point in WGS84 lat/lon and local grid. Most all data collector files record the coordinates of each surveyed point in WGS84. So that QuikView can compute and display offsets immediately after opening a data collector file, offsets are initially computed on the WGS84 ellipsoid using the surveyed coordinates and the WGS84 coordinates from the preplot QLD file. Once the transformation is performed, QuikView then has the local grid coordinates of each surveyed point. Since QLD files are typically created in QuikLoad by importing local coordinates and then transforming them to WGS84, recomputing the offsets in QuikView using the local grid coordinates of both the surveyed and the preplot Qld data provides an opportunity to test the consistency of the preplot and postplot transformations. If any aspect of the datum or projection parameters is different, then offsets computed on the WGS84 ellipsoid will differ from offsets computed on the local grid. So, once the transformation is complete, for each point QuikView will compute the difference between the radial offset on the WGS84 ellipsoid versus the radial offset on the local grid. The RMS of these differences is then determined. If it is less than one meter, a message indicating that the preplot and postplot transformations appear to be consistent. If not, a warning message is issued.

QUIKMAP FAQS What is QuikMap? Do I need it? According to statistics on application usage we keep, QuikMap is the most used application. So the answer is to whether you need it is Yes. Just a partial list of what QuikMap does includes preplot/postplot comparison, Digital Elevation creation and use, Fold Analysis, preplot re-design, exclusion area functions, proximity tests, spread analysis, and binning. -------------------------------------------------------------------------- Where do I get the SPS X file used in fold analysis. At this point in time, you can only make simple X files with GPSQL. When you use the utility in GPSQL, you are prompted for two queries. The first should be the sources, the second, receivers. GPSQL will write records that will consist of a source followed by the start and end station of a track. There will be one record for each track. So if you had 1000 sources and 20 discernable tracks, the X file would have 20,000 records. You may see the ability to write X files with greater complexity in future versions, but for now, it is normally expected that this file comes from the design Geophysicist using a tool like Omni or Mesa to create it. The Fold Analysis utility does have options for converting an I-O System 2 ASCII Script file (binary or ASCII), or an ARAM script file (*.PRJ) to a SPS X-File'). -------------------------------------------------------------------------- My points are not being rebinned yet I know they should be. If you import points into QuikMap, then open a grid definition file, you have the option of rebinning which is the action of renaming all stations based on where they fall in the theoretical grid. If you find that no stations are rebinned, yet you know they should be, this means the change in numbers is so great, that QuikMap believes they might be receiver points and not source points. Go to the Miscellaneous Settings dialog. Go to the Program Settings tab page. The top text box (Maximum offset for binning logic) should be changed to a much larger number. Then try rebinning again. -------------------------------------------------------------------------- Can I find and remove duplicates in QuikMap. There is a way to remove duplicate points in QuikMap by sorting the data and finding out where the difference in consecutive station values is zero: 1) Open your file SP1 file containing duplicates on the initial layer. 2) Choose File-Sort. 3) Choose File-Outputs and press the 'Interval Report' button in the Outputs dialog 4) In the spreadsheet choose Query-Build New Query, and build a query where the criteria is '[INTERVALS].`Change` = 0'. Then display that query via the first toolbar button. 5) Choose File-Turn Current Query Records Hit. 6) Once the spreadsheet closes and you are viewing the map, press the 'delete' key to be prompted to delete the Hit points (your duplicates). -------------------------------------------------------------------------- Can I determine all points falling in a polygon shape file? If you have a file of coordinates and a polygon Shp file, you can isolate the points inside the polygons in the following manner: Import your preplots into QuikMap. Then go to the image menu and load the SHP file. Go back to the Image menu and select layers. Right click on the SHP layer and create an XZO form the SHP. Import the XZO using 'Begin Batch Search' from the Search menu. The points inside will turn red. Go to Outputs in file menu and save the red points. -------------------------------------------------------------------------- How do I make a intervals check? Don't be confused and use the Proximity utility for finding large intervals along a line. Do the following. 1) Input your file, or in GPSQL, select your query and send this query to QuikMap 2) Select 'Sort' from the File menu. 3) Select 'Outputs' from the File menu and press the 'Report' button 4) Here you will have a spreadsheet of the distance intervals between points. You could query out those that are greater than a certain value. -------------------------------------------------------------------------- I need to create additional preplots for a large area adjacent to the initial prospect. I have a grid definition file. What do I do? An addback utility in QuikMap allows the user to create points in a user defined polygon. You would import your prospect into QuikMap and then a grid definition file for the same. You can optionally import an image if you need one to help define where the additional prospect is to be created. Note that since the grid definition file dictates where additional points are to be created, this can be any type of grid, including odd/even (Canadian) grids. You now lasso the area, right click and elect to create addback points on the popup menu. Doubleclick and like magic, you are done.

GPSQL FAQS What is GPSQL? Do I need it? All processed data whether it is GPS, Conventional or Inertial is placed in a database and GPSQL allows you to open the database and create reports, seismic files, map files, and much more. Its the core application for all of your data management requirements and believe us when we say that when you are dealing with what could potentially be tens of thousands of survey locations, data management is key. GPSQL has many built in functions that are tailored for the seismic industry. -------------------------------------------------------------------------- A message has appeared that says the database can't be modified! It also says something about primary key! What up? Despite what exact message you might see says, if you find that you can't modify the database using the modern spreadsheet viewer, the first thing you want to try is this: Select 'Compact/repair Database' from the File menu of GPSQL. Select the database and choose Access 2000 compatible. The problem should disappear. -------------------------------------------------------------------------- I was given a CD with a database on it. Why can't I open it? This could mean the database is write protected or the database is currently opened exclusively by another application. GPSQL uses 'False' for the read-only argument when opening an mdb (because we might eventually write to it), so you cannot open a database which has it's read-only attribute set. For an mdb on a CD, you will have to copy it to your hard drive and change that attribute. -------------------------------------------------------------------------- How do I use swath definitions? In GPSQL, you may import a set of swath definitions as a table (or append an existing one). The imported file must be in the form of a comma delimited file and have the following field sequence: Swath, HiTrack1, LoTrack1, HiBin1, LoBin1... The user is first prompted for number of swath definitions and the typical entry is '1'. which would produce a five field table as above. '2' would produce four additional fields describing more high and low track bin values. For example: Swath, HiTrack1, LoTrack1, HiBin1, LoBin1, HiTrack2, LoTrack2, HiBin2, LoBin2 The most common is one set of low/high definitions per swath, but if not, and the swath is not contiguous, you can specify the additional parameters up to 10. Below is a typical file which would be imported: 1,0,5000,1000,2000 2,0,5000,2000,3000 3,0,5000,3000,4000 4,0,5000,4000,5000 5,0,5000,5000,6000 6,0,5000,6000,7000 7,0,5000,7000,8000 8,0,5000,8000,9000 9,0,5000,9000,10000 Above, there are 9 swaths identified by the numbers 1-9. The first swath is defined by a low track of zero, a high track of 5000, a low bin of 1000 and a high bin of 2000. The remaining swaths are identified similarly. Once imported, a table is created. If the above data was imported, you would have five fields and nine records. The field names are called Swath LoTrack1 HoTrack1 LoBin1 and HiBin1. The query builder is designed so that it is possible to drag and drop table fields into the specified value textbox. This allows 'BETWEEN' statements to be constructed based on multiple table fields. For example, if two tables are selected and called SWATHS and POSTPLOT, you could build a criteria like: Select [POSTPLOT].*,[Swaths].* From [POSTPLOT],[Swaths] Where [POSTPLOT].`Track` Between [Swaths].`LoTrack1` And [Swaths].`HiTrack1` And [POSTPLOT].`Bin` Between [Swaths].`LoBin1` And [Swaths].`HiBin1` When you build such a query, you are cautioned to add a join to the table, but you don't have to here. Trust me! Finally, when you display (or report) this query, you will see that the Swath field will identify each station's unique swath number. -------------------------------------------------------------------------- I had to recalculate geoid heights..now what? If you have had to recalculate geoid heights in GPSQL for some reason and now need to correct the local heights, do the following: The fundamental height equation is: WGS84 Height = Local Height + Geoid Height or conversely Local Height = WGS 84 Height - Geoid Height So, since your WGS84 heights are ok and now your Geoid Heights are good, you would select a query in GPSQL that isolates all records you want to update and make the [Postplot]`Local Height` field equivalent to the following expression: [POSTPLOT].`WGS84 Height` - [POSTPLOT].`Geoid Height`') -------------------------------------------------------------------------- Can the accuracy of my heights be improved with a barometer? With regard to processing data and the use of barometers in height aiding, I would like to say I'm an expert in this but I'm not. But I would like to state what I have discovered. I have looked at the specs of a couple of barometers and what seems to be the accuracy for these systems. The better instruments range around 0.15 to 0.20 hPA (which stands for hecto-Pascals and is also known as millibars). There's about 1 hPa change in pressure for every 10 meters change in elevation. What I would therefore like to see in a system is an accuracy of about one or two tenths of that which is 0.10 to 0.20 hPa. So to me a system with these kinds of specs sure seems accurate enough to help in processing. Now, the way GPSQL works is you isolate by means of a query each separate GPS traverse. Once the barometric utility dialog is displayed, you select the pressure field and Local Height field. The utility looks for RTK phase shots to use as a 'calibration'. The best scenario that could happen is that each separate traverse starts with a phase shot, ends with one, and has some scattered through the middle of it. Since the phase shots act as a calibration, any system calibration error is removed, so I think you would end up computing heights with accuracies of about 1-1.5 meters and perhaps better if the operator did a good job taking phase shots when they could. -------------------------------------------------------------------------- How can I look for duplicates in the database? There is a report in the Report Builder that determines all duplicates based on a user defined key. A feature is included in the spreadsheet display in which sorting by any field allows the user to launch a small dialog that lists all duplicates based on the sort key. A GOTO button allows the user to quickly move to any duplicate. A 'Duplicates Manager' utility in the Modifications menu graphically depicts all duplicates for the currently selected query. The 'Purge Duplicates' utility in the Modifications menu allows the user to find duplicates based on the exact same thing being in three selected fields. This utility is typically used for finding shots that are exact matches (for example, when a data collector file is accidentally loaded twice.) Note that to find skips, the best way is to select two queries and send to separate layers of QuikMap. Once done the Compare item in the File menu is used.' -------------------------------------------------------------------------- How can I include a statement in my query in which I look for records where there is nothing in a particular field? Use the Miscellaneous helper on the Query Building dialog to assist you in entering the correct syntax. It will end up being something like: 'MyField' not like *' -------------------------------------------------------------------------- I want to write a query that find Descriptors with the letters 'A, C and D' and those Descriptors that have nothing. But there are 20 different descriptors and its getting really long and complicated. You can accomplish what you want with the following: Select [POSTPLOT].* From [POSTPLOT] Where ([POSTPLOT].`Descriptor` In ('A','C','D') Or [POSTPLOT].`Descriptor` Not Like '*') The string helper on the query building dialog can help you by automatically constructing the 'In' criteria.

GPNAV FAQS What is GPNav? Do I need it? GPNav is vehicle tracking application with sophisticated logging routines and outstanding mapping capabilities. Up to 100 map layers are supported and can consist of point, line and polygon SHP files, DXF, DGN and DWG Cad files, or TIFF, JPG and BMP raster images. GPNav supports real time tracking using either NEMA $GPGGA or Trimble GGK serial inputs. A second comm port optionally allows for a NMEA $HCDM or $PTNHTM magnetic heading messages. A third port can be opened for inputting a NMEA $SDDBS depth message. A fourth port can be opened which represents a secondary NMEA $GPGGA position or you may define a secondary position by offsets from the primary GPS position. You can log on an incoming serial comms event or you may send pre-log and at-log serial events out. You may also relay the primary position to a separate port. There is the capability of looking for several inputs on one port. There is an embedded simulator which can be used for training and configuration purposes. -------------------------------------------------------------------------- How can I use the embedded GPNav simulator? On the Map Properties dialog, enter a latitude and longitude and a radius in meters. When the simulator is started from the Utilities menu, a simulated position will circle the coordinates (the radius of which was entered). You need to enter the local grid coordinate system on the Map Properties dialog that represents the system of all image and vector layers to be imported.

GPARC FAQS What is GPArc? Do I need it? How do I install it? GPArc is a presentation mapping application which is available to the user as are all other GPSeismic applications, however, it is different from the rest in that it relies on a set of libraries that must be purchased from a company called ESRI. No other GPSeismic applications require additional third party libraries. If you already have a favorite mapping application, you don't have to read further. If you do need a mapping application, GPArc might be the tool for you. Here are the basic requirements: GPSeismic requirements -You should first download and install GPSeismic. If you have not done that already, go to the download page now. ESRI library requirements - You must install ESRI's software libraries called 'ArcGis Engine Runtime 10.0' for Windows. If you currently have ArcView, ArcEditor or ArcInfo 10.0 installed on your system, neither this step nor any steps below are necessary (except for Service Packs) and you should be able to start using GPArc immediately. If not, you must purchase ArcGis Engine 10.0 and install. You should choose the 'typical' installation and follow all the prompts. Generally speaking, you should be using the Service Pack that GPArc was compiled with. For GPArc 2011.3, this is ArcGis 10 SP1. For GPArc 2011.1, this is ArcGis 10 SP3. To purchase the ESRI runtime license contact your regional ESRI office. At the time of this writing, the cost was 500 US. You can use ESRI's regional US office page or international page to help assist you in finding a contact number. Again, make it clear that you want to purchase the 'ArcGis Engine Runtime' 10.0 libraries for Windows. Once you purchase the 'ArcGis Engine Runtime', you can order a DVD or download the software from their site (It's a huge download so we suggest ordering the DVD. You will also be sent an authorization number. Once the ESRI libraries are registered, GPArc should run. ---------------------------------------------------------------------------- What are the system requirements for GPArc? Do you intend to load large images? Generally speaking you need enough memory for your operating system (discussed below), the application and associated libraries, and the map layers you are rendering. SHP files require very little memory unless there are many associated labels. Labels take up a lot of memory and you should minimize the number displayed at any one time. Raster images can generally be thought of as requiring as much memory as their size. So, for example, a 1 GB raster requires 1 GB memory. So as an example, lets say you have a dozen SHP layers and a 500MB raster image. In general terms you will need 500MB for the image, approximately 100MB for the application and approximately 50MB for the remaining layer rendering including labels. The total is 650MB. However, this does not represent how much the operating system requires. If you are using Windows XP and run a clean system (meaning no concurrent applications or memory resident items), expect XP to take up about 200MB of Ram. Add this to the above numbers and you are up to 850MB. Could you get by with 1GB. Yes but it would be cutting it close. If you run some tests on Vista, its pretty disturbing. Immediately after booting, run task manager and you will see where you are using about 1GB of RAM (if you run a very clean system, meaning you run no background applications). This means that 1GB is being used just to run the operating system (and other essentials like virus scan). Now do the math with the numbers in item 1 and you can see where you will have dicey results with 2GB of Ram. It would seem 4GB is best. Finally, you might hear about the fact that you can add memory to a PC running Vista by plugging in a memory stick. This method of adding memory is pretty much a joke. Yes it provides more apparent 'Ram' but it is only OK with slow reads, not where random read/write is required. It turns out, most memory is accessed in this manner so this feature is pretty much useless. ---------------------------------------------------------------------------- I have seen a layer just disappear for no apparent reason. What gives? GPArc is based on a set of libraries that insist on creating a file with an 'sbn' extension. For example, if you have a SHP layer called MyGreatLayer, there are actually three files that collectively form the layer: MyGreatLayer.Shp MyGreatLayer.Shx MyGreatLayer.Dbf All these files serve a useful purpose, but the MyGreatLayer.Sbn file, also called a spatial index file, can cause problems if the SHP file is re-created with different extents. In this case, the SBN should be deleted. In version 2008, and greater some protection was put in for this that pretty much removes the sbn file when it gets created. ---------------------------------------------------------------------------- I am drawing a polygon and want a hole in it. How do I do that? If you want multiple parts for a polygon (like a hole), when you finish the solid part of the polygon, rather than double-clicking, hold down Shift and double-click to finish this part, then trace the inside part and finish normally by double clicking. This will create the hole. As far as lines, when you draw a line and then double click, finishing it, if you immediately draw another line, you will find that this is a different and completely different line from the first and has its own individual record in the underlying database. However, if you want two visibly distinct lines, but you want them to essentially be the same entity (i.e., one record in the database), then when you finish the first part, hold the Shift key when double clicking, then draw the second part. Finish the second part in the normal way by double clicking. You will find the the two parts are treated as one line. ---------------------------------------------------------------------------- My labels will not appear. What do i do? When you defining your labels, if you specify an SQL expression for a string field that involves the MOD operator, you are warned that this type of expression requires a numeric field. The same warning is given if you are inappropriately trying to assign a string expression for a numeric field. However if these warning work only with the 'helper' buttons. If you manually write an expression that is inappropriate for the field type, you will notice labels for all layers disappear.

GPLOCATOR FAQS What is GPLocator? Do I need it? GPLocator is the only optional application in the GPSeismic suite. For pricing contact Cliff Harris. GPLocator is a fleet tracking application. Its capable of tracking up to 130 vehicles simultaneously. It has a map component in which the user can display registered raster images and shape files or any combi- nation. There is a tabular component which gives constant readouts of all important vehicle information including position, speed and heading. There is also a quality control component that alerts the user if certain conditions have been met. For example, the user can have an alert raised when any vehicle is within a defined area. ---------------------------------------------------------------------------- How do I receive the vehicle position information? We don't offer any hardware for fleet tracking. GPLocator is capable of accepting data via the web or via serial communications. It also can work with flat files. Here's a summary: Web and network based - There are a two supported formats. One is by UDP PACKETS This is a NMEA $GPGGA message that GPLocator would receive over an ethernet connection. The origin IP address would uniquely identify the vehicle. The second is a web based service is that offered by Fleet Management Systems (FMS). GPLocator presently supports FMS, a company that provides its client with vehicle tracking hardware consisting of a GPS receiver and a phone (cell or satellite). Their system relays the position of each vehicle to their website where the data is available to anyone with the correct user name and password. GPLocator can be configured to make periodic request for vehicle position data from their website. Serial comms based - There are a several supported formats, all of which are listed here. Minimally, any format must contain a vehicle ID, time of position and position in practically any coordinate system (although WGS84 geographic coordinates are most common). Dynamic Survey Solution will support additional protocols at no charge. Here is what we currently support: Raveon: ------ $PRAVE,0002,0001,3308.9037,-11713.1167,165919,2,9,184,25,12.7,0,-95,0,0,,*76 $PRAVE,0003,0001,3308.9086,-11713.1138,165920,2,10,189,25,13.0,0,-100,0,0,,*73 The Raveon data has the sender's ID as the second comma delimited string. Teledesign: ---------- +TSNA01003$GPGGA,223419.19,3157.1422,N,10208.4465,W,1,05,2.8,841.6,M,-23.0,M,,*5C +TSNA01003$GPGGA,223409.19,3157.1419,N,10208.4464,W,1,05,2.8,840.5,M,-23.0,M,,*56 The five characters after '+TSNA' represent the vehicle ID so above that is '01003'. Kantronics: ---------- G12>$GPGGA,223419.19,3157.1422,N,10208.4465,W,1,05,2.8,841.6,M,-23.0,M,,*5C G12>$GPGGA,223409.19,3157.1419,N,10208.4464,W,1,05,2.8,840.5,M,-23.0,M,,*56 Here, G12 is the vehicle ID Kenwood: ------- $PKLDS,140520,A,2947.4050,N,09540.5596,W,000.0,000.0,210605,5.4,W00,349,4900,80,00,*67 $PKLDS,140520,A,2947.4050,N,09540.5596,W,000.0,000.0,210605,5.4,W00,349,4900,80,00,*67 ...the vehicle ID is'3494900'. PBX Tail Buoy tracking system: ------------------------------ $GP1001,223419.19,3157.1422,N,10208.4465,W,1,05,2.8,841.6,M,-23.0,M,,*5C $GP1001,223409.19,3157.1419,N,10208.4464,W,1,05,2.8,840.5,M,-23.0,M,,*56 This is essentially the NMEA string in which the 'GGA' has been replaced with the vehicle ID, in this case '1001'. GPLocator also supports the following data files. These are produced by 'black box' instruments that are placed on vehicles and record positions, but don't work with a radio link. When a vehicle returns to base, the contents are downloaded to a PC as an ASCII file. GPLocator can quickly create log files from these file which in turn can be played back or analyzed. GPTracker: --------- S9022879 &4.2 ?P-105084 #I0,051005,124609 #I1,051005,153552 $,153634,2940.1707,N,9539.6824,W,12.6,051005 $,153637,2940.1821,N,9539.6762,W,15.8,051005 $,153640,2940.1944,N,9539.6696,W,15.7,051005 $,153643,2940.2084,N,9539.6674,W,17.6,051005 $,153646,2940.2240,N,9539.6674,W,18.4,051005 $,153649,2940.2385,N,9539.6659,W,15.0,051005 $,153652,2940.2459,N,9539.6567,W,13.8,051005 The third line gives the vehicle ID. In example above, the ID is '105084'. Faucon: ------ Waypoint 2 23.68577 14.68929 L 0 19/9/6 9:10:30 Waypoint 3 23.68593 14.68912 L 0 22/9/6 6:32:36 Waypoint 4 23.68570 14.69085 L 10 22/9/6 6:38:18 Waypoint 5 23.68503 14.68829 L 10 22/9/6 6:40:10 Waypoint 6 23.68517 14.68828 L 0 22/9/6 6:55:48 Waypoint 7 23.68540 14.69069 L 5 22/9/6 7:1:29 Waypoint 8 23.68547 14.68883 L 5 22/9/6 7:5:25 GPLocator prompts for a vehicle ID for each file. Lat/Lon is in DD.dddd format.

QUIKCON FAQS What is QuikCon? Do I need it? QuikCon processes conventional data. If you only use GPS for your surveying, read no further. QuikCon processes about 30 different formats. If you have a conventional data file you want supported, we will be glad to do it. But don't just send a file. Also send the all information necessary to understand the data. For example, we need to know how to identify back sights, fore sights, and sideshots. We need to know how to determine face 1 and 2 shots. We need to know how to determine the HI for the setup and the HRs for all the shots taken from the instrument point. Don't assume that we have some magic ability to determine these things without help. Also, conventional data is often highly dependent on field procedures. If you say, for example, that 'BS' is used to identify a back sight, we would like to know if that is inherent in the equipment or if you are purposely coding this way in the field. -------------------------------------------------------------------------- Q - I'm not sure if we're doing something wrong but I have found that when I export data from QuikCon into Quikview it takes the height of the instrument station across as the rod height for all the side shots from that station. It looks to to as though it is taking the wrong column across - using the HI column from QuikCon instead of the HR column. A - QuikView shows the HI's initially in the Antenna Height dialog. You could actually change these which would affect all stations that were shot from a particular setup. After populating the database, the HI's go into the HI field and the HR's go into the 'HR' field if, when you created the database, you chose to use the 'conventional' field structure for the last several fields. If you went with the default field structure, the HI is placed in the 'Unit Variance' field. This might be why you think the HI's didn't make it into the database. -------------------------------------------------------------------------- Q - How do I combine 2 traverses that were shot in opposite directions. A - Reverse the order of one traverse using 'Reverse Observations' in the Edit menu of the DCO editor. This re-orders the DCO observations, switching the 'Pcod's of back sights and foresights and changing the instrument and back sight IDs accordingly. This feature can assist the user in saving one set of observations in which direction is consistent even if the line was shot in several segments in different directions. This utility requires that observations begin with a back sight and end with a foresight. -------------------------------------------------------------------------- Should I correct for parallax and refraction when computing a sunshot? The following may help you decide whether to correct for parallax and refraction if you use the Altitude sunshot method .My knowledge of this comes from two sources... Surveying Theory and Practice Andeson and Mikhali Sokkia Celestial Observation Handbook In both references, it is implied that the corrections should be made for the Altitude Method. Here are the corrections QuikCon makes. Correction For Parallax = 8.94 * SIN(Zenith Angle) Note that this correction is in seconds so even if the sun was on the horizon, the adjustment would be 8.94 seconds. It therefore does not account for a lot. Correction For Refraction = 0.00452 * Pressure * TAN(Zenith Angle)/Temp Note that pressure is in millibars and temperature in Kelvin. This correction is in degrees. Since the refraction correction varies as a tangent to the zenith angle, an observation at 45 degrees would generally yield a 50 second correction. An observation at 85 degrees would yield a correction of over 11 minutes. The total correction is applied as follows: Zenith Angle = Zenith Angle - Correction For Parallax + Correction For Refraction -------------------------------------------------------------------------- Q - How far back can I go when using the sunshot program in QuikCon? I have some old observations and I'm concerned about using the computed ephemeris values. A - If you enter high resolution ephemeris from a outside source, it doesn't matter. If you go with the computed ephemeris, I feel comfortable with the late 1980's. I say this because I can enter 1994 observations and use the presently computed ephemeris to derive results within 10-13 seconds or so. So I suspect that if it can be trusted to provide that kind of accuracy 7 years in the future, the same should hold true in reverse. -------------------------------------------------------------------------- Q - How are the various mis-closure values computed? Horizontal Ratio - The reciprocal of the difference between computed and known coordinates divided by the cumulative slope distance at that point. Vertical Ratio - The reciprocal of the difference between computed and known height divided by the cumulative slope distance at that point. Vertical QC - Difference between computed and known height divided by square root of cumulative slope distance divided by 1000. Azimuth Constant - Difference between computed and known azimuths in seconds divided by number of setups at that point. So if, at some point, we had a mis-tie of 1 meter and the cumulative slope distance of 10,000 meters the Horizontal Ratio would be 1:10,000. If for some reason at this point, the height mis-tied by 25 meters we would have a Vertical ratio of 1:400 and the Vertical QC would be computed by 25 / SQRT(10000/1000) = 7.9 If at this point, there was a mis-tie of 1 minute between computed and known azimuths, and there were 5 setups prior, then the Azimuth Constant would be 60/5=12. Nominal Vertical QC - Spreadsheet cells are colored red if values in those cells are greater than the numbered entered by the user. Nominal Azimuth Closure - Spreadsheet cells are colored red if values in those cells are greater than the numbered entered by the user (DD.MMSSss) Nominal Azimuth Constant - Spreadsheet cells are colored red if values in those cells are greater than the numbered entered by the user. -------------------------------------------------------------------------- Q - Why are the azimuth misclosures different in the classic report and the spreadsheet? Also, what is the azimuth constant? A - In the classic report, the azimuth closure is in DDD.MMSS format, for example: 000.0237 () 000 degrees 02 minutes 37 seconds) In the spreadsheet, it is in DD.ddddd format: 0.0436121666 degrees (which is 000.0237 in DDD.MMSS) If you check the formatting checkbox in the spreadsheet, the column will be displayed in DDDMMSS format. The azimuth constant is the azimuth difference in seconds divided by the number of setups at that point: 0.0436121666 * 3600 / 66 = 2.38 -------------------------------------------------------------------------- What are TI points used for? TI points are similar to side shots but have one additional use, namely, to fix azimuths during processing. If you shoot one or more TI points and you know the foresight azimuths for these shots, it's possible to use this information to fix back sight 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 back sight 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 back sight azimuth of the next setup in the traverse. For all essential purposes, the appearance in the spreadsheet will be exactly like a fixed back sight azimuth and the difference can be prorated if required.