[auscope-geosciml] GeoSciML v3 RC1 Borehole Testbed 4 issues

Bruce.Simons at dpi.vic.gov.au Bruce.Simons at dpi.vic.gov.au
Mon Jun 13 23:18:15 EDT 2011


Some problems with gsml:Boreholes that have come about during my mapping 
of groundwater, geothermal and hyperspectral boreholes:

1. Each Borehole can only have one nominalDiameter, and this must coincide 
with the Borehole:MappedInterval.
Where a borehole starts at one diameter and then is reduced in size 
further down it must be treated as two Boreholes in GeoSciML .  The 
deeper, smaller diameter hole must have a startPoint as "from pre-existing 
hole".
This is counter-intuitive;  a preferred solution would be to allow the 
nominalDiameter to vary down the Borehole by independently associating it 
with MappedInterval.

2. Multiple drillingMethods are permitted, but there is no way of 
specifying which methods were used for which part of the Borehole. This 
could be solved similar to the nominalDiameter problem.

3. Multiple coredIntervals are permitted and their geometry is specified 
with GM_LineString.  This is tolerable, but in keeping with the pattern 
proposed to solve 1 & 2 above, coredInterval should be associated with 
MappedInterval.

4. Establishing a MappedInterval service (similar to a MappedFeature 
service) doesn't allow specifying the Borehole the MappedInterval comes 
from. The only work around was to use the identity of the samplingFrame 
where this is the Borehole:
<gsml:samplingFrame>
        <gsml:Borehole gml:id="ffsr.borehole.51409">
                <gml:name codeSpace="http://www.ietf.org/rfc/rfc2616">
http://groundwater.data.vic.gov.au/borehole/ffsr/51409</gml:name>
...

I propose taking coredInterval, drillingMethod and nominalDiameter out of 
BoreholeDetails and associating them with MappedInterval (solves 1-3).

Making the Borehole - MappedInterval association bidirectional, optional 
0..1 on Borehole end (to allow MappedInterval to be used for example to 
map geological sections) and labelling the association end 
'associatedBorehole'.

I believe these should be fixed before GeoSciML v3.0 is released.

Thoughts?

----------------------------------------------------
Bruce Simons
Senior Information Geoscientist
IUGS-Commission for Geoscience Information Oceania Councillor
GeoScience Victoria/Australian Spatial Research Data Commons
Level 9, 55 Collins St
PO Box 4440
Melbourne, Victoria, 3001
Australia

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20110614/41be9352/attachment.htm>


More information about the GeoSciML mailing list