Investigating the effect of oil spills on the environment and public health.
Brought to you by GRIIDC GoMRI
Reset the form to the default values.
Or, bypass this web page and do time conversions from within a computer program.
Notes about the Time Converter
The first word can be (upper or lower case):
ms, msec, msecs, millis, millisecond, milliseconds,
s, sec, secs, second, seconds,
m, min, mins, minute, minutes,
h, hr, hrs, hour, hours,
d, day, days,
mon, mons, month, months,
yr, yrs, year, or years.
"since" is required.
The time can be any time in the format YYYY-MM-DDThh:mm:ss.sssZ,
where Z is 'Z' or a ±hh or ±hh:mm offset from the Zulu/GMT time zone.
If you omit Z and the offset, the Zulu/GMT time zone is used.
Separately, if you omit .sss, :ss.sss, :mm:ss.sss, or Thh:mm:ss.sss, the
missing fields are assumed to be 0.
So another example is "hours since 0001-01-01".
Technically, ERDDAP does NOT follow the CF standard when converting "years since"
and "months since" time values to "seconds since". The CF standard defines a
year as a fixed, single value: 3.15569259747e7 seconds. And CF defines a month
as year/12. Unfortunately, most/all datasets that we have seen that use
"years since" or "months since" clearly intend the values to be calendar years
or calendar months. For example, "3 months since 1970-01-01" is usually intended
to mean 1970-04-01. So, ERDDAP interprets "years since" and "months since" as
calendar years and months, and does not strictly follow the CF standard.
How ERDDAP Deals with Time