TerraFlex add-in for ArcMap v4.04
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.
Note: Version 4.04 is a minor update to version 4.02 which was originally released in October, 2019, and for which the text below applies. The only changes in 4.04 are improved logging and error handling as it pertains to the handling of migrations from InSphere to Connect. In addition, compatibility with older versions of ArcGIS Desktop (10.2.x, 10.3.x) has been restored.
New Features & Improvements
- 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).
- Error when trying to publish a TerraFlex project when the name ends with a space or a period. The add-in would be unable to publish a project if the project name ended with a space or a period. This has been resolved to trim trailing spaces and to validate that the name does not end in a period prior to saving.
- Errors when trying to access NTRIP source table from add-in. When creating a field configuration, the wizard will try to access the NTRIP sourcetable 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 sourcetable.
- Problems with form metadata updates made to InSphere after download. In some cases, users would get an error message after downloading indicating that “objectid values could not be updated.” This may have resulted in duplicate features being created locally if the same set of forms was downloaded again. This has been resolved.
- 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.