You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the question whether elevation in basin-3d needs to be represented as an
absolute or relative value? I would deal with this as a unit conversion
issue. We cannot do the conversion without the top of casing or ground
reference elevation
On Thu, Sep 14, 2023 at 1:36 PM D.S. Christianson ***@***.***> wrote:
Unclear how to handle the following elevation + depth/height cases:
Feature is a point at a given height or depth from the ground surface.
1. Elevation is reported as ground surface. Height / depth of the
feature is also reported relative to ground surface.
2. Elevation is reported as the absolute location of the feature.
Height / depth of the feature is also reported relative to the ground
surface.
We have been implementing height / depth in both cases as a representative
coordinate in the plugins thus far.
Is elevation in case 1 a representative coordinate and in case 2 it is
absolute?
We should probably add some documentation on how to use / interpret these
location fields in the data model.
—
Reply to this email directly, view it on GitHub
<#175>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC2PYFAP56XANQOZ266Y3ETX2NTGBANCNFSM6AAAAAA4YZMJVM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
It's about how to report elevation when the point is not at the ground surface. Data sources may treat their location information differently as in the cases as described above. Assume there is a reference for the depth / height value.
Unclear how to handle the following elevation + depth/height cases:
Feature is a point at a given height or depth from the ground surface.
We have been implementing height / depth in both cases as a representative coordinate in the plugins thus far.
Is elevation in case 1 a representative coordinate and in case 2 it is absolute?
We should probably add some documentation on how to use / interpret these location fields in the data model.
The text was updated successfully, but these errors were encountered: