TerraFlex add-in for ArcMap v4.10

A new version of the TerraFlex Desktop add-in for ArcGIS Desktop (ArcMap) is available for download here. As a reminder, the add-in supports both TerraFlex on Connect and TerraFlex on InSphere workflows. The lists below do include some changes that were released in 4.02 and 4.04.

New Features & Improvements

• Accuracy reporting (68/95%) option for TerraFlex on Connect workflows. Users of TerraFlex workflows can now configure accuracy reporting for both field and office. Additional office-side metadata is also available.
• Easier configuration for common metadata and auto-fill fields. Improvements have been made to the Layer Settings page of the project wizard to make auto-collected/metadata field configuration easier. You now have the option to ‘add all (common)’ fields in a single click.
• Improved real-time correction datum configuration. Previously, the field configuration wizard always used an Esri coordinate system selection tool for setting the coordinate system of the real-time correction source. This made sense for Esri field workflows but did not make sense for Trimble field workflows that utilize the Trimble Coordinate System Database (CSD). Field configurations created as part of the project wizard for TerraFlex on Connect workflows will now use a Trimble coordinate system selection user experience.
  Note: If you are creating local field configurations and publishing them to Connect as part of your projects, and are using the TerraFlex add-in on a computer without other Trimble desktop software installed, you will need to install the Trimble Coordinate System Manager software component available for download here. This is a one-time installation and the software will auto-update.
• Improved handling of photo downloads. Improvements have been made to how photo downloads are handled with regards to the Esri edit session (and for enterprise geodatabases, transaction) handling. All photos are now downloaded to the temp folder prior to opening the edit session and then stored as attachments along with the feature inserts and updates. This reduces the time that the session (and transaction) is open.
• New office-side metadata fields. Based on customer requests, we have added several new metadata values that can be transferred to feature class attributes when forms are downloaded: Accuracy Reporting Setting (currently always RMS - 68%), X Coordinate (in the current map coordinate system), Y Coordinate (in the current map coordinate system).

Bug Fixes

• Error when trying to publish a TerraFlex project when the name ends with a space or a period or otherwise contains invalid characters (e.g., slashes). The add-in would be unable to publish a project if the project name ended with a space or a period or contained characters not supported in Connect. This has been resolved to trim trailing spaces and to validate that the name does not contain or end with unsupported characters.
• Errors when trying to access NTRIP source table from add-in. When creating a field configuration, the wizard will try to access the NTRIP source table to list the mount points. This would often fail (unable to connect) if the computer you were using was NOT behind a firewall due to non-standard HTTP headers in the NTRIP messages. This has been resolved to always retrieve the NTRIP source table. In addition, if there are still issues with contacting the NTRIP caster (server) through Trimble TerraFlex Desktop, you can save the source table information to a text file (e.g., from a browser) and then Control+click the ‘...’ button and browse to the file.
• Can not publish local TerraFlex project to a new Connect project in the non-default region. During publishing of a local TerraFlex project to a Connect workspace, users have the option to pick an existing Connect project (across all regions) or can specify a new project to be created in the specified region. If the user selected the option to publish into a new Connect project and picked a region other than the default (the first one in the list), it would publish the workspace into a new project in the default region only - and not the region specified. This has been resolved.
• Can not edit local TerraFlex project if published to a Connect region other than North America. If the user published a local TerraFlex project into a Connect region other the default region, they would not be able to edit it through the project wizard. They would receive a message (with corresponding log entry) about not being able to find or access the project. They likely would still be able to download forms through the dockable window however. This has been resolved and all projects can now be edited through the project wizard provided the appropriate map document is open.
• Office-side metadata fields did not always populate. Certain office-side metadata fields (e.g., accuracy reporting setting) did not always populate during form downloads.
• Connect publish area in wizard not showing users/groups for permission assignment. This has been resolved and permissions can be set during initial publishing of projects.
• Inconsistent messages presented during database schema checks and upgrades. Messages displayed to the user during database schema checks and upgrades were inconsistent and in some cases, not helpful. This has been resolved.
• Failure to login to Trimble Connect because of restrictive proxy or firewall rules. For proper operation, Trimble Positions Desktop must be able to connect to the various Connect API URLs. In restrictive IT environments, this may require whitelisting at the proxy server or firewall level. In some cases, there were further problems as Trimble Positions Desktop will try to query the other, regional Connect servers (Europe, Asia) and failures in reaching either of these would result in a general failure. This has been adjusted to at least allow continued operation with the primary region (e.g., North America) even if the other regions cannot be reached because of network restrictions.
• Features without Z coordinates cannot be stored. Due to issues in other parts of the workflow, it was possible that forms had missing Z values in their 3D geometries. These forms would cause failures in the download into Trimble Positions Desktop. Additional logging has been added to allow information to be provided to Trimble MGIS Support for assistance in restoring older versions of the forms prior to the removal of the Z values.
• NTRIP source table display is not usable for large networks. When connecting to an NTRIP caster with a source table containing a large number of entries (e.g., for single-base networks), the long list is hard to use. If the mount points contain a latitude and longitude, they are now sorted by proximity to the current map center.

Advanced Configuration

In certain deployment scenarios, customers may need to manually configure the database connection. A configuration application can be downloaded here. Unzip the files and run it from there - no installation is required.