-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input as cartesians? #1
Comments
Julian, Yes, you are correct. Positions should be valid cartesian coordinates. In full: Inputs identified as tuples (lists) of n real numbers should exist in a euclidean space of dimension n. If you are using lat/lon, you will need to convert to a cartesian coordinate system. Depending on the range of latitudes and longitudes inputs, and the desired accuracy, you will want to be cognisant of this conversion. If accuracy is not a concern, you can model the earth as a sphere: If you have large lat/lon ranges or you are using an ellipsoid model of the earth (like WGS-84), you will want to look into solutions that account for this. Does this answer your question?
|
Perfect, Scott. Thanks a lot. Cheers. |
Using the linked SO equations, the input positions would be composed of x and y (throwing away z)? |
Why would you throw away z? |
The positions are arrays of two doubles but there are three axes in the SO answer. I don't understand how to coerce the SO answer into the required input positions. |
Thanks! Much appreciated |
Hi,
just to make sure, I assume TrilaterationFunction expects the position argument to be in cartesian coordinates, not in lat/lon or anything else?
Cheers,
Julian
The text was updated successfully, but these errors were encountered: