Simple terms like height, depth, and altitude are great for onboarding --
though complicated usage ('geoid must always be defined in the grid_mapping'),
lessens the onboarding benefit. And if they are ambiguous, the long-term
usability is affected. (See: sea_surface_temperature.)
I want a consi
It looks like the OGC Met-Ocean Domain Working Group has also been
thinking about this:
http://external.opengeospatial.org/twiki_public/MetOceanDWG/MetOceanWMSBP20120206
This doc is two years old, so I'll ask Jeff DLB if he can summarize
for the list what they came up with.
-Rich
-R
On Mon, Fe
Dear all
Thank you for clarifications and further information.
We used "altitude" for "height above geoid" because that's what it most
commonly means, I think. However, it's unclear. To avoid confusion, we could
rename altitude as height_above_geoid, using aliases. There are 14 standard
names whi
