As of Friday (April 11) afternoon, all issues should be resolved.
As of Friday (April 11) afternoon, all issues should be resolved.
Earlier today we became aware of a problem downloading CORS base station data from the NGS/NOAA servers through Trimble Positions Desktop add-in. At the beginning of post processing, you will see error messages for the failed downloads. We are currently investigating the issue but it appears to affect Pathfinder Office and Field Inspector in addition to Trimble Positions. One workaround would be to note the URLs for the attempted downloads and then download the files manually through a browser. You can then setup a new post processing profile for those specific files.
We’ll share additional information as we have it.
UPDATE: As of Friday (April 11) afternoon, all issues should be resolved.
By now you’ve probably seen the announcements from Esri about the availability of ArcGIS 10.2.1. Although the “major.minor.revision” numbering has been used for a few years in some of the mobile and runtime products, it’s somewhat new to the core ArcGIS releases. In the past, it’s usually been service packs between the “minor” releases of Desktop, Server, and Engine (even though at the DLL level, the service pack number was typically reflected in the “revision” position of the version string). Moving forward, these intermediate releases will likely follow this new convention. One big advantage is that they come with a full installer so that you can install the latest version directly and not have to do the main release and then apply the service pack. You can also upgrade an installation in-place.
Given these new options, there are a few different paths you can take to get to 10.2.1. Although the Trimble Positions Desktop add-in is supported with ArcGIS for Desktop 10.2.1, there are a few things to consider depending on your upgrade path. Here are several of the most common scenarios and the steps you will need to take to get everything working:
Hope that helps.
The Trimble Positions Development Team is pleased to announce the release of Trimble Positions 10.2.0.1 for all products. As the name implies, this release supports ArcGIS for Desktop 10.2, ArcGIS for Windows Mobile 10.2, and ArcPad 10.2, in addition to supporting Trimble’s latest GNSS handheld, the Geo 7 Series.
This release addresses usability, bug fixes, and a handful of noteworthy new features:
The release notes contain the full listing of new functionality and bug fixes and should be consulted for further detail. Check back here in the next couple of weeks for demonstration videos highlighting some of the new functionality in the context of different workflows.
Before we go, an important note: This release includes an upgrade to the schema of the Trimble Positions Desktop database. As a reminder, this is the Jet/MDB or ODBC data source that you configured during installation using the Trimble Positions Desktop Configuration application available in the Start Menu. After installing Trimble Positions Desktop add-in 10.2.0.1, run the Configuration application, and click the ‘Test current configuration‘ link. This will alert you that the schema needs to be upgraded and that all existing data (projects, processing profiles, field configurations, etc.) will be preserved. Click the ‘Yes‘ button, wait a few seconds, and then re-click the ‘Test current configuration‘ link to verify that the schema was upgraded.
In August of this year, we released the long-awaited Positions ArcPad extension for Windows. The 10.0.0.2 installation package includes installers for both Windows and Windows Mobile. For those of you who have installed the Positions ArcPad extension on Windows, you likely have come across some errors either during installation or when trying to run ArcPad. Unfortunately, the installer for Windows is missing a required Microsoft Visual C++ runtime redistributable.
To rectify this:
That should resolve the problem. We’ve heard reports of it working without steps 3 and 5 but included them here regardless.
Due to the US government shutdown all NGS/CORS services are unavailable (UFCORS, CORS ftp). This means that data cannot be post-processed against CORS base stations or services unless the data has previously been downloaded. If this affects you, please contact your Trimble dealer as they may be able to suggest other sources of base station data for your area.
The goal is to setup a shared SQL Server database called TPDatabase1 on SQLServer1 that will allow User1 on PC1 and User2 on PC2 to share their Trimble Positions projects, post-processing profiles, and field configurations. This will be done by using Windows Authentication. Let’s assume that User1 and User2 are Windows domain users and at least User1 is a member of the administrators group for the SQL Server installation on SQLServer1. Also, User1 has SQL Server Management Studio (SSMS) installed on either PC1 or SQLServer1 so that he/she can connect to SQLServer1. Finally, PC1 and PC2 have installed the SQL Server Native Client (at or above the SQL Server version), Esri ArcGIS for Desktop, and the Trimble Positions Desktop (TPD) add-in.
We’re excited to announce that the Trimble Positions ArcPad extension now includes support for Esri ArcPad on Windows. This provides GIS customers looking to couple ArcPad with powerful tablet PCs, such as the Trimble Yuma 2, with the ability to post-process and analyze field data collected on a tablet. Available for download now, the installation package for the Trimble Positions ArcPad extension v10.0.0.2 includes installers for both Windows and Windows Mobile. The Windows version has the same language support that the Windows Mobile version does.
Look for the new “Trimble Positions Software Suite – August 2013 (current)” section of the Technical Support – Downloads area at www.trimble.com/positions. Note that all version numbers remain the same as the previous release as there have been no other changes in the software; all other installation packages are identical to the previous release. Esri pre-requisites and version support also remain the same.
As you’re probably aware, Esri recently released ArcGIS 10.2 (Server, Desktop, Engine) and ArcPad 10.2, with ArcGIS for Windows Mobile 10.2 to follow. Trimble remains committed to the Esri technology stack and intends to support these new versions in a future release of Trimble Positions.
Since the release of Trimble Positions, we have seen an increasing number of customers looking at the “server” workflow in ArcGIS for Windows Mobile. In this workflow, the mobile device (running ArcGIS for Windows Mobile + Trimble Positions Mobile extension) synchronizes data changes directly to the enterprise geodatabase through a mobile service on ArcGIS for Server. All feature and feature attachment data synchronizes through the service. The mobile service will synchronize the feature (shape and attributes) and each attachment as separate transactions to minimize the packet size as much as possible. As a reminder, the binary GNSS “session” data that gets recorded in the background during data collection, as required for post processing, is stored as an attachment to a feature in the TrimbleSessions layer. This data accumulates at the rate of roughly 1MB per hour and so a typical data collection work session might yield an attachment of 2~3MB. This is likely among the larger attachment sizes a customer may deal with in typical workflows.
Due mainly to the very restrictive application memory space for Windows Mobile applications (32MB; into which both Esri’s application and our extension have to fit), and the fact that Esri has to support different types of secured mobile services (token, web auth, Windows auth, etc.), synchronizing large attachments (say >= 4MB) may be problematic in certain scenarios. Logic in the existing ArcGIS for Windows Mobile 10.1.1 application may not notify the user that one or more attachments has failed to synchronize and may also prevent any retries of failed attachment synchronizations. It’s not until the Trimble Positions office user gets failure messages when trying to “check for new sessions” that there is any indication of a problem. In such cases, a message about “no GNSS measurements” will be logged to the Trimble Positions Desktop add-in log file. This indicates that a feature in the TrimbleSessions feature class is missing the binary attachment and thus it cannot be imported into the Trimble Positions office database. In these scenarios, there is no data loss as the unsynchronized session attachments will continue to sit in the device’s mobile cache folder.
We are working closely with Esri on these limitations and Esri is improving both the underlying attachment synchronization logic and error notification within the 10.2 release to accommodate larger attachments. For customers that may encounter problems now, there are several workarounds available:
Unfortunately, workarounds are never perfect and even the work that Esri is doing for 10.2 will have its limits. It is always recommended that adequate testing be performed in an environment as close as possible to what is expected in production. This would include network topology (DMZ, WiFi/cellular, LAN/WAN), software versions, mobile hardware, attachment workflows (number and size), synchronization workflows, etc.
For the Trimble Positions Mobile extension workflow, it is best to keep session attachments to a reasonable size (1~3MB) by closing the project (or application) in between work activities (e.g., when taking a break or meal). This will close the session and store it as an attachment. If the user simply hits the power button on the device (suspend), the session will be resumed upon start-up and will continue to grow in size. Disconnecting from the GNSS receiver does not stop the session. Advanced users can also use the ‘GNSS Sessions’ task to manually start and stop sessions.