Present list of base coordinates during AP Config

[amlago]

Trying to improve and simplify the entry of base coordinates, I pass the following for your consideration:

1. When obtaining base coordinates with survey in, you could add the height of the rod and the difference in the phase center and save the coordinates of the mark in a file on the SD.
   The corrections are sent from the coordinates of the phase center but we save the coordinates of the mark for future use. (It would be necessary to subtract from the height of the antenna the height of the pole and the difference in the center of phase)
2. The next day, I park on the mark and I would like to access the list of saved stations, by means of, for example, Wi-Fi configuration.
   I indicate which point I want to use as a base and of course the height of the pole and the difference in the phase center will be indicated, in order to determine the correct height of the antenna.
3. The list could be seen on the Base page in the wifi configuration.
4. If I want to manually enter known base coordinates, I will do it as usual.

I leave you my ideas.
Cheers

[amlago]

To access the list of base points, a button would have to be added that allows the list to be displayed, as is done with the nmea messages, etc.

[amlago]

I would love for this crazy idea to be possible.

[amlago]

To simplify the programming a fixed amount of base points could be saved, for example 5 or 10 as fixed message data nmea is saved. As there is little data, it would not be necessary to save a points file on the sd. I would like you to give your ideas that are always very successful.

[amlago]

Base points can be identified as Base1, Base 2, etc or by using the date and time as a name.

[tonycanike]

This is a fine idea; we've discussed this in the past in some of the long and intertwined conversations on various issues.

I am not opposed to this, it would help me, especially if the file was in a CSV .txt format similar to that input and output from survey data controllers and desktop survey packages (I use Carlson SurvPC on my data collector and Carlson Survey on my desktop.)

I think there was a conversation that resulted in we should put the coordinates of the base in a profile settings file, which I am doing, but it is getting tedious to edit the profile settings files. So having a CSV .txt file with a handful of mark coordinates would be very helpful.

On another note, I'm having some success in using my data collector (with SurvPC) to set the base coordinates of the Facet. But that's another story.

Though in this sentence, I think you meant " subtract the height of the rod and the difference in the phase center" to calculate the coordinates of the mark.

1. When obtaining base coordinates with survey in, you could add the height of the rod and the difference in the phase center and save the coordinates of the mark in a file on the SD.

[amlago]

We agree on everything.

1. I said a while ago that using profiles to load different base coordinates was not useful for me.
2. If you could save the data to a txt or csv file that would be great. I am content at the moment with saving a few base points in any format or in the most practical way for programming.
3. Regarding the height of the mark you are right.
   mark height = antenna ellipsoidal height - pole height - phase center difference

I apologize and remind you that I communicate through Google translator.
If I do a reverse translation back to Spanish, it is still understood, I am not sure what you receive.
We will continue exchanging ideas. Thanks for sharing ideas.

[amlago]

In addition, if fixed base coordinates are entered manually, we should add a button to add the coordinates to the list of base points.
So the procedure would be:

1. If the base is obtained with survey in , the coordinates are automatically added to the list of base points
2. If you add a fixed base point manually, touch the new button and add it to the list.

I keep dreaming....

[nseidle]

Ok, so

• The RTK device needs to store a list of coordinates in a separate file 'StationCoordinates.csv' or similar to SD and LittleFS
• We will need StationCoordinates-Geodetic.csv and StationCoordinates-ECEF.csv
• The list of coordinates needs to be presented any time the user might be entering coordinates. The user should be able to select a group of coordinates to fill in the various boxes.
• The list needs to be editable, but perhaps not at the time the user is selecting coordinates.
• The user should be able to copy the current ECEF or Geodetic data to the list of coordinates

Do we need to store a unique pole length and ARP for each StationCoordinate-Geodetic.csv entry?

[nseidle]

Here's a bad markup, but hopefully it helps. Is this kind of what you are looking for?

The 'Copy Coordinates To List' would add a record to the list of station coordinates. The 'Load' button would copy the selected record to the ECEF boxes. The Delete button would remove a record from the list.

If a nickname matched a record already in the list, it would be overwritten.

[amlago]

What is presented is a very beginning of a solution to what has been proposed. Excellent. The idea of ​​being able to add a nickname is very good.

1. For Ecef coordinates I think it would be enough, since it would be used with really fixed bases.

2. For geodesics, the idea is to save the coordinates of the mark so that the height to be saved must be obtained by subtracting the height of the pole and ARP.
   mark height = antenna ellipsoidal height - pole height - phase center difference
   The height of the antenna is not saved, but the height of the mark.
   I don't think it's necessary to save stick height and ARP.

3. When I go to the field another day, I choose the base I need in Geodesics by one of the authorized methods and enter the new height of the pole and ARP as it is already being done.
   Method 1 Manual entry
   Method 2 Use current coordinates with the button
   Method 3 The list of coordinates is displayed

My idea is that this method 3 is another base coordinate entry method in addition to the existing ones and what has already been programmed to follow like this or similar.
In other words, the button to use current coordinates is very useful in the field.

You should be able to check option a) use current coordinates and use the button or option b) choose from the list and use this new thing you have programmed.

Keep in touch.
Cheers

[tonycanike]

This looks like it's going to be very useful! Very awesome!

I agree with @amlago 's comments. He described the situation very well.

No need to save the instrument height or ARP-APC offset, the mark Height Above Ellipsoid (little h) is want we want to in the CSV file.

When saving LLh, the instrument height and ARP-APC offset will be subtracted from the HAE (h) of the APC and saved to the CSV file.

When recalling from the LLh CSV file, the instrument height and ARP-APC offset will be added to the h of the mark from the CSV file to determine the h of the APC.

In all instances h is Height Above Ellipsoid.

I believe all I wrote above to be what @amlago said but in dif

[tonycanike]

Some thoughts about Height Above Ellipsoid here. This is basic info to some (but not me) so apologies if I'm stating the obvious.

---

In some NMEA strings the ZED applies its own crude built-in geoid model and gives a rough orthometric elevation (capital H) in the string. We don't want this rough orthometric elevation! We want to save HAE (lower case h). Fortunately the NMEA string also contains the crude geoid height (N) it applied. Thus the N can be backed out to recover HAE of the APC.

There are different geoid models used by different users for different purposes in different countries. The most useful data to save is the HAE (h) and let each user apply the geoid they need elsewhere.

So depending on where the firmware determines the ZED coordinates, it might be necessary to

1. add crude geoid height (N)
2. subtract ARP-APC offset
3. subtract instrument height (rod length)

to get the h to save to the CSV file.

---

The sign of the geoid height N can be confusing.

H ~= h - N
h ~= H + N

N is negative in the 48 US states.
H is greater than h in the 48 US states.

That is, in most (all?) geoid models, the geoid surface is below the ellipsoid surface in the 48 US states. (Some might say that the ellipsoid is above 'sea level'.) Things are different in Alaska and many other parts of the world.

https://www.researchgate.net/profile/Richard-Snay/publication/273133676/figure/download/fig1/AS:294934641954819@1447329306491/Relationship-between-orthometric-height-ellipsoid-height-and-geoid-height.png