Changes between Version 10 and Version 11 of TemporalExtentSearch
- Timestamp:
- Apr 14, 2010, 5:51:31 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TemporalExtentSearch
v10 v11 35 35 [[Image(temporalextentsearch1.png)]] 36 36 37 In ISO records temporal extents can be specified in a number of different ways (GML has many different and flexible representations for time). The !GeoNetwork editor simplifies the options by using a !JavaScript calendar interface to specify an ISO DateTime or ISO Date interface. For temporal extent searching to work correctly, we need a flexible method of parsing as many of the different time formats as possible because not all records in the catalog will be created using the !GeoNetwork editor. After parsing we will need to convert to a common time format and timezone before storing in a Lucene Index field for searching.37 In ISO records temporal extents can be specified in a number of different ways (GML has many different and flexible representations for time). The !GeoNetwork editor simplifies the options by using a !JavaScript calendar interface to specify an ISO !DateTime or ISO Date interface. For temporal extent searching to work correctly, we need a flexible method of parsing as many of the different time formats as possible because not all records in the catalog will be created using the !GeoNetwork editor. After parsing we will need to convert to a common time format and timezone before storing in a Lucene Index field for searching. 38 38 39 39 Example temporal extents (these were not created with the !GeoNetwork editor):
