From: Alexander Nickolsky (nickol_at_argussoft.ru)
Date: Wed Jun 26 2002 - 16:49:59 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 9E92C15869 for <cavexml-outgoing_at_ethz.ch>; Wed, 26 Jun 2002 17:09:38 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id 6D1B915865; Wed, 26 Jun 2002 17:09:36 +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 6D2A815869 for <cavexml-loopcheck_at_ethz.ch>; Wed, 26 Jun 2002 17:09:35 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 96) id 4B24415838; Wed, 26 Jun 2002 17:09:33 +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 05FD515869 for <cavexml_at_cartography.ch>; Wed, 26 Jun 2002 17:09:33 +0200 (CEST) Received: from ns.argussoft.ru (ns.argussoft.ru [195.7.171.132]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id C8F1D15809 for <cavexml_at_cartography.ch>; Wed, 26 Jun 2002 17:09:29 +0200 (CEST) Received: from cachet (cachet.argussoft.ru [195.7.171.199]) by ns.argussoft.ru (8.9.1/8.9.1) with SMTP id RAA29003 for <cavexml_at_cartography.ch>; Wed, 26 Jun 2002 17:47:15 +0300 (MSK) Message-ID: <007001c21d20$bedf9d40$c7ab07c3@argussoft.ru> From: "Alexander Nickolsky" <nickol_at_argussoft.ru> To: <cavexml_at_cartography.ch> References: <20020626142541.9D90B9A43_at_karmail.ethz.ch> Subject: Re: Progress report - cave survey data model Date: Wed, 26 Jun 2002 18:49:59 +0400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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
----- Original Message -----
From: "Richard Knapp" <richfk_at_attglobal.net>
To: <cavexml_at_cartography.ch>
Sent: Wednesday, June 26, 2002 5:36 PM
Subject: Re: Progress report - cave survey data model
>
> > The most interesting problem (and the real one) is how to represent data
:
> > shots or stations. Speaking mathematically, it is a graph
representation.
> > stations are graph nodes, and shots are branches. The problem is
> > that nobody surveys this way. So shots should be recorded.
>
> Isn't it more a directed graph? How would surveying be different if it was
done just as a
> graph?
It is an oriented (directed) graph in some sense. There is some data,
associated to graph
elements, that include direction. It is there because of the method used for
measurement.
If we could somehow measure absolute coordinates a-la GPS, direction will be
unnecessary, but the graph will remain. (BTW : technicaly it is not THAT
impossible.
Using sensitive magnitometer, the cave positioning system could be made.)
>
> > And there will be some stations with no place to put comments - the last
> > stations in branches.
>
> Comments and Notes should be allowed on shots and stations in the format.
If not, they
> the format is just asking for trouble. As to those that record the data,
there's not much
> a data format can do to influence how they survey. In fact, a good format
will let them
> survey how every they want and adapt to their method - no matter if it is
good or bad.
Agree. This is 100% correct.
> <Shot from="A1" to="A2">
> <Azimuth value="135" direction="Forward"/>
> <Azimuth value="316" direction="Backward"/>
> .....
> </Shot>
but if the shot is backward, where the comment belongs ?
> True. However, would it be worthwhile to delineate the Survey data section
from the
> Inventory or Picture or ? section?
It depends on the definition of 'survey'. I used 'segment' to denote a
series of
measurements done by the same team in the same conditions and sharing
some defaults, like precision, methods, etc. One trip can contain
several segments, for example surveying large passage makes one segment
and narrow belly-crawl makes another. In this case data goes outside
the 'segment'.
This archive was generated by hypermail 2b30 : Wed Jul 10 2002 - 21:35:00 CEST