Skip to content

CDA-101 Created ADR clarifying vertical datum semantics#1784

Open
rma-bryson wants to merge 1 commit into
developfrom
feature/CDA-101-ADR-for-vertical-datum
Open

CDA-101 Created ADR clarifying vertical datum semantics#1784
rma-bryson wants to merge 1 commit into
developfrom
feature/CDA-101-ADR-for-vertical-datum

Conversation

@rma-bryson

Copy link
Copy Markdown
Collaborator

Summary

Creates ADR for discussion and clarifying Vertical Datum semantics.

Related Issue

Relates to #1611

Validation

No testing needed here

Checklist

  • AI tools used

@rma-bryson rma-bryson force-pushed the feature/CDA-101-ADR-for-vertical-datum branch from f8056fb to adca2be Compare June 15, 2026 22:04
@rma-bryson rma-bryson force-pushed the feature/CDA-101-ADR-for-vertical-datum branch from adca2be to b07df3b Compare June 16, 2026 20:56
@rma-bryson rma-bryson marked this pull request as ready for review June 16, 2026 20:56
Context
=======

When storing vertical datum information, specifically for "NATIVE" datums, there's a need to support custom or non-standard datums.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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.

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.

2 participants