From: Andreas Neumann (neumann_at_karto.baug.ethz.ch)
Date: Sun Feb 11 2001 - 21:23:51 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id VAA02395 for cavexml-outgoing; Sun, 11 Feb 2001 21:23:52 +0100 Received: from karto.ethz.ch (karto.ethz.ch [129.132.127.159]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id VAA02391 for <cavexml_at_cartography.ch>; Sun, 11 Feb 2001 21:23:51 +0100 Date: Sun, 11 Feb 2001 21:23:51 +0100 (CET) From: Andreas Neumann <neumann_at_karto.baug.ethz.ch> X-Sender: <an_at_karto.ethz.ch> To: <cavexml_at_cartography.ch> Subject: Stepwise establishing Cavexml-standard / Grouping Message-ID: <Pine.LNX.4.30.0102112048450.2283-100000@karto.ethz.ch> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
Hello!
In order to successfully establish a common CaveXML-standard I suggest
that we first try to integrate data that can already be used by todays
cave-surveying software. This will speed up the development of export and
import filters and we can more easily promote our suggestion rather than
by trying to cover each single case and all surveying methods.
However we can already discuss the more complex cases for future versions.
(f.e. complex cross-sections, version tracking, keeping original
data, etc.)
Martin Heller and I discussed various aspects and read your contributions.
Martin will soon send a suggestion of how he would like to store his own
data xml-based in the future. Maybe we could use this as a starting-point
for future discussions and see if and how we can represent data from the
different cave-surveying programs using this approach.
Toporobots series structure can be represented by a grouping feature,
similar to grouping-structures also used for chronological, survey, survey
method, surveyor, etc. I can immediately specify at least ten different
grouping schemes (like different database queries). So the original data
structure/hierachy could be quite flat with different grouping rules that
allow us to represent the data in different "views". A unique ID (must
only be known internally by the software) for stations, shots, bisectors,
fixpoints, etc. is a prerequisite for such representations. Series like
the ones used in Toporobot and CaveRender are just one of many different
grouping methods that can be defined.
A rather flat hierarchy can also be easier stored in relational
databases.
Andreas
"If you have got the right attitude,
interesting problems will find you."
(Eric S. Raymond)
----------------------------------------------
Andreas Neumann - Department of Cartography
Swiss Federal Institute of Technology (ETH)
ETH Hoenggerberg, CH-8093 Zurich, Switzerland
Phone: ++41-1-633 3037, Fax: ++41-1-633 1153
e-mail: andreas.neumann_at_karto.baug.ethz.ch
www: http://www.karto.ethz.ch/~an/
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:00 CET