Re: [GeoNetwork-users] searching records by temporal extent error

[Ricardo F. S. G. da <ric...@gm...>]

Hi Andrew, list

> Could be explained by fact that any local ISO8601 date/time i.e without a
> 'Z' indicator,
> is converted to  a UTC time in the Lucene search index that GN
> uses for search.

So I've reuploaded the metadata, this time adding a Z after the
temporal extent definitions. It now looks like this:

<gmd:extent>
<gmd:EX_Extent>
<gmd:temporalElement>
<gmd:EX_TemporalExtent>
<gmd:extent>
<gml:TimePeriod gml:id="extent_tp" frame="#ISO-8601">
<gml:description>to be filled out.</gml:description>
<gml:name>timeslot</gml:name><gml:beginPosition>2012-04-01T18:00:00Z</gml:beginPosition><gml:endPosition>2012-04-01T18:00:00Z</gml:endPosition>
</gml:TimePeriod>
</gmd:extent>
</gmd:EX_TemporalExtent>
</gmd:temporalElement>
</gmd:EX_Extent>
</gmd:extent>

The temporal research still doesn't work.

Could it be that the time that I'm giving using the GUI widgets that
is being interpreted as not being UTC? This seems really wierd. I
cannot expect my users to set their local computers to UTC time.

Or maybe there is something else..
Thanks for your help.

-- 
___________________________ ___ __
Ricardo Garcia Silva