Mapping and GIS Solutions Community

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg
------------------------------


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark. This is Elena survey manager from Fairfax. I'm trying easy solutions for our construccion guys and inspectors for simple tasks through my maps used in google maps.

 I rented recently a DA2 to make it work with google maps through Duncan Parnell too.

I have tried using TMM in a Galaxy S22 ultra and the app is not working with the antenna. When I move the phone, the point moves and it shows an unstable blue point.

I have tried also with an ipad and an iphone same way and the point looks stable, and follow the antenna no the ipad. I also installed in the ipad GPStest and it show around 15'-20' accuracy. So while google maps looks it works, this app (GPStest) doesn't show better accuracy than the ipad get by itself. However the same point in diferent moments, either with the ipad either with the iphone, looks in the same position always. 

My questions: 

• How could I check the real accuracy got in ios using google maps?
• How can I do the same in android?. I have tried to check every setting I found but I couldn't find a way to make it work.

Thanks in advance!

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Elena,

Apologies for the delay responding! A couple of points:

1. On iOS the position comes directly from a dedicated Bluetooth connection to the receiver. 
2. On iOS the operation system location services will never report an accuracy better than 5m, there is no way to see a better accuracy figure through any location services application. The actual position will be accurate from the receiver, however there is no way to confirm that after the fact.
3. On Android, Mock Locations is used to feed positions from the external receiver to location services. In Trimble Mobile Manager/Application Settings you need to make sure that the app is set to share locations with your regular applications. In order to achieve this you need to make sure that Developer Options are enabled within Android and that the Mock Location application is set to Trimble Mobile Manager.

I hope the above is clear. You can see this described on our Help portal here.

Regards,

Hi Mark. This is Elena survey manager from Fairfax. I'm trying easy solutions for our construccion guys and inspectors for simple tasks through my maps used in google maps.

 I rented recently a DA2 to make it work with google maps through Duncan Parnell too.

I have tried using TMM in a Galaxy S22 ultra and the app is not working with the antenna. When I move the phone, the point moves and it shows an unstable blue point.

I have tried also with an ipad and an iphone same way and the point looks stable, and follow the antenna no the ipad. I also installed in the ipad GPStest and it show around 15'-20' accuracy. So while google maps looks it works, this app (GPStest) doesn't show better accuracy than the ipad get by itself. However the same point in diferent moments, either with the ipad either with the iphone, looks in the same position always. 

My questions: 

• How could I check the real accuracy got in ios using google maps?
• How can I do the same in android?. I have tried to check every setting I found but I couldn't find a way to make it work.

Thanks in advance!

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.

Hi Mark,

Thank you very much for you answer.

I kept testing over an ipad, and even I can not confirm the accuracy, the points I'm checking over a map coming from a kml over google maps, works perfect every time I check, same position and stable point along 15 miles in 3 different areas. I assume is getting the correct position. I hope so!

I found yesterday the link with the android info. I moved it to developer mode and set the mock location to Trimble Mobile Manager. I checked this using and app, GPStest for android, and the app returned same accuracy that TMM. So I went over google maps and .... it wasn't working. Google maps wasn't moving with the anntena, it kept moving with the phone, even the GPStest report same accuracy than TMM, so this third app was using the anntena and no the movil gps.

I had the chance today to speak with someone from Trimble, I going to try to change the geoid from EGM96 (Global) to geoid18(Conus) by her recommendation. I couldn't yet because I don't have wifi were I'm right now, so we will try that tomorrow, and if it doesn't work, keep looking. Any idea of the issue it could be?

Thanks!

Hi Elena,

Apologies for the delay responding! A couple of points:

1. On iOS the position comes directly from a dedicated Bluetooth connection to the receiver. 
2. On iOS the operation system location services will never report an accuracy better than 5m, there is no way to see a better accuracy figure through any location services application. The actual position will be accurate from the receiver, however there is no way to confirm that after the fact.
3. On Android, Mock Locations is used to feed positions from the external receiver to location services. In Trimble Mobile Manager/Application Settings you need to make sure that the app is set to share locations with your regular applications. In order to achieve this you need to make sure that Developer Options are enabled within Android and that the Mock Location application is set to Trimble Mobile Manager.

I hope the above is clear. You can see this described on our Help portal here.

Regards,

Hi Mark. This is Elena survey manager from Fairfax. I'm trying easy solutions for our construccion guys and inspectors for simple tasks through my maps used in google maps.

 I rented recently a DA2 to make it work with google maps through Duncan Parnell too.

I have tried using TMM in a Galaxy S22 ultra and the app is not working with the antenna. When I move the phone, the point moves and it shows an unstable blue point.

I have tried also with an ipad and an iphone same way and the point looks stable, and follow the antenna no the ipad. I also installed in the ipad GPStest and it show around 15'-20' accuracy. So while google maps looks it works, this app (GPStest) doesn't show better accuracy than the ipad get by itself. However the same point in diferent moments, either with the ipad either with the iphone, looks in the same position always. 

My questions: 

• How could I check the real accuracy got in ios using google maps?
• How can I do the same in android?. I have tried to check every setting I found but I couldn't find a way to make it work.

Thanks in advance!

Hi Mark, I read through this and I'm a bit confused by the response. .  

It seems from  Joaquin's testing that the position was not being updated at all on iOS from the DA2.  See #5. From that remark it sounds like location services was not receiving an updated position from the DA2. 

I'd be curious to hear the results if they shot over some control points.  This would be a true baseline for better understanding what is happening. 

​

------------------------------
Jacob Wittenberg


Original Message:
Sent: 02-08-2022 12:32
From: Mark Kellaway
Subject: Using Catalyst with a web App on iOS platform

Hi Joaquin,

Thank you for the detailed message. The behaviour you are seeing is not a limitation of DA2, but is a limitation of iOS itself, which will not report accuracies as provided by the connected receiver, and is normally limited to ~5m. There is no way around this, so any app that requires knowledge of the actual position accuracy will need to utilise an API to get the position directly from the receiver or from TMM. We expose a Web socket on TMM and this would be the recommended path forward if your app can support it. Note that the position provided to iOS location services by the DA2 is accurate (see notes below), it's simply that iOS does not report that accuracy.
Some notes also:

• On iOS the position in location services comes directly from the receiver. If you have TMM connected it will be a corrected position.
• Because the position comes direct from the receiver location services will not benefit from transformations or geoids (orthometric height) applied by TMM.