download the software
get your questions answered
learning resources





show me highest rated faqs QuikView FAQs

  • Job name not in database!

    If you are using a utility import feature of QuikView (including Generic ASCII), note the following. In QuikView, when certain primary systems are selected, certain flags are raised. For example, if you are in Leica mode, there is no single download file and as such, a filename is never sent to the database. If you are in Inertial System modes Applanix or Zupt, a data collector Job name does not apply so a flag is set never to populate that field. So the answer to the this apparent problem is to make sure a primary system is selected when you process your utility files that is neither of the above. Trimble would be a good choice.

    x +

  • Omit bad points in transformation

    Q - I have a point in my data collector file whose coordinates are grossly in error and QuikView can\'t transform the coordinates. Is there a way I can delete this point ?

    A - In the QuikView.INI file which is found in the Windows folder, add the following section at the bottom:

    [Preplot Limits] UsePreplotLimits=1
    PreplotMinLat=20.0
    PreplotMaxLat=70.0
    PreplotMinLon=-140.0
    PreplotMaxLon=-60.0

    In the example above, this tells QuikView that the acceptable range for preplots and base points is from latitude +20 to +70 and in longitude from -140 to -60 (decimal degrees). Change these values to suit your job. When you want to turn this check off, just change the 1 in the UsePreplotLimits line to a 0.')

    x +

  • Compute offsets with no preplots

    Q - How can I compute offset information in QuikView for surveyed points that had no corresponding uploaded preplot?'

    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.'

    x +

  • Displaying masks quickly

    Q - 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

    A - 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.

    x +

  • How is Glonass handled?

    The requirement for a new GPS/GLONASS survey mode first came up with Leica System 1200 a little more than a year ago. 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 complained 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 the release of v2006.3 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.

    x +









QuikView FAQs

  • 'RMS of the difference...' message

    Q - 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.""

    A - 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 form 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.

    x +

  • Do you have training videos?

    A - We have the following videos.

    QuikView - Verifying base station information (8.1MB)
    QuikView - Coordinate and geoid selection (8.3MB)
    QuikView - Simple example of creating and working with masks.(864 KB)
    QuikView - Downloading Leica Data (7.2MB)
    QuikView - Downloading Trimble Data (7.8MB)
    QuikView - Modifying Data (8.4MB)
    QuikView - Preplots And Offsets (8.0MB)
    QuikView - Quality Control (6.7MB)
    QuikView - Updating The Database (7.6MB)
    QuikView - Using Masks (7.2MB)

    x +

  • Azimuths Discussion

    In QuikView, inline azimuths are entered and displayed in the Azimuth page of the Offsets dialog as true (geodetic). Project Manager ultimately requires the same. The reason for this is because QuikView normally begins with data in WGS84 geographic coordinates and does not have the local grid coordinates until after a transformation has been performed. So, in QuikView, when local grid coordinates are not available (typically before a transformation has been performed) inline azimuths are geodetic.

    Once local grid coordinates are available, inline azimuths are grid. Remember that when using ASCII Import or when importing QuikCon CVX files, local grid coordinates are available immediately and inline azimuths are then grid. Whatever is used for the inline azimuth (geodetic or grid) that value is used in all offset computations, spreadsheets, and reports.

    An interesting test is to open a file in QuikView (a GPS file so that WGS84 geographics are imported), then before performing transformations, do an inverse (right-click Home/End). Note that the title of the inverse dialog says Geodetic Inverse Computation . Then press Transform and repeat the inverse computation. Note that the title of the inverse dialog now says Grid Inverse Computation . With the inverse dialog shown, press the Use Bearing for Sources button. Now go to the Azimuths page of the Offsets dialog and note that the source azimuth is shown as true even though the displayed azimuth in the Inverse dialog is grid.

    Summary of Inline Azimuth use in QuikView:

    1) The Azimuth page of the Offsets dialog always reflects geodetic azimuths.

    2) When local grid coordinates are not available, azimuths used for offset computations will be used as shown in the Azimuth page of the Offsets dialog (geodetic) and offsets are computed on the WGS84 ellipsoid.

    3) When local grid coordinates are available (after a transformation or when using some of the Utility Import options), azimuths used for offset computations will automatically be corrected by the convergence angle (to be grid azimuths) and offsets will be computed on the local grid.

    4) Whatever is used for the inline azimuth (geodetic or grid), that value is used in all offset computations, spreadsheets, and reports.

    If you are working 2D and using a CRK file which contains many azimuths, the Azimuth page of the Offsets dialog clearly states that Crooked line logic will only be used after a transformation. CRK files always contain grid azimuths and are all programs which use CRK files (QuikLoad, GPSQL, QuikMap, and even QuikView) will only use them with grid coordinates so that offsets are computed on the local grid.')

    x +

  • Using a grid definition file

    You can use a grd file in QuikView to essentially create preplot points (and therefore offset information).

    You select a grid definition file on the Offsets dialog in order to have QuikView compute a preplot for a surveyed point that does not have a preplot in either the downloaded file or a QLD file. Once a grid definition file has been selected, AND the surveyed points have been transformed, if a numeric point does not have a corresponding preplot, the Changes dialog will display a Compute Preplot button. When pressed, offset information is computed and displayed for this point. If you have a receiver and source grid definition file defined, QuikView uses the source and receiver discrimination parameters of the Offset dialog to determine which grid definition file to use. A button on the Offsets dialog allows the user to compute preplots and, therefore offsets for ALL surveyed points which don't have preplots.

    x +









QuikView FAQs

  • Can't Communicate With Garmin

    If you have a Garmin that attaches via a USB cable and are having problems connecting using QuikLoad or QuikView, there could be a simple answer. These units comes with software drivers that allow for serial communications via the USB port. If you don\'t install the USB driver, no application will be able to connect to the Garmin.

    x +

  • Can't Communicate With Magellan

    Q - I am trying to download some waypoints from a Magellan Explorist 500. I have no Magellan software, just the units themselves. When I connect to my PC I immediately get an error message which repeatedly pops up in the bottom right hand corner of my screen. The message states "USB Device Not Recognized". Any suggestions?

    Unlike Garmins which require specialized device drivers, the Magellans interface like a regular disk drive. If you are seeing "Device is not Recognised" when you hook up the unit, chances are you inserted the cable into the Magella incorrectly. It should be directed down toward the bottom of your unit. If you have the cable connected so the cable is directed toward the top of your unit it will say "Device is not Recognised"....... If this fails I would check all your cable connections and delete the unknown device from Device Manager.

    x +

  • Can't populate Postplot table

    Q - 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 couldn\'t 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?

    A - 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.

    x +

  • What Is the Alternate Datum?

    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.

    x +