From: Richard Knapp (richfk_at_attglobal.net)
Date: Mon Jun 24 2002 - 11:40:54 CEST
Return-Path: <owner-cavexml-outgoing_at_ethz.ch> Delivered-To: cavexml-archive_at_cartography.ch Received: from localhost (localhost [127.0.0.1]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id AF91C15834 for <cavexml-outgoing_at_ethz.ch>; Mon, 24 Jun 2002 16:14:36 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id 912AE14AD5; Mon, 24 Jun 2002 16:14:34 +0200 (CEST) Delivered-To: cavexml-loopcheck_at_ethz.ch Received: from localhost (localhost [127.0.0.1]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id 566B615834 for <cavexml-loopcheck_at_ethz.ch>; Mon, 24 Jun 2002 16:14:33 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 96) id 30B7914AD3; Mon, 24 Jun 2002 16:14:31 +0200 (CEST) Delivered-To: cavexml_at_cartography.ch Received: from localhost (localhost [127.0.0.1]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id D5E9215834 for <cavexml_at_cartography.ch>; Mon, 24 Jun 2002 16:14:30 +0200 (CEST) Received: from prserv.net (out1.prserv.net [32.97.166.31]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id 7999614ACD for <cavexml_at_cartography.ch>; Mon, 24 Jun 2002 16:14:26 +0200 (CEST) Received: from Muphin (slip-12-65-6-34.mis.prserv.net[12.65.6.34]) by prserv.net (out1) with SMTP id <200206241356452010665ml7e>; Mon, 24 Jun 2002 13:56:46 +0000 From: "Richard Knapp" <richfk_at_attglobal.net> To: "cavexml_at_cartography.ch" <cavexml_at_cartography.ch> Date: Mon, 24 Jun 2002 05:40:54 -0400 (EDT) X-Mailer: PMMail 2.20.2380 for OS/2 Warp 4.5 In-Reply-To: <5.1.0.14.1.20020620051819.01d78ec0_at_popa.melbpc.org.au> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Progress report - cave survey data model Message-Id: <20020624141426.7999614ACD@karmail.ethz.ch> X-Loop: cavexml Sender: owner-cavexml_at_karmail.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch X-Virus-Scanned: by AMaViS perl-11
Peter,
An excellent start. Some ramblings....
On the next draft, could you include some simple definitions for the elements? There are
some elements that appear unrelated (Spur, Segment, etc).
(Again, just ramblings.)
Will "Name" (for Branch, Cave, etc) be made an attribute or an element?
Comment seems to be missing.
Will Coordinate data be stored as and attribute of a Station or as a Point? One of the
problems I have with COMPASS is it never displays the actual error it finds on loops; all
loops are assumed closed because it has no way to hold multiple end points for a single
station. Karst had a nice feature of showing the non-aligned points and then drew dark
blue, dashed lines between lines the points. Coodinate data would also be useful for
locating the Entrance.
Will Measurement hold all shot attributes (length, direction, azimuth, etc.)? That's a
rather clean way to hold the information.
How about passage dimensions? Will they be put as a measurement or something else? I
think it would be good to allow people to measure passage dims with spherical coordinates
if desired. One of the problems discussed on CaversDigest was taking LRUDs at a pit or
other very high angle/incline shots. There really is no Left or Right since the survey
line goes straight down. LRUD could still be used but it would just be shorthand for 90
deg off the last shot at zero inclination. If the surveyor wanted other dimensions
recorded (for solid modeling or whatever), they could be added:
azimuth = "135" incline="+45" distance="10.5"
azimuth = "215" incline="-45" distance="40"
It is like having spray shots for passage dimensions. If such information is associated
with a Shot element, then having the reference point specified would be necessary as well
(at="").
Would survey date (or processing date) be a separate element or attribute?
Declination?
I see Person but not Role/Job/Position. If those items are just an attribute, then a
survey member can only have one position during a survey. However, there are many times
when one person does many things: sketch, backsights, and lead tape or frontsights and
inventory.
Will things like Book Format (one or two line data collection), Tape Method, BackSight
Method, PassageDimensions, etc. be put under the Survey as attributes? Or will these be
under Method?
Will there be a way to specify the order and units of each data item? This would be
similar to the FORMAT directive in COMPASS and would allow the "view" of the data to
alter without effecting the DOM. Specifying units with each measurement removes any
implied units and the need to include on each measurement element.
Will there be a Survey header to collect all the header info and keep those elements
separate from the Data section or will it just be Survey?
Should consideration be given now to simple "inventory" data like temperature, wind
velocity, humidity? If a precision survey is being done (theodelite), temperature may be
required to process the data.
What is the root element? I thought there was some agreement that a CaveXML element would
exist containing version information.
> To give you an idea of what I will be covering in the initial draft, here
> are the entities currently included. Of course their names will also be
> subject to discussion. If I have left out any obvious entities please let
> me know by return so I can include them in the first draft.
>
> Branch
> Cave
> CaveSystem
> Fieldbook
> Instrument
> Interpoint
> Leg
> Map
> Measurement
> Method
> Node
> Organisation
> Person
> Point
> Project
> Role
> Segment
> Shot
> Spur
> Station
> Survey
> Team
> Technique
> Trip
This archive was generated by hypermail 2b30 : Wed Jul 10 2002 - 21:35:00 CEST