[auscope-geosciml] RE : RE : Borehole gsml:coredIntervalGM_Envelope vs GM_Object [SEC=UNCLASSIFIED]

Boisvert, Eric Eric.Boisvert at RNCan-NRCan.gc.ca
Mon Jan 24 05:03:45 EST 2011


Depends how badly you want to query borehole based on interval location and how you depend on out-of-the-box feature of your WFS software.
 
querying 1D geometry just won't come with regular WFS implementations (unless wrong).  For GIN, we created a function.
 
Eric

 
________________________________

De: auscope-geosciml-bounces at lists.arcs.org.au de la part de Oliver.Raymond at ga.gov.au
Date: lun. 2011-01-24 00:38
À: auscope-geosciml at lists.arcs.org.au
Objet : Re: [auscope-geosciml] RE : Borehole gsml:coredIntervalGM_Envelope vs GM_Object [SEC=UNCLASSIFIED]




Hi Eric,

"One caveat  : to query, this requires the use of 1D spatial operators (or to provide your own functions)."

Is that a show-stopper, an annoying inconvenience, or something to not worry about?

Cheers,
Ollie



-----Original Message-----
From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Boisvert, Eric
Sent: Friday, 21 January 2011 9:18 PM
To: auscope-geosciml at lists.arcs.org.au
Subject: [auscope-geosciml] RE : Borehole gsml:coredIntervalGM_Envelope vs GM_Object [SEC=UNCLASSIFIED]

>You probably also want it to use a 1-D linear reference system matching the axis of the hole, in order >that the point coordinates are in fact a single-number each, being offset from the collar or similar.



>It's doable, but these are important caveats.


One caveat  : to query, this requires the use of 1D spatial operators (or to provide your own functions).


________________________________

De: auscope-geosciml-bounces at lists.arcs.org.au de la part de Simon.Cox at csiro.au
Date: jeu. 2011-01-20 22:06
À: auscope-geosciml at lists.arcs.org.au
Objet : Re: [auscope-geosciml] Borehole gsml:coredIntervalGM_Envelope vs GM_Object [SEC=UNCLASSIFIED]



It was considered desirable to specify a cored-interval using just begin-end offsets along the hole, regardless of the shape intermediate between these.

The only ISO/OGC geometry type that matches this is Envelope.



GM_Object is too general.

What you want is some kind of GM_Curve.

GM_LineString is a specialization of GM_CurveSegment, but has a special implementation in GML etc, which allows it to be substitutable for Curve.

 But if you do choose to specify the use of GM_LineString, then you must constrain it to only have two points (i.e. begin and end).

You probably also want it to use a 1-D linear reference system matching the axis of the hole, in order that the point coordinates are in fact a single-number each, being offset from the collar or similar.



It's doable, but these are important caveats.



Simon



From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Oliver.Raymond at ga.gov.au
Sent: Friday, 21 January 2011 10:31 AM
To: auscope-geosciml at lists.arcs.org.au
Subject: Re: [auscope-geosciml] Borehole gsml:coredInterval GM_Envelope vs GM_Object [SEC=UNCLASSIFIED]



..another email that slipped through in my Xmas email storm...



Bruce, did you get a reply from anyone on this?  I don't recall any decision on this at Rome.  We talked about borehole surveys vs gml:curve, but not about your question as I recall.



Having said that, I think your proposal is to change the data type is correct.  I'm not sure why we modelled CoredInterval as gml:Envelope.  Is there a member of the Boreholes subgroup (from circa Melbourne 2007) that can tell us the reason why gml:Envelope was used (or if it is just an error).



Cheers,

Ollie



______________________________________________________________________________________

Ollie Raymond

National Geological Maps and Data Standards Project
Geoscience Australia

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

Address: GPO Box 378, Canberra, ACT, 2601, Australia | ABN: 80 091 799 039
Ph: +61 2 62499575 | Fax: +61 2 62479992 | Email: oliver.raymond at ga.gov.au | Google Map
Geoscience Australia web services  -  http://www.ga.gov.au/resources/applications/ogc-wms.jsp
______________________________________________________________________________________

--- This message was created with 100% recycled electrons ---



________________________________

From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Bruce.Simons at dpi.vic.gov.au
Sent: Monday, 22 November 2010 9:45 AM
To: auscope-geosciml at lists.arcs.org.au
Subject: [auscope-geosciml] Borehole gsml:coredInterval GM_Envelope vs GM_Object



The discussion on the TWiki on GM_Envelope vs GM_Object for gsml:coredInterval has:

"For sa:shape and gsml:shape we have used GM_Object, which allows the use of gml:LineString. For gsml:coredInterval we have used GM_Envelope which allows gml:Envelope. gml:LineString allows gml:id as well as srsName, whereas gml:Envelope doesn't allow gml:id. This precludes referring to the same geometries described in the Observations (see "Multiple Properties" discussion above).

More importantly it requires gml:lowerCorner and gml:upperCorner, rather than the two gml:pos values gml:LineString uses. This is inconsistent and wrong, the gsml:coredInterval should be treated the same as the Observation interval."
(https://www.seegrid.csiro.au/wiki/bin/view/CGIModel/BoreHolesAndObservation#gml:Envelope_vs_gml:LineString) <https://www.seegrid.csiro.au/wiki/bin/view/CGIModel/BoreHolesAndObservation#gml:Envelope_vs_gml:LineString>

My recollection from Rome was we decided to change the data type on coredInterval. Is this correct?

Cheers
Bruce Simons

Ph: +61-3-9658 4502
Fax: +61-3-9658 4555
Mobile: +61 429 177155

Notice:
This email and any attachments may contain information that is personal, confidential,
legally privileged and/or copyright. No part of it should be reproduced, adapted or communicated without the prior written consent of the copyright owner.

It is the responsibility of the recipient to check for and remove viruses.

If you have received this email in error, please notify the sender by return email, delete it from your system and destroy any copies. You are not authorised to use, communicate or rely on the information contained in this email.

Please consider the environment before printing this email.







_______________________________________________
auscope-geosciml mailing list
auscope-geosciml at lists.arcs.org.au
http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml
_______________________________________________
auscope-geosciml mailing list
auscope-geosciml at lists.arcs.org.au
http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 9189 bytes
Desc: not available
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20110124/af09e700/attachment.bin>


More information about the GeoSciML mailing list