IDEA
|
When you have Averaging turned on, and you edit an existing feature, if you tap Update Point, it asks if you would like to use the Target location (meaning a digitized location) or if you would like to Start Averaging (meaning use your GNSS location). This is good. However, when Averaging is not on, you edit an existing feature, if you just tap Update Point right there, Collector automatically assumes you want the Target Location and doesn't give you an option to use GNSS Location. You have to tap the little location arrow in the upper right to get it to move to your current location, and then you tap Update Point and then it automatically uses your GNSS location. This is not intuitive. I think it should be like it is when you're averaging where it asks which location you want to use.
... View more
08-15-2019
03:46 PM
|
0
|
0
|
403
|
POST
|
Thanks so much for the tip Fred! I was actually working with Ben on your issue, and he let me know about your solution too. I'm going to try that with my other customers, and I'll let everyone know if that fixes others too.
... View more
07-08-2019
07:20 AM
|
0
|
0
|
703
|
POST
|
The solution with the R2 is still to roll back to version 5.22, and I've found that I must do that with the Web UI. The Trimble Installation Manager does not seem to always roll back the firmware properly.
... View more
06-19-2019
02:07 PM
|
0
|
5
|
2597
|
POST
|
Rolling back the R2 to firmware 5.22 used to resolve this issue, but now that seems to not be working either. I have confirmed that the High-Accuracy NMEA option is installed and have turned all NMEA strings on in GNSS Status, but on Windows 10 tablets, I continue to get the same issue where tapping Switch in Collector just does nothing. Collector will not connect to the R2.
... View more
04-22-2019
10:25 AM
|
0
|
0
|
2597
|
BLOG
|
Thanks Johnathan. Appreciate the confirmation. Just FYI, the Trimble R1 and R2 are listed as supported on iOS in that link above for supported devices.
... View more
02-22-2019
09:30 AM
|
0
|
0
|
1244
|
BLOG
|
Hello Johnathan, Trying to use Trek2There on iOS with an R1 receiver. I have GNSS Status installed and set to output the required NMEA sentences. But when I go into the app and try to set the receiver, I can't turn on Discoverable and therefore, I can't choose the R1. Is there a workaround for this? Thanks, Alison
... View more
02-19-2019
09:01 AM
|
0
|
0
|
1244
|
POST
|
Hi Benjamin, On the 6000 series Geo's, to use it with ArcPad, you would either need to have the Trimble Positions extension or the Trimble GPScorrect extension for ArcPad installed on that device. If you don't have one of those extensions, then you would have to purchase a separate NMEA output option for that Geo so that it can talk to the software. I would get in touch with your Trimble dealer where you purchased the equipment and see if you have either the NMEA output or one of those extensions.
... View more
03-19-2018
01:57 PM
|
0
|
0
|
243
|
IDEA
|
I have a user who is using Survey123 to interview their clients and contacts, and they sometimes have repeats of these. They would like to be able to take a survey from the inbox and duplicate all the contact information to a new survey so that they don't have to fill it out again but also don't have to edit the old survey. The number of surveys for a specific contact is important to maintain.
... View more
05-24-2017
08:58 AM
|
9
|
1
|
2360
|
POST
|
Yes, exactly. So I have some data that was collected this morning that had the real-time purposely disconnected to see what would happen. For 3 or 4 minutes, Collector continued to report 1 inch accuracy and record that metadata in the metadata fields long after (like 2 minutes is long in this case ) GNSS Status was reporting much worse. However, on this test, it did eventually respond and report the proper estimates. Just seemed like it was slow to react or refresh. I wouldn't be too worried about this if it didn't continue to record incorrect data into the metadata. I will fully admit that I have not had time to do thorough enough testing to determine if the problem is really Collector or if, in fact, the bad data is coming from GNSS Status. I will try to come up with a better test plan and keep you updated, but if you'd like to see the data or any screenshots, let me know. Thanks, Alison
... View more
10-14-2016
01:12 PM
|
0
|
1
|
1030
|
POST
|
Thank you both for the feedback. The issue is that Collector continues to report 1-inch accuracy even when GNSS Status is reporting much worse due to the loss of real-time correction. So even if I have Collector set to only collect data at a certain level of accuracy, Collector just lets me keep going even though the real-time has been dropped and GNSS Status is reporting 10 feet. Worse yet, the metadata records whatever Collector is reporting, so I might end up with metadata showing 1 inch of accuracy when in fact it’s nowhere near that.
... View more
10-11-2016
02:10 PM
|
0
|
4
|
1030
|
POST
|
Using the latest Collector with an R2 CM Edition receiver. Seems to work great, but I'm concerned about the accuracy reporting. I've lost my connection to my base station a couple times which reduces the accuracy of this receiver from 1 cm to a couple of meters, but Collector does not give me any indication that there is a problem and just lets me continue collecting data. It continues to report that I am getting less than an inch of accuracy when that is not the case. Has anyone else seen this issue? I'm going to do more extensive testing to reproduce the issue before I submit a case, but I wanted to see if anyone else has seen this and resolved it already?
... View more
10-07-2016
10:50 AM
|
1
|
12
|
2552
|
POST
|
Hi Greg, Hope you're doing well! You might check out the GeoJobe admin tools if you haven't already. I'm not sure about this specific functionality. I'm pretty sure you can deal with the editing, but I'm not sure about the naming, but you will find tons of other awesome functionality in there. Give me a call if you have questions about it. Here's a link to their YouTube channel: GEO-Jobe - YouTube
... View more
10-07-2016
10:29 AM
|
0
|
0
|
383
|
POST
|
Hi Joel, Not sure why that would happen just from moving the license manager, but the release notes for Positions do address this error, and this fix might work for you? I’ve also found that just reinstalling Positions sometimes does the trick, and that might be easier. During the installation process, the Trimble Positions Desktop add-in installer attempts to modify the ArcMap.exe.config file in the C:\Program Files (x86)\ArcGIS\Desktop 10.1\bin folder. Depending on permissions, this can sometimes silently fail… manually edit the ArcMap.exe.config file (using a suitable text editor, for example, Microsoft® Notepad) to make the <! <supportedRuntime version="v4.0.30319"/> > Alison
... View more
11-09-2015
07:47 AM
|
0
|
0
|
1018
|
POST
|
Just FYI, you can remove the default ones from TerraSync using TerraSync Studio in the later versions of Pathfinder Office. Of course if you’re just using Trimble Positions, then you probably wouldn’t invest in Pathfinder Office for that one piece of functionality. Alison
... View more
11-03-2015
07:45 AM
|
0
|
0
|
1018
|
Title | Kudos | Posted |
---|---|---|
9 | 05-24-2017 08:58 AM | |
1 | 10-07-2016 10:50 AM | |
19 | 11-18-2014 08:35 AM | |
2 | 02-06-2014 12:56 PM |
Online Status |
Offline
|
Date Last Visited |
08-30-2021
12:40 PM
|