- Defense & Intelligence Back
- Advanced SolutionsBack
GeoRover® Software Support
Get help with GeoRover geospatial software products. Our support team is ready to help you by email or phone, or you can review a list of common concerns below.
- Affected Software: All GeoRover and Leidos Geospatial software extensions
- Description: Text and buttons are cropped off from the windows and forms displayed. In some cases, you will not be able to click buttons that are partially cut off or not visible on the window.
- Solution: Set the display settings to the recommended screen resolution for ArcGIS for Desktop, which is a minimum of 1024 x 768 or higher at normal size (96 dpi). For additional information and instructions, refer to Esri's technical article on screen resolution.
- Affected Software: GeoRover Locus Track version 4.0.0
- Description: When editing a selected feature attribute(s), if changes have not been saved and another feature is selected, the changes are discarded. Although a pop-up form asks to save changes, a Yes response fails to save the changes.
- Cause: This is a GeoRover Locus Track bug in version 4.0.0
- Solution: This bug will be corrected in future releases of GeoRover software. The workaround is to save the current feature before selecting another feature.
- Affected Software: GeoRover Locus Track version 4.0.0
- Description: In the first page of the Feature Import Wizard, selecting a layer from the Map drop-down list causes a series of Unexpected Errors. The series of error are similar to the following:
- Error: -2147216010
- Source: esriDataSourcesGDB.SdeWorkspace.1
- Description: Function called out of sequence [name of the SDE layer]
- Procedure: nextLine LocusTrack\LocusTrack\clsImportTable_LorSAT.cs Line : 167
- Cause: This is a GeoRover Locus Track bug in versions 3.3 and 4.0.0
- Solution: This bug will be corrected in future releases of GeoRover software. The workaround is to browse and select an SDE layer using the File/GIS Data interface.
- Affected Software: GeoRover Digital Data Tracker version 4.0.1+
- Description: After GeoRover Digital Data Tracker version 4.0.1 is installed over GeoRover Digital Data Tracker version 4.0.0, uninstalling GeoRover Digital Data Tracker version 4.0.1 leaves behind extra files.
- Cause: Inconsistencies between installation GUIDs
- Solution: If you have 4.0.0 installed, uninstall this version before installing 4.0.1+ (otherwise extra files will remain after 4.0.1+ is uninstalled).
- Affected Software: GeoRover Mobile v1.x
- Description: After installing the GeoRover Mobile Application on an Android device Windows Explorer will not properly display the GeoRover Folder in the Android Device's Internal Storage. Windows Explorer may display GeoRover as a an unknown file type. The Windows user is unable to navigate into the GeoRover folder in their Android Device's Internal Storage to copy License Files or MapPacks to the Android Device.
- Cause: Android OS will only re-scan the device's Internal Storage for the absolute path of each file after a restart of the Android Device.
- Solution: a) On the Android Device, navigate to Settings --> Apps --> All Apps and Open Media Storage b) Select "Clear data" --> "OK" c) Restart Android Device.
- Affected Software: All Leidos Geospatial Extensions
- Description: There is a conflict with installing Leidos Geospatial products when SAIC Geospatial products are currently installed.
- Cause: Shared common DLLs referencing the same GUIDs installed in different folders due to branding
- Solution: It is highly recommended that all SAIC Geospatial ArcMap extensions be removed before installing any Leidos Geospatial products.
- Affected Software: ArcGIS 9.0 - 9.3 with any version of GeoRover software.
- Description: This bug is characterized by increasingly slower editing, usually apparent after eight (8) or more consecutive edits. This only happens under the following conditions: 1) the shapefile was empty at some point, either newly created or all features deleted, and 2) During the same ArcMap session that the shapefile was empty, more than 8 edits were made to the layer.
- Cause: This is actually an Esri bug (NIM006247), but is exposed most often using GeoRover editing tools, such as those in the Locus Track or Range Tools extensions. The reason for this is the "quick-edit sessions" which allow multiple edit sessions to be opened/closed in a very rapid manner.
- Solution: Esri fixed this bug in ArcGIS Desktop 9.3 Service Pack 1 (SP1). If ArcGIS Desktop 9.3 SP1 can not be installed, the best practice is to save and close the map document after creating a new, or otherwise empty, shapefile then re-open the map document and continue editing normally.
- Related Information: Esri Support Center
- Affected Software: GeoRover Locus Track versions 3.2-3.2.3
- Description: Exporting as a tab-delimited text file actually exports as space-delimited.
- Cause: This is a GeoRover Locus Track bug in versions 3.2-3.2.3
- Solution: This bug has been fixed in Locus Track version 3.2.4. Contact us at email@example.com or 866-417-5322 to request the latest version of Locus Track. A work- around for this bug is to use the Locus Track Export Wizard to export to a Text File, then choose the "other" character field to choose a delimiter, and paste a tab character into the box (Open Notepad, type a tab, and copy/paste it).
- Affected Software: GeoRover RPF Tools versions 0.9-1.0.1 with ArcGIS 9.x.
- Description: If a saved map document has a GeoRover RPF Layer, and the .gmc file for that layer is not present when the map document is opened, ArcMap crashes.
- Cause: This is a GeoRover RPF Tools bug in versions 0.9-1.0.1 with ArcGIS 9.x.
- Solution: This bug will be fixed in future releases of RPF Tools software. There is a workaround for this bug: put a valid .gmc file where the map document is expecting the original .gmc. The map document should open. If necessary, you can then remove the problem RPF layer, add in correct RPF layer, and save the map document.
- Affected Software: GeoRover Locus Track Versions 3.1 - 3.2 with ArcGIS Version 9.2 or later.
- Description: When trying to move a polygon or line vertex with GeoRover Locus Track "Move Feature by Click-and-Drag" tool, the edit fails and the following error message appears: "The Project method cannot do a datum transformation."
- Cause: This is a bug with GeoRover Locus Track Version 3.1-3.2 with ArcGIS 9.2 or later.
- Solution: This bug has been fixed in newer versions of Locus Track software. Contact us at firstname.lastname@example.org or 866-417-5322 to request the latest version of Locus Track.
- Affected Software: GeoRover Coordinate Viewer extension version 1.0.2 with PLTS for ArcGIS 9.3.1, PLTS for ArcGIS 9.3 Foundation Service Pack 1, or PLTS for ArcGIS 9.2 Foundation Service Pack 6.
- Description: This conflict occurs when the GeoRover Coordinate Viewer extension is enabled, and one of the conflicting versions of PLTS is installed. In this scenario, when some map documents are opened via File > Open, or the ArcMap startup window, ArcMap crashes without any error messages.
- Cause: This is a conflict between the PLTS Attribution Center Extension and the GeoRover Coordinate Viewer extension.
- Solution: We are working with Esri to eliminate this conflict in future versions of PLTS and GeoRover Coordinate Viewer. There are several workarounds for this conflict:
Only open the map document by double-clicking in Windows.
Disable the GeoRover Coordinate Viewer extension before opening the map document via the File > Open method. Once open, the Coordinate Viewer extension can be re-enabled.
Before opening ArcMap, use the Component Category Manager to disable the PLTS Attribution Center Extension:
- Navigate to C:\Program Files\ArcGIS\bin\.
- Double-click on categories.exe
- In the Component Category Manager window open the Esri Mx Extensions folder.
- Select the PLTSAttCenter.AttCenterExt entry and click the Remove Object button. This removes the registry entry that marks a class within the AttCenterExt.dll as an ArcMap extension. This extension will not be available until it is re-enabled.
To re-enable with the Component Category Manager:
- Select the CEsri Mx Extensions folder and click CAdd Object.
- Choose the CC:\Program Files\PLTS\Bin\AttCenterExt.dll and click Open.
- Ensure only CAttCenterExt is checked by unchecking the other entry (IACApps) and click OK.
Uninstall either one of the conflicting products.
- Affected Software: ArcGIS 10.x with GeoRover Locus Track V3.3
- Description: If VBA_SDK is not installed, the Locus Track V3.3 installer will not complete, and will instruct the user to install VBA_SDK from the ArcGIS Desktop installation package. If VBA_SDK is installed but not authorized, the Locus Track extension can be installed, but not activated.
- Cause: Starting with ArcGIS v10.0, VBA is not installed automatically with ArcGIS for Desktop. VBA_SDK must be manually installed, and a VBA authorization file requested from Esri. At ArcGIS 10.1, Esri stopped fully supporting VBA. Esri offers a VBA compatibility install for ArcGIS for Desktop10.1, but this does not fully enable functionality of Locus Track.
- Install VBA_SDK:
- For ArcGIS 10.0, prior to installing Locus Track V3.3, run the Setup for ArcGIS Desktop VBA Resources for Developers from the ArcGIS for Desktop installation.
- For ArcGIS 10.1, prior to installing Locus Track V3.3, run the Setup for ArcGIS VBA Compatibility from the ArcGIS for Desktop 10.1 installation. After successful installation, proceed with installing the ArcGIS Desktop 10.0 VBA Resources for Developers, which is provided via the Esri customer portal. Both VBA installations are required to enable functionality of the Locus Track extension.
- Authorize VBA: Contact Esri to request a VBA Authorization file.
- Related Information: Esri Support Center
- Affected Software: ArcGIS 10.2.1 with GeoRover Locus Track, Coordinate Viewer, and Zoom Tools Products.
- Description: After installing ArcGIS 10.2.1, coordinate issues can be experienced within the GeoRover Locus Track, Coordinate Viewer, and Zoom Tools extensions.
- While using the Locus Track extension, the symptoms are experienced as the MGRS and UTM coordinate fields within a layer will stop auto-populating with the location of the feature, along with an unexpected error. Additionally, incorrect DD, DMS or XY coordinates are possible.
- While using the Coordinate Viewer extension, the symptoms will be blank MGRS or UTM fields in the Coordinate Window, and inability to copy MGRS and UTM coordinate lists from the Coordinate Lists window. Additionally, incorrect DD, DMS or XY coordinates within the Coordinate Window or Coordinate Lists window are possible.
- While using the Zoom Tools extension, the symptoms will be experienced as blank coordinate fields in the MGRS and UTM tabs of the Zoom to Location window. Additionally, incorrect DD, DMS or XY coordinates are possible.
- Cause: This issue is caused by Esri Bug NIM-100236.
- Solution: There are Beta versions of the GeoRover extensions available until Esri corrects the bug or the next release of each GeoRover extension. Contact email@example.com for more information.
Download a free trial of the latest GeoRover software:
- Digital Data Tracker 4.1
- Range Tools 4.1
Easily import track logs and waypoints from a variety of GPS receivers (formats include GPX files or GPS-tagged data), and displays these imported formats.
Interactive tool enabling the user to create, edit, and import ring, ellipses, and arc feature layers.