Skip to content

Latest commit

 

History

History
54 lines (39 loc) · 2.01 KB

time_detection.md

File metadata and controls

54 lines (39 loc) · 2.01 KB

Time Detection

The OnEarth Time Service has the ability to detect time ranges for a given layer. This is accomplished by the use of special keywords in the layer configuration file.

Time Element Options

  1. Known date range in ISO 8601 format with start time, end time, and duration.
time_config: "2013-01-01/2014-03-28/P1D"
  1. Automatically detect the start time, end time, and duration.
time_config: "DETECT"
  1. Automatically detect only the start time.
time_config: "DETECT/2014-03-28/P1D"
  1. Automatically detect only the end time.
time_config: "2013-01-01/DETECT/P1D"
  1. Automatically detect the start and end times but use a predetermined period.
time_config: "DETECT/DETECT/P5D"
  1. Automatically detect the start and end times but use a predetermined period; create multiple date ranges if breaks are detected.
time_config: "DETECT/P5D"
  1. Known date range format with start time as diff from LATEST date (ex. 30 days back), end time is LATEST date, and duration. (allowable diffs: Y = years, D = days, MM = minutes, S = seconds)
time_config: "LATEST-30D/LATEST/P1D"

Sub-daily periods are also supported.

time_config: "2000-01-01T00:00:00Z/DETECT/PT5M"

Note: Forced date behavior

Forcing All values start_date, end_date(with date values or LATEST), and period will prevent any detection. Periods.lua will set a single period with the start/end/period provided. There will be no gap detection. 

There will be gap detection when only forcing a start_date or a end_date.  Providing only the start_date will override the start date of the first date from detection. Providing only the end_date will override the end date of the last date from detection. 

Note: The period detection is determined by the first two intervals in the image archive for the given layer. Time detection may not be accurate if there are less than three files or if they are not continuous.