Local Cartesian (NED) to Geodetic (Lat,Lon,Alt) Conversion - Max Distance from Reference Point

Looking at this:

[lat,lon,h] = ned2geodetic(xNorth,yEast,zDown,lat0,lon0,h0,spheroid))

The obvious question is by how much the current location on local Cartesian NED (xNorth,yEast,zDown) can be far away from the reference point (lat0,lon0,h0)?

For example if the reference point is in Australia and the current location is in the US, does those "mathematical tricks" still will be valid?

I assume that there is an intermediate step of-

Local Cartesian NED to geocentric ECEF: https://www.mathworks.com/help/map/ref/ned2ecef.html

Since they also using Geodetic reference point - probably first converting the Geodetic reference point to ECEF, and then there is the questioned "mathematical tricks" to "add" current local Cartesian NED to that reference point (already represented in ECEF) so the current local Cartesian NED will be in ECEF - Thus the "mathematical tricks" are some sort of Cartesian/Vectorial manipulations, I suspect how long they holding in the context of maps, geodesy etc?

Regarding converting Geodetic reference point into ECEF in the intermediate step mentioned above, and in the final step converting back current Cartesian point (already in ECEF) to Geodetic, they use:

Transform geocentric (ECEF) to geodetic coordinates: https://www.mathworks.com/help/map/ref/ecef2geodetic.html

Assuming this is pretty much straight forward formulas with known limitations (Characteristics of different methods to convert ECEF to LLA) So I don't see how they interfere here...

• I was working with both formulas (ecef2geodetic) then (ecef2enu) for different coordinates around the world. They did the job. But I still cannot get your question! – Moh Jun 16 at 13:35
{"ft_lang_label":"__label__en","ft_lang_prob":0.8425575,"math_prob":0.9135785,"size":1546,"snap":"2019-43-2019-47","text_gpt3_token_len":371,"char_repetition_ratio":0.12775616,"word_repetition_ratio":0.0,"special_character_ratio":0.20051746,"punctuation_ratio":0.14335664,"nsfw_num_words":0,"has_unicode_error":false,"math_prob_llama3":0.9682555,"pos_list":[0],"im_url_duplicate_count":[null],"WARC_HEADER":"{\"WARC-Type\":\"response\",\"WARC-Date\":\"2019-10-20T12:43:43Z\",\"WARC-Record-ID\":\"<urn:uuid:5d84c52e-4aaf-48a7-ab90-41e0f1d15aad>\",\"Content-Length\":\"140351\",\"Content-Type\":\"application/http; msgtype=response\",\"WARC-Warcinfo-ID\":\"<urn:uuid:ddab1ab8-76ce-4eb3-9e80-fd5772dd9e0d>\",\"WARC-Concurrent-To\":\"<urn:uuid:adede897-5eb4-4e0c-8ea0-dc2f197ffe72>\",\"WARC-IP-Address\":\"151.101.193.69\",\"WARC-Target-URI\":\"https://gis.stackexchange.com/questions/274739/local-cartesian-ned-to-geodetic-lat-lon-alt-conversion-max-distance-from-r\",\"WARC-Payload-Digest\":\"sha1:ITJNUFCQW3XSE3SUGVPGYDLEQER5CWR5\",\"WARC-Block-Digest\":\"sha1:H3JYZQNTKRPNFUCFUMI2Q5YLU4CNWKZO\",\"WARC-Identified-Payload-Type\":\"text/html\",\"warc_filename\":\"/cc_download/warc_2019/CC-MAIN-2019-43/CC-MAIN-2019-43_segments_1570986707990.49_warc_CC-MAIN-20191020105426-20191020132926-00370.warc.gz\"}"}