ArcPad has long supported 2-point offset constructions (bearing-bearing or distance-distance) for points and line/polygon vertexes. When using an optical rangefinder (e.g., LaserAce or TruPulse), the rangefinder button can be used to populate the data for Reference Point A then Reference Point B in succession. This is partially enabled through ArcPad changing control focus after the first reference point is shot.
In the Geo 7X Rangefinder workflow, pressing the rangefinder button on the device launches the rangefinder app. After a point is shot (by pressing the device button again), you click the checkmark icon to return to ArcPad. This should populate the data for Reference Point A and move the control focus to Reference Point B. Unfortunately, when you then try taking the second shot and returning to ArcPad, control focus is no longer on Reference Point B because of the application switching. The result is that Reference Point A gets replaced with the new shot and there is effectively no way to populate Reference Point B automatically from the rangefinder on the Geo 7X.
We are discussing this issue with Esri and will update our user community when we have something to share.
Earlier this year, an operating system update (6.7.16) was released for the Geo 7X handheld. Support cases submitted to both Trimble and Esri have indicated that ArcPad users with complex projects are running up against memory problems with increased frequency after upgrading their devices to this new OS version. Customer and dealer testing indicates that there is ~4MB less memory available to the application compared to the old OS version.
This issue is being investigated internally. Initial testing suggests that any high-memory use application could be affected including ArcPad and ArcGIS for Windows Mobile + Trimble Positions. At this time, it is recommended that Trimble Positions users with larger field projects stay at the previous operating system version (6.7.15) until further notice.
We’ve been asked on several occasions about support for ArcMap version 10.3.1 in the latest version of the Trimble Positions Desktop add-in (version 10.3.0.2). Initial testing indicates that upgraded installations will generally work (i.e., ArcMap was upgraded after Trimble Positions Desktop was installed) but that new installations on ArcMap 10.3.1 will not see a properly registered add-in. There are 2 workarounds:
- Manually add a registry entry to mimic what the installer is supposed to be doing. This will preserve the proper uninstallation behavior of the app. The name of the new registry key should be:
(or if x64, HKLM\SOFTWARE\Wow6432Node\ESRI\Desktop10.3\Settings\AddInFolders)
…and then you’ll create a new string value that points to the path c:\program files\trimble\trimble positions desktop add-in\addins.
- Manually register the PositionsDesktopAddIn.esriAddIn by double-clicking the file in c:\program files\trimble\trimble positions desktop add-in\addins. This will copy the .esriAddIn to Esri’s staging area (c:\users\<user>\documents\arcgis\addins) and ArcMap will pick it up there. In this case, an uninstallation of Trimble Positions Desktop using the Control Panel will not remove it from ArcMap and you’d have to use the menu options within ArcMap to remove the add-in.
Just wanted to put up a quick post on this as we’re starting to see questions in Support. At this time, no components in the Trimble Positions Software Suite are supported on Windows 10. For one thing, Esri has not certified any of their products on Windows 10.
Esri FAQ: Is Windows 10 certified with Esri’s ArcGIS products?
In addition, there are some issues in getting Windows Mobile Device Center to work properly on the desktop.
Some of you may have noticed that a new version of the Trimble TerraFlex Desktop add-in was released last week. This version introduces support for the data update workflow whereby existing features can be uploaded to InSphere as a task creation step in the add-in. Typically we’d also release an updated version of the Trimble Positions Desktop add-in that has the same level of functionality for TerraFlex workflows. However, we have not yet been able to do so.
Although it is technically possible to install the new TerraFlex add-in alongside the existing Trimble Positions add-in (10.3.0.2), you may run into problems in certain workflows. Although most of the underlying components are the same between those versions, some of the InSphere dependencies have changed and so functionality may depend on in what order ArcMap loads the add-ins (and hence what version of the dependencies get loaded to be used by both).
Thus for the time being, the recommendation is to not run both add-ins side-by-side in production workflows unless you have thoroughly tested it and know what works and what doesn’t.
In an earlier blog post, we discussed how to specify a GGF file for use by the Trimble Positions ArcPad extension in calculating mean sea level (MSL) elevations in the field. This is done through a registry entry. The blog post also included a simple utility application (with source code) for creating this registry entry. At the time of that release, the solution only pertained to Windows Mobile. However, in the latest (10.2.2.1) release of the Trimble Positions ArcPad extension, this functionality now exists in the Windows version as well as the Windows Mobile version. The necessary registry entry is the same on both platforms. The simple utility application is available for both platforms:
Note: The download links in the original blog post have also been updated to include the Windows files.
We are extremely pleased to announce the March 2015 release of Trimble Positions. This release adds support for the Trimble R1 GNSS receiver in both real-time and post-processed workflows using the Trimble Positions Mobile extension or Trimble Positions ArcPad extension. This release also includes several bug fixes and incorporates the items discussed in this earlier blog post.
- Support for the Trimble R1 GNSS receiver. Trimble Positions can now be used to collect data on devices paired with a Trimble R1 GNSS receiver via Bluetooth® wireless technology. Both real-time and post-processed workflows are supported.
- Esri ArcGIS for Windows Mobile 10.2.1 support. Trimble Positions now supports Esri ArcGIS for Windows Mobile 10.2.1. The mobile cache synchronization geoprocessing (GP) tools can be used with either Esri ArcGIS for Desktop 10.1, 10.2, or 10.3.
Additional information is available in the release notes:
Note: If you have issues upgrading the Trimble Positions Desktop add-in and the old version still appears, it may be worth manually cleaning the entry in ArcMap’s AssemblyCache after uninstalling the old version and before installing the new version. It’s generally in the following location on Windows 7 (AssemblyCache is a hidden folder):
Another Note: Please be aware that this release of the Trimble Positions Desktop add-in requires a schema upgrade in the office database. After uninstalling the old version and installing the new version, please run the Trimble Positions Desktop Configuration tool and click ‘Test current configuration’ to upgrade the schema.
Our friends at Esri have been working on a 10.2.1 maintenance release of ArcGIS for Windows Mobile. The English language version of the application (and SDK) was released this week and other languages will follow.
New versions of the Trimble Positions Mobile extension and the Trimble Positions Mobile Project Center extension will be required to support this new release. Until those versions are available, you should stay on ArcGIS for Windows Mobile 10.2.
We are grateful to our diligent user community for spotting a couple issues in the November release of the Trimble Positions Desktop add-in and the Session Processor utility. While investigating these issues, we also found a couple other things that we felt warranted fixing. Updated installers for both applications are now available on the Trimble website. The version number remains 10.3.0.1 so you will need to check file revision dates to determine if a machine has the original or the re-release.
- TerraFlex publish/harvest workflows were broken after the TerraFlex Advanced upgrade. This functionality has been restored although the new data update workflows are not supported in this release.
- Session Processor installer did not include all files necessary for ArcPad project support. These files are now included and ArcPad projects can now be used in the Session Processor when ArcPad 10.2.2 is installed on the desktop.
- Session Processor installer did not write a .config file to the installation folder in all cases. The configuration file is specific to the ArcGIS for Desktop version (assembly binding) and should now be written to the installation folder for all supported ArcGIS versions (10.1, 10.2, 10.2.x, 10.3).
- Photo handling was not correct in certain TerraSync workflows. In certain cases, photos may have been missing the full path information or may have received duplicate names on check-in. This has been resolved.
- Change made to ArcMap.exe.config file during installation caused Version Manager toolbar to stop working. The Trimble Positions Desktop add-in installer will no longer make a change to the <startup> tag in the ArcMap.exe.config file. It will only add a supported .NET runtime version. For more information, refer to this earlier blog post.
- Project wizard should not include hidden fields in TerraSync/TerraFlex project layers. If fields are hidden at the time the project is created, they will not be included in the project layers. If changes are made to the geodatabase schema or ArcMap layer definition after the project was created, a new project should be created. The OBJECTID and SHAPE fields should never be hidden in TerraSync project workflows.
- Dockable window should remember last check-out/check-in folder for TerraSync SSF files. This is now functional.
- Layer names > 20 characters were improperly handled in TerraSync workflows preventing check-in. Long layer names are now truncated properly for use in the Data Dictionary Editor. Original layer names in ArcMap should not need to be changed.
- Layer names should have ‘.’ character stripped before being used in TerraSync workflows. Layers added from an enterprise geodatabase will by default contain one or more ‘dots’ in the name. These will be removed automatically for internal layer name storage in TerraSync workflows. Original layer names in ArcMap should not need to be changed.
- Checked-out features (in TerraSync SSF files) that weren’t updated were incorrectly included in a new session on check-in. Unmodified features will now always be excluded from sessions on check-in.
- Feature accuracy values were not populated on check-ins from TerraSync SSF files. In some cases, feature accuracy values were not always populated on check-in. This has been resolved.
Note that because of the changes in TerraSync support, you should check-in any in-progress data before upgrading. Although in most cases, existing check-outs can still be checked-in with this version, there are some workflows (namely those with long layer names) where it likely won’t work.
Non-ASCII characters are unsupported in TerraSync workflows. Currently, the use of non-ASCII characters in layer names/aliases, field names/aliases, and string attributes may cause problems in TerraSync workflows using the Trimble Positions Desktop add-in. This will be fixed in the next release.
In the November 2014 release, we introduced the Trimble Positions Session Processor, a stand-alone utility for processing collected GNSS data (check-in, post processing, feature updating, etc.) based on Trimble Positions project settings. During installation, a proper configuration file is supposed to be stored in the main application folder based on the version of ArcGIS for Desktop (or Engine) components that are installed. However, some customers have reported that this is not always the case and it seems that the installer may not handle all ArcGIS versions properly. The absence of a SessionProcessor.exe.config file prevents the Session Processor from running. Although this will be fixed in a future update, a zip of all the proper configuration files can be downloaded here:
Extract the appropriate SessionProcessor.exe.config for your ArcGIS version and place it in the main application folder where Session Processor was installed. Note that these configuration files do specify a default log file and path (C:\Temp\mylog.log) that you may want to change prior to running the application.