Display both HAE of APC and HAE of Mark in Base Geodetic Coordinate Configuration AP page

[tonycanike]

Subject of the issue

I entered this in response to @nseidle 's request in #327 . This is just one possible approach. I like this approach because there is no mystery as to what calculations the firmware is performing. The user can enter their data, see the results of the calculations, and confirm that the device is operating as they intend.

To be completely clear to the user and prevent confusion, the Base Geodetic Coordinate Configuration page should contain both the HAE_APC and HAE_Mark elevation fields. These two fields should dynamically recalculate as the user enters Antenna_Height and APC_Offset.

So the form will have the following six fields:
Lat (user entered, loaded from CSV, or pasted from ZED. required to be non-blank but could be zero!)
Long (user entered, loaded from CSV, or pasted from ZED, required to be non-blank but could be zero!)
HAE_APC (Height above ellipsoid of the Antenna Phase Center) (display only?)
Antenna_Height (user entered optional, default to zero)
APC_Offset (use entered, optional, default to zero)
HAE_Mark (user entered, loaded from CSV, or calculated. required to be non-blank but could be zero)

This is a simplified request related to #330

Expected behavior

HAE_APC is sent and retrieved from the ZED. It is never loaded or saved to the CSV file.

HAE_Mark is loaded or saved to the CSV file.

HAE_APC and HAE_Mark are equal if Antenna_Height and APC_Offset are both zero.

When user copies coordinates from the ZED, the HAE from the ZED is loaded into HAE_APC. Then APC_Offset and Antenna_Height are subtracted from the HAE_APC and displayed in the HAE_Mark field.

When user types into the HAE_APC field (if we allow this, do we need to?), the APC_Offset and Antenna_Height are subtracted from the HAE_APC and displayed in the HAE_Mark field.

When user types into the HAE_Mark field,the APC_Offset and Antenna_Height are added to HAE_Mark and the sum is loaded into the HAE_APC field.

When the user saves coordinates to the CSV file, the HAE_Mark field is saved.

When the user loads coordinates from the CSV file, the HAE_Mark field is loaded from the file. The APC_Offset and Antenna_Height are added to HAE_Mark and the sum is loaded into the HAE_APC field.

It's a toss-up which direction to calculate (HAE_Mark --> HAE_APC, or HAE_APC --> HAE_Mark) when the user updates the Antenna_Height and/or APC_Offset field.

I work in HAE_Mark coordinates so I'd say always go HAE_Mark --> HAE_APC. That is, if Antenna_Height or APC_Offset are updated, recalculate HAE_APC.

Serial Menu?

I'm not sure what to do on the serial menu.

[amlago]

Good summary.
I support what was raised by tonycanike.

"I work in HAE_Mark coordinates so I'd say always go HAE_Mark --> HAE_APC. That is, if Antenna_Height or APC_Offset are updated, recalculate HAE_APC."

[amlago]

One question: This topic has been added to the last RC?
It's just that I've been away from the discussions and I don't know what we agreed on.
It doesn't have a label so I'm assuming it doesn't.
This is a very important part of what was advanced in #327 .

[amlago]

Hello. I understand that on these dates time is scarce.
I tried the latest version 2.6 and the height correction for the base station save has not been added.
I would ask you, if possible, to consider what is requested in this topic so that the saving of base coordinates with the height of the mark is possible.
I have a job these days where what I requested would be very useful due to the high number of bases that I will use.
Thanks.

[nseidle]

WIP while I fix the common coordinates box.

[nseidle]

The current RC (Dec 30) has these boxes but we are not storing them within the commonly used coordinate list. Please let me know if we are headed in the right direction.

[amlago]

We are on the right track regarding the APC HaE presentation.
What I see is that it is not being dynamically updated when entering the rest of the data.

[amlago]

Now we can easily access the serial menu via bluetooth, so
In the serial menu it would be interesting to replicate this way of working and add a presentation of HAE APC

[amlago]

The HAE APC calculation that you present in the screenshot of your menu is correct.
That is the expected value.
We are making progress.

[amlago]

In principle, it is not necessary to save the HAE APC as this should be dynamically calculated from the data entered, each time the equipment is installed on a known point.
Either we know the base coordinates or we already have them saved in the list of base points.

[amlago]

Facet v2.7 01/06/23
I am testing the improvements in the latest version and I propose some variants to the input of base coordinates

1. Now we have a visualization of the HAE APC
2. The suggestion is that when we paste coordinates with the PASTE button, the APC height is pasted in the HAE APC box and not in the mark height box as it currently happens
3. The HAE Mark Height should then be calculated using the entered AH and ARP data.
   HAE Mark = HAE APC - AH-ARP

This is only when we paste data with the PASTE button.
For the other situations, everything is already working fine and the HAE APC is calculated dynamically as programmed.