From: John Halleck (John.Halleck_at_utah.edu)
Date: Mon Feb 12 2001 - 00:30:26 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id AAA03383 for cavexml-outgoing; Mon, 12 Feb 2001 00:30:29 +0100 Received: from cor.oz.cc.utah.edu (nahaj_at_cor.oz.cc.utah.edu [155.99.2.2]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id AAA03379 for <cavexml_at_cartography.ch>; Mon, 12 Feb 2001 00:30:28 +0100 Received: from localhost (nahaj_at_localhost) by cor.oz.cc.utah.edu (8.9.2/8.9.2) with ESMTP id QAA28305 for <cavexml_at_cartography.ch>; Sun, 11 Feb 2001 16:30:27 -0700 (MST) Date: Sun, 11 Feb 2001 16:30:26 -0700 (MST) From: John Halleck <John.Halleck_at_utah.edu> To: cavexml_at_cartography.ch Subject: Incremental algorithms... Message-ID: <Pine.GSO.4.05.10102111619270.26377-100000@cor.oz.cc.utah.edu> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
In an earlier message I mentioned a few things that I thought
might be handy in the dataset. As I pointed out in a later
responce to Bob Thrun (and probably not obvious in the original
posting) is that I want them to support incremental update
algorithms.
Probably this is not the appropriate place to discuss such
algorithms. However, if anybody here is interested in
discussing them (I've been collecting them for years) contact
me privately... If there is enough responce I'll set up
another mailing list.
Note that CaveXML support for these don't have to be anything
extensive. For Unique compact point numbers it is only
one more (optional) attribute on a point. For spanning trees it is
just one more (optional) attribute on a shot. For adjustments
it is more complex, but leaving a space for it [Such as a tag
RMatrix) doesn't seem too bad. It might be argued (and has been)
that this might be an inclusion of "propriatary data" in the file.
But if you don't allow a specific product to include something
not in the standard, specific to itself, then the writer of that
product has a good reason not to use CaveXML as it's file format,
and it is less likely to try to put what it can in that format.
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:00 CET