search

opengeospatial / boreholeie

Repository to support the work done in the 2018-2019 Borehole Interoperability Experiment
9 stars 9 forks source link

How to encode TrajectoryReferent #68

Closed bsimons14 closed 5 years ago

bsimons14 commented 5 years ago

There are two diagrams supposedly clarifying how to encode TrajectoryReferent:

  1. https://github.com/opengeospatial/boreholeie/blob/master/Relevant_material/referent.pptx

  2. https://github.com/denevers/boreholeie/blob/d9e9e700d825a62880291b752051a106d511ac05/instances/cases/bh_reference.svg

It is still unclear how these should be encoded. An option for the first (with alternative encoding as comments) is provided at: https://github.com/opengeospatial/boreholeie/blob/master/Relevant_material/TrajectoryReferent_test.xml What is the correct encoding?

denevers commented 5 years ago

My understanding was it's still under debate - hence the two proposals

sgrellet commented 5 years ago

Agreed. Let's rediscuss it today (24th) during the webconf. One option on the table being not to carve this in the model but defer this to the BoreholeReferencingMethod (now, we have at least 2 : absolute or relative). Which seems more ISO 19148 spirit

bsimons14 commented 5 years ago

Only one way in my example encoding can be right, but I don't know which. If they are both valid then there is no way of knowing what the depths are.

Cheers Bruce

Sent from my Samsung Galaxy smartphone.

-------- Original message -------- From: sgrellet notifications@github.com Date: 24/10/19 4:52 pm (GMT+10:00) To: opengeospatial/boreholeie boreholeie@noreply.github.com Cc: Bruce Simons bruceasimons@hotmail.com, Author author@noreply.github.com Subject: Re: [opengeospatial/boreholeie] How to encode TrajectoryReferent (#68)

Agree. Let's rediscuss it today (24th) during the webconf. One option on the table being not to carve this in the model but defer this to the BoreholeReferencingMethod (now, we have at least 2 : absolute or relative). Which seems more ISO 19148 spirit

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/opengeospatial/boreholeie/issues/68?email_source=notifications&email_token=ACAGF2IZUU357MVKW7NHZGDQQEZ3RA5CNFSM4JD2HWKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDZM3Q#issuecomment-545756782, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAGF2KUY5NLA73KWEYIMWDQQEZ3RANCNFSM4JD2HWKA.

sgrellet commented 5 years ago

I think there is a way, provided you document in the BoreholeReferencingMethod that yours is : absolute or relative (to the Referent) and the unit which is used

bsimons14 commented 5 years ago

I've specified 'relative' but it is still not clear to me how to encode it based on the reference .ppt diagram:

<BhML:trajectoryReferent>​
 <BhML:DistanceExpression>​
  <BhML:distanceAlong uom="http://qudt.org/vocab/unit/M">-1.0</BhML:distanceAlong>​
  <!--Should this be "0.0" and everything be distance from here, or -1.0 and everything distance from ground level. The ppt "Point of Trajectory" suggests it should be "0.0" -->

To be clear I think we need an example of each (absolute and relative) wrt the .ppt, stating what the reference point (TrajectoryReferent) is for each.

Cheers Bruce Simons +61 475 954 391 Grand Maître, Fêlés du Grand Colombier (#1681) Club des Cinglés du Mont-Ventoux (#12000)

From: sgrellet notifications@github.com Sent: Thursday, 24 October 2019 6:32 PM To: opengeospatial/boreholeie boreholeie@noreply.github.com Cc: Bruce Simons bruceasimons@hotmail.com; Author author@noreply.github.com Subject: Re: [opengeospatial/boreholeie] How to encode TrajectoryReferent (#68)

I think there is a way, provided you document in the BoreholeReferencingMethod that yours is : absolute or relative (to the Referent) and the unit which is used

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/opengeospatial/boreholeie/issues/68?email_source=notifications&email_token=ACAGF2OVI76FHI6QTNISY4TQQFFP5A5CNFSM4JD2HWKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECEATHY#issuecomment-545786271, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAGF2N77DWCO6ZN2HOH3M3QQFFP5ANCNFSM4JD2HWKA.

sgrellet commented 5 years ago

Closing after webconference 35 (see drawing updated during the discussion) referent_20191024