Skip to content

Adding NED coordinate system#71

Open
jleny wants to merge 4 commits into
JuliaGeo:mainfrom
jleny:master
Open

Adding NED coordinate system#71
jleny wants to merge 4 commits into
JuliaGeo:mainfrom
jleny:master

Conversation

@jleny

@jleny jleny commented Mar 27, 2021

Copy link
Copy Markdown

As discussed in issue #69: adds NEDfromENU / ENUfromNED transformations and the other transformations by composition.

jleny added 4 commits March 19, 2021 14:13
This adds the type of NED coordinates (standard for navigation and aerospace applications), transformations to and from ENU, and other transformations by composition through ENU
Added also a few tests and some cosmetic changes
@ajkeith ajkeith mentioned this pull request Mar 28, 2021
@RomeoV

RomeoV commented Aug 1, 2023

Copy link
Copy Markdown

Just want to say thanks for providing this. It's a handy reference for define my own conversion.

@asinghvi17 asinghvi17 requested a review from anowacki July 28, 2025 04:01

@anowacki anowacki left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All looks good bar a couple of textual things (ENU{T} in and '…extrema care must be taken…' in README.md). Consider reverting the new whitespace inserted in src/transformations.jl.

Comment thread README.md
##### `ENU{T}` - east-north-up

The `ENU` type is a local Cartesian coordinate that encodes a point's distance
The `ENU` type stores local Cartesian coordinates that encode a point's distance

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the old text is fine. Whether a coordinate is a single encoding of position or only one of the numbers which encodes position is an age-old debate.

Comment thread README.md
extreme care must be taken to choose an appropriate zone for the `UTM` methods.
(In the future, we implement the exact UTM transformation as a fallback —
contributions welcome!)
extreme care must be taken to choose an appropriate zone for the `UTM` methods

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original text is correct—the proposed change is typographically not.

Comment thread src/transformations.jl
"""
ECEFfromUTM(zone, isnorth, datum) = ECEFfromLLA(datum) ∘ LLAfromUTM(zone, isnorth, datum)


Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to introduce extra whitespace in an unrelated PR.

@anowacki

Copy link
Copy Markdown
Contributor

Thank you @jleny for your contribution! Your approach of composed transformations makes sense to me. Overall it looks very good.

Similarly to Claire, I 'do not love' the proliferation of conversions of things trivially computable from ENU by the user, but I accept that NED is much more common in some fields so I think it makes sense. I think I would be less encouraging for future PRs that add one or more of NWU, WSU, SEU, WND, SWD and ESD!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants