From: Richard Knapp (gyp_caver_at_yahoo.com)
Date: Mon Jan 29 2001 - 02:18:49 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id DAA31006 for cavexml-outgoing; Mon, 29 Jan 2001 03:25:27 +0100 Received: from smtp1.mail.yahoo.com (smtp1.mail.yahoo.com [128.11.69.60]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id DAA31002 for <cavexml_at_cartography.ch>; Mon, 29 Jan 2001 03:25:26 +0100 Message-Id: <200101290225.DAA31002@karto.ethz.ch> Received: from slip166-72-184-5.nc.us.prserv.net (HELO Muphin) (166.72.184.5) by smtp.mail.vip.suc.yahoo.com with SMTP; 29 Jan 2001 02:25:36 -0000 X-Apparently-From: <gyp?caver_at_yahoo.com> From: "Richard Knapp" <gyp_caver_at_yahoo.com> To: "cavexml_at_cartography.ch" <cavexml_at_cartography.ch> Date: Sun, 28 Jan 2001 20:18:49 -0500 (EST) X-Mailer: PMMail 2.20.2030 for OS/2 Warp 4.00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: CaveXML>Range of Fields Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
>To get the ball rolling on this item from Andreas' Tasks / Todo list, I
>submit the following items (fields) for consideration. Think of these as...
It is not unreasonable to assume individual caves could be grouped in a single file or, by
using XLink, to be grouped through a single file into a cave system. Hence:
- System: a group of related caves
- System Name: The name for this system
This also would cause problems with using "Cave Survey" as the root element. Maybe the
root element should be something like:
- CaveXML: the data storage format of this file (with)
- CaveXML Version: the release of this format.
There is still some akwardness when pulling in other files via XLink, especially if they
conform to difference versions.
>Survey - An actual survey series
>Survey Name - The name applied to this survey
If the survey is continued at a later date, would two entries for one survey cause
problems?
<survey name="A" description="Entrance to first pit" date="1 Jan, 2000">
</survey>
...
<survey name="A" description="From first pit to first crawl" date="3 Feb, 2000">
</survey>
This is more of a chronological orientation but it is possible to also group as:
<survey name="A">
<subsurvey name="Entrance to first pit" date="1 Jan, 2000">
</subsurvey>
<subsurvey name="From first pit to first crawl" date="3 Feb, 2000">
</subsurvey>
</survey>
>Survey Quality - the impled quality of the survey
Would this be known before the data is compiled?
>Shot - an element of a survey, one leg or shot
>Processing - handling instructions for an item, e.g. correct, ignore,
>subtract, etc.
Would this be the same as attributes? For instance, "do not include in length", "do not
plot", "do not close", "(all of the above)".
>From - orienation of survey leg, necessary for determining Left, Right,
>Up, Down
>To - orienation of survey leg, necessary for determining Left, Right,
>Up, Down
They are also the station IDs.
>Length - measured distance between two points
Is length or distance more correct? The shot has length and there is a distance between to
stations.
>Forward Azimuth - 360 degree compass reading looking from the "From"
>station to the "To" station
>Reverse Azimuth - 360 degree compass reading looking from the "To"
>station to the "From" station
This makes it easier to distinguish between a foresight and backsight. Is a "back shot" a
valid item? Somewhere, it needs to be documented if the angles read are the real angles
or reversed angles. If I have a shot from 1 to 2 and the forward azimuth is 90, the real
backward azimuth is 270. However, there are groups that would read the back azimuth as
90. The same goes for inclination.
>Left - Distance to left wall, when looking forward in the direction of
>survey, at a given station
>Right - Distance to right wall, when looking forward in the direction of
>survey, at a given station
>Up - Distance to ceiling, when looking forward in the direction of
>survey, at a given station
>Down - Distance to floor, when looking forward in the direction of
>survey, at a given station
I think Ceiling and Floor should be a possibility as well. I don't use them but others do.
- Ceiling - distance from floor to ceiling (measurement is vertical);
- Floor - distance from the station to the floor (measurement is vertical);
Also, some way of specifying the orientation of these measurements needs to be given:
- direction: perpendicular to next, perpendicular to previous, average;
- reference: relative to caver, relative to station;
- location: from station, to station, both(!)
>Have at it.
!
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Wed Feb 14 2001 - 00:03:54 CET