CDA-101 Created ADR clarifying vertical datum semantics#1784
Open
rma-bryson wants to merge 1 commit into
Open
Conversation
f8056fb to
adca2be
Compare
adca2be to
b07df3b
Compare
perrymanmd
suggested changes
Jun 16, 2026
| Context | ||
| ======= | ||
|
|
||
| When storing vertical datum information, specifically for "NATIVE" datums, there's a need to support custom or non-standard datums. |
There was a problem hiding this comment.
I think I would strike "especially for "NATIVE" datums", as the statement is true for all storage/retrieval operations on elevations, and since (as you note below) the term NATIVE just means whatever datum the elevations are stored in.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Creates ADR for discussion and clarifying Vertical Datum semantics.
Related Issue
Relates to #1611
Validation
No testing needed here
Checklist