All Opmantek applications that handle time-series data use a common mechanism for parsing start and end times, which supports a large number of different formats listed below.

Starting with opEvents 2.0.4, Time zone specifications are also supported.

Default Format

The default format is the specific "DD-MON-YYYY HH:MM:SS", which you will have seen already in the Quick Search field. The default timezone is the server's local timezone (or the configured timezone as per omkd_display_timezone - available in opEvents releases 2.0.4 and newer).

Absolute Date Formats

• Dow, dd Mon yy
• Dow, dd Mon yyyy
• Dow, dd Mon
• dd Mon yy
• dd Mon yyyy
•  Month day{st,nd,rd,th}, year
•  Month day{st,nd,rd,th}
• Mon dd yyyy
• yyyy/mm/dd
• yyyy-mm-dd
• yyyy/mm
• mm/dd/yy
• mm/dd/yyyy
• mm/yy

Relative Date Formats

• count "days"
• count "weeks"
• count "months"
• count "years"
• Dow "after next"
• Dow "before last"
• "next" Dow
• "tomorrow"
• "today"
• "yesterday"
• "last" dow
• "last week"
• "now"
• "now" "+" count units
• "now" "-" count units
• "+" count units
• "-" count units
•  count units "ago"

Absolute Time Formats

• hh:mm:ss[.ddd]
• hh:mm
• hh:mm[AP]M
• hh[AP]M
• hhmmss[[AP]M]
• "noon"
• "midnight"

Relative Time Formats

• count "minutes" (count can be franctional "1.5" or "1 1/2")
• count "seconds"
• count "hours"
• "+" count units
• "-" count units
• count units "ago"

Timezone Specifications

The underlying date and time parser understands primarily the formats "GMT+H", "GMT+HHMM", "+HHMM" (and the corresponding variants with "-"), and a very limited subset of Timezone names; Starting with opEvents version 2.0.4 we've extended this to also understand the full set of flavours from the iso8601 standard and the TZ database (aka the Olson TZ database).

This means that you can use timezone declarations like "Australia/Brisbane", "+04:30" or "CET" - but please note that the abbreviated versions are not guaranteed to be unique and unambiguous!