Request: Make Field Maps compatible with GNSS receivers with tilt compensation

[KyleMcCormick]

In our experience GNSS receivers with tilt compensation more than double the efficiency of data collection.

Many (most?) of the more recent ones include tilt compensation, from the Trimble R780 and R12i receivers, the Hemisphere S631, the Emlid Reach RS3, all the way down to the $1300 SparkFun RTK Torch.

Currently we are using Microsurvey FieldGenius Android for data collection but some departments here at the City would like to use Field Maps. The only thing stopping us is the lack of tilt compensation compatibility.

Please bring this enhancement into active status.

I am sure many others would concur. If you do, add a request to the thread below.

[Debert]

Hi Kyle,

Curious what exactly you are referring to here, as I'm in the process of configuring Trimble receivers to Field Maps? I have successfully paired a few DA2s and next will be pairing a few R12i's.

Are you saying Field Maps doesn't recognize the tilt compensation (meaning the R12i needs to be level before storing points)?

If this is indeed what you are referring to, I would agree this is a valid enhancement request.

[KyleMcCormick]

Hi Debert.

My understanding is that field Maps will not recognize the tilt compensation of the R12i.

What is interesting is that the free app SW Maps does handle the tilt compensation of the Sparkfun RTK Torch.

Regards,

Kyle

[Jacbrod]

Hello,

It appears that many receivers now have tilt option as standard, such as the Leica Zeno.

Will ESRI integrate the transfer of these measurements into ESRI Fields Map, or should we consider other data capture applications ?

Regards

[Debert]

There are many receivers incorporating the tilt compensation- yes.

However, I think this is more of an Esri Field Maps issue as the Trimble R12i has tilt-compensation but Field Maps only recognizes the tilt-compensation on an Android device (not iOS).

Android is more prominent in other counties, so I believe the idea is to roll out those integrations first- but I could be wrong.