Hello,
I have a colleague who is facing an issue when he tries to use the temporal
extent in GeoNetwork. It appears that the "gml:timePeriod" attribute
"gml:Id" is not being managed correctly by GeoNetwork. This is the problem
he is having -
/When validating one of our records (we're on GN 2.6.3) in preparation to
export it, I kept getting a persistent error that took me ages to track
down. The element that ended up being the cause of the problem was
TimePeriod. Below is the incorrect xml:
<gmd:extent>
<gmd:EX_Extent>
<gmd:temporalElement>
<gmd:EX_TemporalExtent>
<gmd:extent>
<gml:TimePeriod>
<gml:name>NZST</gml:name>
<gml:beginPosition>2007-07-01T15:41:00</gml:beginPosition>
<gml:endPosition>2012-06-30T15:41:00</gml:endPosition>
</gml:TimePeriod>
</gmd:extent>
</gmd:EX_TemporalExtent>
</gmd:temporalElement>
</gmd:EX_Extent>
</gmd:extent>
There is no id attribute on the timePeriod element, which is the cause of
the error. I couldn't seem to fix that in the editing interface, and ended
up editing the xml directly to add a blank id attribute. When I next saved
the record, GeoNetwork then inserted an alphanumeric string into the id
attribute by itself. Below is the xml that validates OK:
<gmd:extent>
<gmd:EX_Extent>
<gmd:temporalElement>
<gmd:EX_TemporalExtent>
<gmd:extent>
<gml:TimePeriod <b>gml:id="d127482e584a1052958"*>
<gml:name>NZST</gml:name>
<gml:beginPosition>2007-07-01T15:41:00</gml:beginPosition>
<gml:endPosition>2012-06-30T15:41:00</gml:endPosition>
</gml:TimePeriod>
</gmd:extent>
</gmd:EX_TemporalExtent>
</gmd:temporalElement>
</gmd:EX_Extent>
</gmd:extent>/
As you can see, it was the gml:Id element that fixed the problem. There
seems to be no way to set the value of this element in GeoNetwork, so it is
difficult to correct. If not corrected it fails validation. On further
examination it seems the Temporal extent used here is meant to have an
attribute to indicate what sort off time period is being referenced. Like
for a timeperiod value “Cenozoic” the timeperiod id would be “geologic”. It
seems this is being ignored by GeoNetwork and arbitrary values are being
inserted instead. Since in this case, the time period is standard date/time,
the value of this field does not matter greatly. Anyone looking at the
values knows what they mean. The USGIN site, (
http://repository.usgin.org/sites/default/files/dlio/files/2011/u11/usgin_iso_metadata_1.1.3.pdf)
gives further details as to what values this attribute should hold.
Any thoughts from those who understand these standards better than I? Should
this be submitted as a bug?
Cheers,
Byron Cochrane
LISAsoft
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Temporal-Extent-TimePeriod-ID-error-tp7037167p7037167.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.