-
Notifications
You must be signed in to change notification settings - Fork 46
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
Need ability to convert 3D coordinates #150
Comments
Yeah, we should definitely support 3-4D transforms, it's just a question of API design. |
CC #121 |
I agree but I don't have time, so (and I mean this in the most constructive way) if you want it, you'll almost certainly have to write it. |
I have a fork that I adapted for 3D coordinate conversion, specifically, because I needed to reproject to ECEF @whitefractal . Here is the proj.rs fork. Here is an example how I use it. In my adaptation, I did the minimum necessary for my use case. However, because the current Coord is 2D only, I'm not sure if adding additional members (eg But if you don't see big hurdles in the API, I'll implement the 3D across proj and send a PR. |
Proj::convert
assumes 2D coordinates, and passesz: 0.0
intoproj_sys
(which handles 3D just fine).This is insufficient for conversions to/from (e.g.) ECEF coordinates, where the z coordinate is critical even for locations on the ground.
Then need to access the private
c_proj
makes it impossible to define a trait with a minimally-modifiedconvert
method which takes a 3D point, passes all three values in/out of proj_sys, and returns a 3D point.Some provision for 3D coords within this crate would be extremely helpful please :-)
The text was updated successfully, but these errors were encountered: