[auscope-geosciml] GeoSciML Detection Limits [SEC=UNCLASSIFIED]

Bruce.Simons at csiro.au Bruce.Simons at csiro.au
Wed May 23 19:18:33 EDT 2012


It's a beautiful thing!
It emphasises the view that XML (and RDF) are for exchanging small subsets of data that match a filter/query, and not for large datasets.
Whether the current filter/query processes are up to this is questionable.

I'm coming around to the view (courtesy of Alistair and Simon) that it's not the schema that is the persistent information model (and UML merely a domain-specialist friendly way to represent the schema) but that the persistent artefacts that specify the format are in fact the UML (and/or RDF graph) and the language used to exchange the data (XML, RDF, SQLite, Word etc) should be client specified.

Of course like most of SOA it is not possible to fully separate the layers, so GeoSciML is 'GML-friendly' rather than 'RDF-friendly', but perhaps one of the aims ought to be to try to preserve the information model while making it more technology neutral.

Cheers

Bruce Simons
SDI Information Modeller
Land and Water/ Environmental Information Systems
CSIRO
E bruce.simons at csiro.au T +61 3 9252 6514 M +61 429 177155
PO Box 56, Highett, Victoria, 3190
www.csiro.au | www.csiro.au/science/Environmental-Information-Systems

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.
Please consider the environment before printing this email.



From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Boisvert, Eric
Sent: Wednesday, 23 May 2012 9:38 PM
To: auscope-geosciml at lists.arcs.org.au
Subject: Re: [auscope-geosciml] GeoSciML Detection Limits [SEC=UNCLASSIFIED]

wow.
I know nobody is supposed to see the XML encoding and compression will squeeze this 95% ... but still...



________________________________
De : auscope-geosciml-bounces at lists.arcs.org.au<mailto:auscope-geosciml-bounces at lists.arcs.org.au> [mailto:auscope-geosciml-bounces at lists.arcs.org.au] De la part de Oliver.Raymond at ga.gov.au<mailto:Oliver.Raymond at ga.gov.au>
Envoyé : 23 mai 2012 02:52
À : auscope-geosciml at lists.arcs.org.au<mailto:auscope-geosciml at lists.arcs.org.au>
Objet : Re: [auscope-geosciml] GeoSciML Detection Limits [SEC=UNCLASSIFIED]
Try multiple om:resultQuality elements...

        <om:OM_Observation>
 <om:resultQuality>
                <gmd:DQ_QuantitativeAttributeAccuracy>
                    <gmd:nameOfMeasure>
                        <gco:CharacterString>positive error</gco:CharacterString>
                    </gmd:nameOfMeasure>
                    <gmd:result>
                        <gmd:DQ_QuantitativeResult>
                            <gmd:valueUnit xlink:href="http://www.opengis.net/def/uom/UCUM/0/%25" xlink:title="%"/>
                            <gmd:value>
                                <gco:Record>
                                    <gco:Real>0.01</gco:Real>
                                </gco:Record>
                            </gmd:value>
                        </gmd:DQ_QuantitativeResult>
                    </gmd:result>
                </gmd:DQ_QuantitativeAttributeAccuracy>
            </om:resultQuality>
            <om:resultQuality>
                <gmd:DQ_QuantitativeAttributeAccuracy>
                    <gmd:nameOfMeasure>
                        <gco:CharacterString>negative error</gco:CharacterString>
                    </gmd:nameOfMeasure>
                    <gmd:result>
                        <gmd:DQ_QuantitativeResult>
                            <gmd:valueUnit xlink:href="http://www.opengis.net/def/uom/UCUM/0/%25" xlink:title="%"/>
                            <gmd:value>
                                <gco:Record>
                                    <gco:Real>0.02</gco:Real>
                                </gco:Record>
                            </gmd:value>
                        </gmd:DQ_QuantitativeResult>
                    </gmd:result>
                </gmd:DQ_QuantitativeAttributeAccuracy>
            </om:resultQuality>
Cheers,
Ollie
__________________________________________________________________

Ollie Raymond
Section Leader  |  National Geological Maps and Data Standards Section
Minerals and Natural Hazards Division  |  GEOSCIENCE AUSTRALIA

Interoperability Working Group
IUGS Commission for the Management and Application of Geoscience Information
__________________________________________________________

Phone:  +61 2 6249 9575    Fax:  +61 2 6249 9917
Email:  Oliver.Raymond at ga.gov.au<mailto:Oliver.Raymond at ga.gov.au>    Web:  www.ga.gov.au<http://www.ga.gov.au/>
Cnr Jerrabomberra Avenue and Hindmarsh Drive Symonston ACT
GPO Box 378 Canberra ACT 2601 Australia

Applying geoscience to Australia's most important challenges

________________________________
From: auscope-geosciml-bounces at lists.arcs.org.au<mailto:auscope-geosciml-bounces at lists.arcs.org.au> [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Bruce.Simons at csiro.au<mailto:Bruce.Simons at csiro.au>
Sent: Monday, 21 May 2012 14:02
To: auscope-geosciml at lists.arcs.org.au<mailto:auscope-geosciml at lists.arcs.org.au>
Subject: [auscope-geosciml] GeoSciML Detection Limits

Some time ago (2010)there was a discussion on specifying errors and detection limits at https://www.seegrid.csiro.au/wiki/CGIModel/GeochemicalAnalysesDiscussion:

4. Detection limits and analytical errors - how do we easily associate the analyte detection limit or analytical error defined in a session to the result for each analyte? Currently the result and the analytical error/detection limit have very different xpaths, and associating the two elements could be tricky. But if we use swe:Quantity to deliver both the Observation-Result and the Process-DetectionLimit then we could use a xlink:href pointer from Observation->result->DataRecord->Quantity->Quality->Quantity to the gml:id of the detection limit Quantity element (which is in Process->Acquisition->AnalyticalSession->ResultQualityDescription).

Does anyone recall if this was ever resolved?

Specifically I am after a way of encoding error ranges associated with laboratory results.

Ollie's example (on the same Wiki page) using DQ_QuantitativeResult has:

<gmd:result>
    <gmd:DQ_QuantitativeResult>    <!-- This class is very similar to swe:Quantity, but with a useful optional "errorStatistic" attribute  -->
         <gmd:valueUnit >
           <gml:UnitDefinition gml:id="ppm_Cu">
              <gml:name>parts per million</gml:name>
             <gml:quantityType>Cu</gml:quantityType>
              <gml:catalogSymbol>ppm</gml:catalogSymbol>
            </gml:UnitDefinition>
          </gmd:valueUnit>
           <gmd:errorStatistic>
               <gco:CharacterString>2 sigma</gco:CharacterString>
           </gmd:errorStatistic>
           <gmd:value>
                <gco:Record>
                 <gml:measure uom="ppm">0.5</gml:measure>
                 </gco:Record>
             </gmd:value>
       </gmd:DQ_QuantitativeResult>
 </gmd:result

The problem with this example is that it only allows one gmd:errorStatistic, whereas I want to include a lower and upper value.
I have not found any instance documents which provide examples of how to do this. Has anyone else played in this space?

Cheers

Bruce Simons
SDI Information Modeller
Land and Water/ Environmental Information Systems
CSIRO
E bruce.simons at csiro.au<mailto:bruce.simons at csiro.au> T +61 3 9252 6514 M +61 429 177155
PO Box 56, Highett, Victoria, 3190
www.csiro.au<http://www.csiro.au> | www.csiro.au/science/Environmental-Information-Systems<http://www.csiro.au/science/Environmental-Information-Systems>

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.
Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20120524/4818aed4/attachment.htm>


More information about the GeoSciML mailing list