Customised vertical datum

[manuel.1633]

Hi,

I am a regular user of reach View 3, I have the app version 7.14.

I have a query / request, I have not managed to load a geoid model of my own, for example, in Spain there is the official geoid EGM08_Rednap (Index of /geoide), this is provided in different formats supported by Topcon, Leica, Trimble, ArcGIS, etc.

I have two questions:

1. When using a Vertical Datum different from ellipsoidal heights the program does not save or at least does not export in CSV the ellipsoidal heights, it only exports orthometric heights referred to the shift geoid model. Is it possible to export in these cases the two heights? This would be useful because if you need to convert those heights to another orthometric system or to ellipsoidal heights in post-processing, having the ellipsoidal height available, it is easier to calculate it.

2. Is it possible to load a geoid model of your own that is downloaded in the device memory and the ReachView 3 app acquires it as a geoid model to be used in the following surveys?

Thank you

[svetlana.nikolenko]

Hi Manuel,

EGM08_REDNAP geoid is supported in ReachView 3. It’s available under the Alicante height vertical datum.

@manuel.1633

When using a Vertical Datum different from ellipsoidal heights the program does not save or at least does not export in CSV the ellipsoidal heights, it only exports orthometric heights referred to the shift geoid model. Is it possible to export in these cases the two heights?

Actually, there are both geographic and local coordinates in CSV export. There is a separate “Ellipsoidal height” column. Is it empty for your survey projects?

@manuel.1633

Is it possible to load a geoid model of your own that is downloaded in the device memory and the ReachView 3 app acquires it as a geoid model to be used in the following surveys?

It’s not possible, but we’re always ready to add needed geoids if they aren’t supported yet. But I suppose this question is no longer relevant if ReachView 3 supports EGM08_REDNAP? Or are there any other geoids missed? If so, feel free to share!

[manuel.1633]

Hello,
Thank you for your reply.

To the first question. Yes in the geographic coordinates I do have ellipsoidal heights, but are they the selected datum (for example in micaso ETRS89) or are they WGS84?

To the second question. The indicated geoid “EGM08_Rednap” is not in the list of available geoids in the ReachView 3 app. Could this one be included in the application (Index of /geoide)?

Thank you very much.
Best regards
Manuel Sanchez

[svetlana.nikolenko]

Hi Manuel,

@manuel.1633

To the first question. Yes in the geographic coordinates I do have ellipsoidal heights, but are they the selected datum (for example in micaso ETRS89) or are they WGS84?

They are in the selected datum.

@manuel.1633

To the second question. The indicated geoid “EGM08_Rednap” is not in the list of available geoids in the ReachView 3 app. Could this one be included in the application (Index of /geoide)?

The Alicante height vertical datum uses EGM08_REDNAP geoid. Have you tested that?

[manuel.1633]

The vertical datum available in ReachView 3 is the EGM08, the EGM08_Rednap is different, it is optimised by the National Geographic Institute of Spain, it is more precise and has differences with the first one. Could it be included in the application?

[svetlana.nikolenko]

Manuel,

What coordinates system do you use in ReachView 3?

For example, I type Spain in the search bar and choose the first one:

Then, I go to the Vertical datum tab and chose the Alicante height:

It asks to download the geoid model, which is named the same as in the source you shared previously:

Does it work the same way for you?

[manuel.1633]

Great thank you very much, problem solved, I hadn’t noticed the country search option.

Thank you very much.

[svetlana.nikolenko]

Great to hear that, Manuel!