[auscope-geosciml] [GeoSciML] #50: Sampling feature can't report from which collection(s) it comes from [SEC=UNCLASSIFIED]

Simon.Cox at csiro.au Simon.Cox at csiro.au
Wed Jun 8 05:49:40 EDT 2011


"O&M v1 didn’t have this problem, because SamplingFeatureCollection was a subtype of SamplingFeature, and so the relatedSamplingFeature association could be used to link a Sample to its SamplingFeatureCollection.  It would be interesting to learn the rationale behind the change in O&M v2."

Its quite simple: on futher examination, SamplingFeatureCollection did not appear to logically have the same properties as a SamplingFeature. In particular, the association to a SampledFeature that is ligically shared by all members did not seem to work, and the association to related observations was ambiguous in terms of which member sampling features was involved.

Simon Cox
Research Scientist
CSIRO Earth Science & Resource Engineering

Phone: +61 8 6436 8639 | Fax: +61 8 6436 8555 | Mobile: 0403 302 672
simon.cox at csiro.au<mailto:simon.cox at csiro.au> | www.csiro.au<http://www.csiro.au/>
Address: ARRC, PO Box 1130, Bentley, WA 6102, Australia

________________________________
From: auscope-geosciml-bounces at lists.arcs.org.au [auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Oliver.Raymond at ga.gov.au [Oliver.Raymond at ga.gov.au]
Sent: Wednesday, 8 June 2011 7:15 AM
To: auscope-geosciml at lists.arcs.org.au
Subject: Re: [auscope-geosciml] [GeoSciML] #50: Sampling feature can't report from which collection(s) it comes from [SEC=UNCLASSIFIED]


Hi Eric,



I agree.  It appears you may have to use the "SamplingFeatureComplex" association class to group your samples together with a role of “member of the XYZ SamplingFeatureCollection”?  Or you would have to refactor your WFS to deliver SF_SamplingFeatureCollection/member/SF_SamplingFeatures instead.  I think I’d prefer to have an optional navigable association from SF_SamplingFeature to SF_SamplingFeatureCollection too.



[cid:image001.jpg at 01CC25BC.A78DF700]



O&M v1 didn’t have this problem, because SamplingFeatureCollection was a subtype of SamplingFeature, and so the relatedSamplingFeature association could be used to link a Sample to its SamplingFeatureCollection.  It would be interesting to learn the rationale behind the change in O&M v2.



Ollie





-----Original Message-----
From: GeoSciML [mailto:trac at projects.arcs.org.au]
Sent: Wednesday, 8 June 2011 12:25 AM
Subject: [GeoSciML] #50: Sampling feature can't report from which collection(s) it comes from



#50: Sampling feature can't report from which collection(s) it comes from

---------------------------------------------+------------------------------

 Reporter:  eric.boisvert@…                  |       Owner:  Oliver.Raymond@…

     Type:  defect                           |      Status:  new

 Priority:  minor                            |   Milestone:  Testbed

Component:  Model                            |     Version:

 Keywords:  SamplingFeature                  |

---------------------------------------------+------------------------------

 The link between SF_SamplingFeatureCollection and SF_SamplingFeature is

 unidirectional, therefore a WFS that exposes SF_SamplingFeature cannot

 link back to the collection.



 This is an issue with SF_SamplingFeature and not GeoSciML



--

Ticket URL: <https://projects.arcs.org.au/trac/geosciml/ticket/50>

GeoSciML <https://projects.arcs.org.au/trac/geosciml>

GeoSciML
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 22715 bytes
Desc: image001.jpg
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20110608/412e219e/attachment.jpg>


More information about the GeoSciML mailing list