Mapping and GIS Solutions Community

 View Only
Back to discussions
Expand all | Collapse all

No Orthometric (MSL) values in TMM

  • 1.  No Orthometric (MSL) values in TMM

    Posted 01-10-2023 10:55
    I am having an issue with detecting MSL values in TMM, with the intention of capturing elevations using collector and fieldmaps. I have attempted to configure TMM, but to no avail.
    Above is the config settings being used. I am located in the Caribbean and have also tried using GEOID18 as well for the id.

    Below is a picture of what is being shown on the status page 
    Hardware being used:
    Samsung Galaxy Tab and a DA1


    ------------------------------
    IT WASA
    ------------------------------


  • 2.  RE: No Orthometric (MSL) values in TMM

    Posted 01-10-2023 12:19
    Thanks for posting this @IT WASA. We'll take a further look.​

    ------------------------------
    Matthew Morris
    ------------------------------

    Original Message


  • 3.  RE: No Orthometric (MSL) values in TMM

    Posted 01-10-2023 12:51
    @IT WASA Can you confirm what version of TMM you are using?​

    ------------------------------
    Matthew Morris
    ------------------------------

    Original Message


  • 4.  RE: No Orthometric (MSL) values in TMM

    Posted 01-13-2023 08:36
    We are using TMM 3.0.2

    ------------------------------
    IT WASA
    ------------------------------

    Original Message


  • 5.  RE: No Orthometric (MSL) values in TMM

    Posted 01-20-2023 08:11
    @Matthew Morris any updates on this issue.. re TMM 3.0.2
    ​​

    ------------------------------
    IT WASA
    ------------------------------

    Original Message


  • 6.  RE: No Orthometric (MSL) values in TMM

    Posted 01-21-2023 01:30
    Hi. We've identified a bug in TMM with how datums are selected in your region and this will get fixed in the next release.

    ------------------------------
    Matthew Morris
    ------------------------------

    Original Message


  • 7.  RE: No Orthometric (MSL) values in TMM

    Posted 02-08-2023 10:51
    Hi @IT WASA. We released a new version of TMM in which we expect this issue to be resolved. Are you able to test with v3.0.6.1379 and let us know if it's fixed? Thanks.​

    ------------------------------
    Matthew Morris
    ------------------------------

    Original Message


  • 8.  RE: No Orthometric (MSL) values in TMM

    Posted 02-22-2023 12:01

    The update was installed now I am seeing the orthometric heigh but the accuracy seems to be off when data is captured. any assistance would be greatly appreciated.



    ------------------------------
    IT WASA
    ------------------------------

    Original Message


  • 9.  RE: No Orthometric (MSL) values in TMM

    Posted 02-24-2023 01:44

    Hi. Can you provide additional information (and TMM logs) indicating what you expect the orthometric height value to be and what you are getting?



    ------------------------------
    Matthew Morris
    ------------------------------

    Original Message


  • 10.  RE: No Orthometric (MSL) values in TMM

    Posted 03-29-2023 08:05

    Good day sorry about the delay we are working on some subscription issues with our local provider. In the interim can you take a look at another issue we are having with the accuracy of the unit? When we try to compare the accuracy against our BRASS points we are finding a large disparity with the Northings position.  

    Date

    Latitude

    Longitude

    Trimble catalyst

    Eastings

    Northings

    Brass points

    Eastings

    Northings

    Transverse St.#

    GLOBAL ID

    WASA Device Name

    Device Name

    10/03/23

    10.65227658

    -61.41894370

    672824.9217

    1177799.755

    672825.481

    1177795.764

    23-0041

    {96154968-AFC2-47E4-9ABD-2EBB270D1674}

    GPS Collection

    Catalyst 5748100065 H

    10/03/23

    10.65237536

    -61.41844628

    672770.5562

    1177788.552

    672771.034

    1177784.203

    23-0042

    {B55A1567-F7A6-4885-B48E-FDFCDAB27A5D}

    GPS Collection

    Catalyst 5748100065 H

    02/03/23

    10.65225135

    -61.41892769

    672772.7641

    1177785.070

    672825.481

    1177795.764

    230041

    {33E7FAF0-B88E-4456-ACC3-AB49B2B503CF}

    GPS Collection

    Catalyst 5734100106 H

    02/03/23

    10.65235558

    -61.41844954

    672825.0178

    1177796.865

    672771.034

    1177784.203

    23-0042

    {2D664A95-3EF8-4592-9017-FEF45019E078}

    GPS Collection

    Catalyst 5734100106 H

    01/03/23

    10.65235490920

    -61.41842109

    672828.1306

    1177796.8067

    672771.034

    1177784.203

    23-0042

    {ABC51D6E-C3ED-4811-B00F-BEE5F2953AE1}

    GPS Collection

    Catalyst 5748100065 H

    01/03/23

    10.65224468490

    -61.41892284

    672773.2973

    1177784.3351

    672825.481

    1177795.764

    230041

    {07DDC6CD-9B04-42C7-95FD-B1E6BD03A751}

    GPS Collection

    Catalyst 5748100065 H


    ------------------------------
    IT WASA
    ------------------------------

    Original Message


  • 11.  RE: No Orthometric (MSL) values in TMM

    Posted 03-30-2023 08:03

    "Offsets" in data as you've observed are typically the result of differences in datum.  Please confirm the datum of the brass cap and the datum of the collected data.  Without knowing your method of collection with Catalyst, it's difficult to say what the correct configuration should be.

    However, start in TMM and verify the "GNSS Output" datum selection. The default is "Auto" which will choose the most appropriate local datum for your geography.  Choosing "Select from list" will allow you to specify the output datum - allowing you explicitly match the datum of your brass caps.



    ------------------------------
    Dan Colbert
    ------------------------------

    Original Message