Skip to content
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

loc_height vs. loc_altitude #7

Open
rbair23 opened this issue Sep 4, 2018 · 1 comment
Open

loc_height vs. loc_altitude #7

rbair23 opened this issue Sep 4, 2018 · 1 comment

Comments

@rbair23
Copy link
Contributor

rbair23 commented Sep 4, 2018

"height" in ISO 6709 is pretty loose in its interpretation, while "altitude" is specific in the same way that "latitude" and "longitude" are specific. I think "altitude" is a better fit here.

In addition, we shouldn't require all three values if any one value is available. Many devices can give lat/lon but not altitude, or vice versa. If we're going to define loc_altitude, we should define loc_height and loc_depth as well, and make those three values optional.

@mlagally
Copy link
Owner

mlagally commented Sep 5, 2018

I agree, we should include altitude and depth and make all 3 optional.

However I would discourage the use of altitude, since it talks about mean sea level which is not a worldwide identical reference point.
See:
https://www.science20.com/news_articles/what_happens_bridge_when_one_side_uses_mediterranean_sea_level_and_another_north_sea-121600

mlagally added a commit that referenced this issue Sep 5, 2018
Integrating feedback from:
#8
#7
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

No branches or pull requests

2 participants