From: Peter MATTHEWS (matthews_at_melbpc.org.au)
Date: Fri Dec 06 2002 - 21:16:17 CET
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 82FC915CA8 for <cavexml-outgoing_at_ethz.ch>; Fri, 6 Dec 2002 21:21:27 +0100 (CET) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id 341FB9FDB; Fri, 6 Dec 2002 21:21:24 +0100 (CET) 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 E909815CA8 for <cavexml-loopcheck_at_ethz.ch>; Fri, 6 Dec 2002 21:21:22 +0100 (CET) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 96) id 92AAD8A92; Fri, 6 Dec 2002 21:21:19 +0100 (CET) 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 4CA6F15CA8 for <cavexml_at_cartography.ch>; Fri, 6 Dec 2002 21:21:19 +0100 (CET) Received: from relay1.melbpc.org.au (newglider.melbpc.org.au [203.12.152.9]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id CFCF578B3 for <cavexml_at_cartography.ch>; Fri, 6 Dec 2002 21:21:14 +0100 (CET) Received: from peter.melbpc.org.au (a1-21.melbpc.org.au [203.12.158.21]) by relay1.melbpc.org.au (8.12.6/8.12.6) with ESMTP id gB6KFrcE000192 for <cavexml_at_cartography.ch>; Sat, 7 Dec 2002 07:15:56 +1100 (EST) (envelope-from matthews_at_melbpc.org.au) Message-Id: <5.1.0.14.1.20021207051540.01d4f1e0@popa.melbpc.org.au> X-Sender: matthews_at_popa.melbpc.org.au X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 07 Dec 2002 07:16:17 +1100 To: cavexml_at_cartography.ch From: Peter MATTHEWS <matthews_at_melbpc.org.au> Subject: Re: Raw & Field Data In-Reply-To: <5.1.0.14.1.20021125053713.01d60310_at_popa.melbpc.org.au> Content-Type: text/plain; charset="us-ascii"; format=flowed X-RAVMilter-Version: 8.3.4(snapshot 20020706) (relay1) 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
Some further comments: These definitions are meant to describe how the
various stages of survey data actually are in the cave surveying world, not
necessarily how we would like them to be to aid in CaveXML handling. I have
therefore changed the comments in the proposed Raw Data definition to allow
for this.
============================= 7-Dec-02 ======================================
Raw data:
An initial unaltered digital copy of some or all of the survey Field Data,
now ready for processing.
Comments:
1. Where the Field Data was already in digital form, e.g. downloaded from
an instrument, the Raw Data version could be an identical but editable
copy, whereas the Field Data version would effectively be a read-only copy.
2. Raw Data could include sketches now converted to fixed or editable
digital form.
3. The Raw Data could be in any format, including that of a survey
processing program into which the Field Data has been typed.
4. If such a program unilaterally alters the data as it is being entered,
then the data has become Edited Data because its values differ from the
Field Data, i.e. a Raw Data version has effectively been skipped.
5. Such a survey program might also store the data in a proprietary binary
format unconducive to easy data exchange, therefore the coming CaveXML
standard may need to define suitable forms of Raw Data to allow free
exchange. Such binary data after being exported to a text format might
qualify. Acceptable formats for raster or vector graphical data may also be
required.
========================================================================
Peter
At 21:08 06-12-02 +1100, Peter MATTHEWS wrote:
>The discussion on field and raw data indicated that the definitions should
>also allow for the following:
>- converting field data to machine-processable "raw" data may involve
>typing it into
> a survey program and that program may unilaterally change the data,
> e.g. by rounding.
>- clarify the status of scanned images - could be field, could be raw.
>- clarify the status of photocopies of field data.
>- not all data has to visit each of the types of datasets.
>- consider the term text-based vs. character-based.
>- dataset types could sometimes overlap, e.g. some data could be both
>field and raw.
>
>However no one has suggested any actual improved definitions, so here are
>my suggestions incorporating the above, for your consideration.
>
>With comments included, they're a bit longer than the originals but
>hopefully are clearer. Because the text is significantly changed from the
>originals, I'll first call for any further comments, and then later call
>for approvals.
>
>Although we do need clarity, please keep in mind that we are not designing
>the fabric of the universe here - we are just trying to come up with some
>definitions for the purpose of each of us understanding what the other is
>talking about when we later get into discussions about field definitions
>and about XML structures, so there has to be a happy medium somewhere
>which will allow us to move on.
>
>First, here are the two definitions as currently presented:
>
>============================= old ======================================
>Field data The original data and sketches recorded in the field,
> e.g. paper-based, or images thereof, or data still stored
> and observable in an instrument.
>========================================================================
> (Peter 20:02 16-Oct-02)
>============================= old ======================================
>Raw data Field data when converted unchanged into character-based,
> machine-readable form, or downloaded from an instrument.
>========================================================================
> (Peter 06:23 17-Oct-02)
>
>And here are my suggested revised definitions:
>
>============================= new ======================================
>Field data:
>The unaltered survey data (readings and/or sketches) recorded in the field
>by whatever means, or verified copies thereof.
>Comments: For example, paper-based records, or decipherable images thereof
>which may have been altered but only to clarify the original data, for
>example, marked up photocopies, or data downloaded unaltered from an
>instrument (survey instrument, PDA, laptop, etc), or data still stored and
>observable in an instrument.
>========================================================================
>
>
>============================= new ======================================
>Raw data:
>An initial unaltered digital copy of some or all of the survey Field Data,
>now ready for processing.
>Comments: Where the Field Data was already in digital form, e.g.
>downloaded from an instrument, the Raw Data version could be an identical
>but editable copy of it, whereas the Field Data version would be
>effectively a read-only copy. Raw Data can include sketches now converted
>to editable or processable digital form. The Raw Data could be in any
>format, including that of a survey processing program into which the Field
>Data has been typed. If such a program unilaterally alters the data as it
>is being entered, then the data has become Edited Data because its values
>differ from the Field Data, i.e. the Raw Data version has been skipped.
>========================================================================
>
>Any comments? Improved versions?
>
>Peter
>
This archive was generated by hypermail 2b30 : Thu Dec 19 2002 - 17:00:00 CET