Vertical Datum Handling #853
msweier
started this conversation in
Database to API User data mapping
Replies: 2 comments 1 reply
-
@MikeNeilson and Mike Perryman, penny for your thoughts? |
Beta Was this translation helpful? Give feedback.
0 replies
-
The conversions are stored per location. It uses a specific algorithm to calculate what it should be. Like you said it's generally quite close. I'm not super aware of the future datum change, but I would assume it would work the same way, calculate by default, allow setting something else.... can't remember how to do that though. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I see that for some elevation timeseries, a vertical datum conversion is included. For example,
yeilds the timeseries data and then at the end:
What is interesting is I cannot find where this conversion is defined in the CWMS database. Where are the offsets stored? Are these associated w/ just the timeseries or location?
I don't think we have anything like stored in the database. The conversions appear to be correct or pretty close even with the oddball MSL 1912. What will the future look like when the new GEOID2022 is required? Can stage timeseries support this for multiple conversions or is this just for Elev timeseries? Any plans to allow managing in CWMS-VUE? This all kind of ties into this discourse post I had https://discourse.hecdev.net/t/datum-management-in-cwms-database/3361/3
Beta Was this translation helpful? Give feedback.
All reactions