[auscope-geosciml] Time Scale

Boisvert, Eric Eric.Boisvert at RNCan-NRCan.gc.ca
Wed Aug 11 14:21:10 EDT 2010


Hi all.

I tested the time scale schema and implemented the URI resolution (which was the original goal).

The whole chart is here

http://ngwd-bdnes.cits.nrcan.gc.ca:8080/Reference/uri-cgi/classifierScheme/ICS/StratChart/2010

And internal reference (trs:member) are also resolvable

Eg:

http://ngwd-bdnes.cits.nrcan.gc.ca:8080/Reference/uri-cgi/classifier/ICS/StratChart/2010/PZ

This subset will only report the two boundaries that are used for this specific GeochronologicEra

An interesting side effect of the implementation is this URL

http://ngwd-bdnes.cits.nrcan.gc.ca:8080/Reference/uri-cgi/classifier/ICS/StratChart/2010/Q,PZ,CZ

Will return all Q,PZ and CZ, although I'm pretty sure it's intended to be used that way.

I do have a couple of questions about my serialization

A) what Am I suppose to do with

<gt:geochronologicEraType>
  <gt:GeochronologicEraTypeTerm/>
  </gt:geochronologicEraType>


The schema just says it's an abstract object.  Look like there is a term list missing (or should it be a CGI_Term ?)

B) If I understand correctly, all the boudary ages should be list individually at the bottom, should these NumericEraBoundary also have a full identity (URI) and be individually resolvable ?

C) Did I get the encoding of the value correctly ?  I have two examples

<gt:referencePoint>
		<gt:NumericEraBoundary gml:id="age.K2d-K2c">
			<gml:name>K2d-K2c</gml:name>
			<trs:position>
				<gml:TimeInstant>
					<gml:timePosition calendarEraName="MA">85.8</gml:timePosition>
				</gml:TimeInstant>
			</trs:position>
			<gt:status>unknown</gt:status>
		</gt:NumericEraBoundary>
	</gt:referencePoint>
	<gt:referencePoint>
		<gt:StandardGlobalNumericalAge gml:id="age.NPR2-NPR1">
			<gml:name>NPR2-NPR1</gml:name>
			<trs:position>
				<gml:TimeInstant>
					<gml:timePosition calendarEraName="MA">850</gml:timePosition>
				</gml:TimeInstant>
			</trs:position>
			<gt:status>unknown</gt:status>
		</gt:StandardGlobalNumericalAge>
	</gt:referencePoint>

I have used NumericEraBoundaries because I did not search all the detailed description for boundaries (and create GeochronologicBoundaries), but I used StandardGlobalNumericalAge when the age are defined by definition (such as Precambrian boundaries).
Did I get this correctly ?

Also, I'm not sure how to encode the gml:timePosition (calendarEraName in particular).  I just put MA for now.

D) should the  NumericEraBoundary provides all the nextEra and previousEra too ?

E) Any other comments ?

Eric

 

================================================================
Eric Boisvert
Spécialiste TI-GI / IT-IM specialist
Eric.Boisvert at rncan.gc.ca, 418-654-3705, facsimile/télécopieur 
418-654-2615
490, rue de la Couronne, Québec (Québec), G1K 9A9
490, rue de la Couronne, Quebec, Quebec, G1K 9A9

Laboratoire de cartographie numérique et de photogrammétrie (LCNP)
Digital Cartography and Photogrammetry Laboratory (DCPL)
Commission géologique du Canada (Québec) / Geological Survey of Canada (Quebec)
Ressources naturelles Canada / Natural Resources Canada
Gouvernement du Canada / Government of Canada
http://cgc.rncan.gc.ca/org/quebec
http://cgc.rncan.gc.ca/dir/index_f.php?id=4186 / http://cgc.rncan.gc.ca/dir/index_e.php?id=4186




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20100811/2f3ecdd4/attachment.htm>


More information about the GeoSciML mailing list