So why does Emlid only take LAT<LONG and ellipsoid elevations in meters as manual input?
Am I correct on this? From what I see I am correct...
You are correct. Emlid only allows you to input in Lat/Long ellip as a manual input and this is from a geographic coordinate system.
Emlid will allow you in Survey to then choose a projected coordinate system when you collect your Control Points and will also allow you to have an orthometric elevation by using a download geoid undulation grid (12B, 18).
A geographic coordinate system mirrors our round world. When we print a map out on a flat peice of paper, if we used this information there would be distortion in this flat map. Think of your lines of longitude. The spacing between them at the equator is wide, as you get closer to the poles, it gets more narrow. Think how this would affect your flat printed map. So we use a projected coordiante system to print a flat map. These projections in our State Plane case are fo small areas (think states and even several projections for larger states). They use meters instead of degrees for distance and each State Plane projection can only be used in its own smaller area. These projections remove distortions and allow us to get accurate measurements. If you output a map in Agisoft in the geographic coordinate sytem NAD 83 (2011) , printed it and then took measurements, they would be off. Take the same data and output in a correct projected coordiante system (UTM, State Plane) you have removed distortion and now have much more accurate measurements.
GNSS equipment's raw output is in a geographic coordinate system. Currently it is WGS 84 (G2139). This is the geographic coordinate system our Emlids use when not receiving corrections.
State Plane and other projections are an Emlid software conversion/transformation.
When we receive corrections, we receive them in the geographic coordinate system of whatever the Base (Sender of corrections) is sending them in. (This works because even though WGS84(2139) is shifted by around 2 meters from NAD 83(2011), they would for our purposes equal each other if shifted over top of each other. They equal each other but are shifted.
When you use your RTN/RTK service in Nevada, they are sent in NAD 83 (2011).
If you setup on an NGS known point, and use the NAD83(2011) data to input into your Emlid Base as a manual entry, you are now sending out corrections to a Rover (Drone or another Emlid) in NAD 83 (2011).
If you use PPK and use data from an NGS CORS and use the NAD 83(2011) coordiantes from the CORS data sheet, you will have your PPK solution in NAD83(2011).
If you use PPK and use data from an NGS CORS and use the ITRF 2014 coordiantes from the CORS data sheet, you will have your PPK solution in ITRF 2014. This is useful if you want your corrections to be in WGS84 (G2139) since G2139 and ITRF 2014 equal each other.
Examples:
I place my Base on a known NGS point.
In my Emlid Base I place the Lat/Long, ellipsoid from the data sheet from the NAD 83(2011), I am now receiving corrections to my Rover (Drone or other Emlid) in NAD 83 (2011)
I place my Base on a known NGS point.
In my Emlid Base I place the Lat/Long, ellipsoid from the data sheet from the NAD 83(2011), I can choose a State Plane or NAD83(2011) UTM projection and am now receiving corrections to my Rover (Emlid) in the chosen projection AND can also get my elevations in orthometric using a geoid (12B, 18) since Emlid does have the geoid undulation tiff (grids) available to do the math (H=h-N). In this scenario I have to use the NAD 83(2011) geographic coordinates if I want to use a NAD 83(2011) projection, either State Plane or UTM. This only works in Survey.
You are setting up your Evo 2 RTK and log into your RTN/RTK service, this service is sending corrections in NAD 83 (2011), so your drone is receiving corrections in NAD 83 (2011).