XML: was Bedding planes, rose diagrams and bug fix (fwd)

John Halleck John.Halleck@utah.edu
Wed, 3 May 2000 11:43:23 -0600 (MDT)


Since there seems to be a request for the dialog to stay on the list,
I'll forward to the list the stuff I sent Michael.

     ---------- Forwarded message One----------

Date: Wed, 3 May 2000 09:35:32 -0600 (MDT)
From: John Halleck <nahaj@u.cc.utah.edu>
To: Michael Lake <Mike.Lake@uts.edu.au>

>   There are things I'd like to see, and didn't, in the area of data
>   concerning survey adjustment.  But I suspect that that is not of
>   general interest, so I'll take it up in private email.

  This is just off the top of my head, so take it with a grain of salt.

1) Covariance of the instrument observations.  A symmetric 3x3 matrix, so one
   only needs to store 6 numbers.
   This is generally the same for an entire cave, but can change from shot to
   shot in truely bizarre surveys.
   99.9% of the time it is the same for an entire survey... so I'd consider it
   a candidate for
   <sometag D="..." A="..." I="..." DA="..." DI="..." AI="..."> survey </sometag>>
   style marking.
   [I'm assuming Distance Asimuth Inclination as was is measured.]
   (D, A, and I are manditory, DA, DI, AI are optional)

2) Covariance of the adjuted points.  Roughly the same as the above in form,
   but with
   <sometag X="...", Y="...", Z="...", XY="...", XZ="...", YZ="...">


I wouldn't mind having (but it would probably clutter the world) the
ability to include (so that updates are minor) generated analysis
data such as reference counts, and the spanning tree of the 
geometry matrix.


    ---------- Forwarded message Two ----------

Date: Wed, 3 May 2000 09:46:40 -0600 (MDT)
From: John Halleck <nahaj@u.cc.utah.edu>
To: Michael Lake <Mike.Lake@uts.edu.au>
Cc: Lev Bishop <lev.bishop@queens.oxford.ac.uk>, John Halleck <John.Halleck@utah.edu>
Subject: Re: XML:  was Bedding planes, rose diagrams and bug fix

On Wed, 3 May 2000, John Halleck wrote:

Almost any program that does any analysis of the data is going to
have to assign a unique number to each survey point.  If this could
be put in the data, then further analysis programs could use the
previous numbers.  (The same could be said of shot numbers...)

If there is a range used put somewhere up front, then combining
sections could be made efficient.