Iso 8601 Utc

  1. Iso 8061
  2. Iso 8601 Utc Converter
  3. Iso 8601 Utc Format


ISO 8601 is a date and time notation format defined by ISO as an international standard. The date and time are connected by 'T' and written. The time zone is expressed as '+09:00' as the difference time from UTC, and in the case of UTC, it is expressed as 'Z'. Separate seconds and milliseconds with a comma (,) or dot (.). Utc was formerly used as the international civil time standard, now superseded in that function by Coordinated Universal Time (UTC). ISO 8601 - Wikipedia ISO 8601 is an international standard covering the exchange of date- and time-related data.

Description of the illustration to_utc_timestamp_tz.eps


Iso 8061

The SQL function TO_UTC_TIMESTAMP_TZ takes an ISO 8601 date format string as the varchar input and returns an instance of SQL data type TIMESTAMP WITH TIMEZONE. It normalizes the input to UTC time (Coordinated Universal Time, formerly Greenwich Mean Time). Unlike SQL function TO_TIMESTAMP_TZ , the new function assumes that the input string uses the ISO 8601 date format, defaulting the time zone to UTC 0.

A typical use of this function would be to provide its output to SQL function SYS_EXTRACT_UTC, obtaining a UTC time that is then passed as a SQL bind variable to SQL/JSON condition JSON_EXISTS, to perform a time-stamp range comparison.

This is the allowed syntax for dates and times:

  • Date (only): YYYY-MM-DD

  • Date with time: YYYY-MM-DDThh:mm:ss[.s[s[s[s[s[s]]]]][Z (+-)hh:mm]


  • YYYY specifies the year, as four decimal digits.

  • MM specifies the month, as two decimal digits, 00 to 12.

  • DD specifies the day, as two decimal digits, 00 to 31.

  • hh specifies the hour, as two decimal digits, 00 to 23.

  • mm specifies the minutes, as two decimal digits, 00 to 59.

  • ss[.s[s[s[s[s]]]]] specifies the seconds, as two decimal digits, 00 to 59, optionally followed by a decimal point and 1 to 6 decimal digits (representing the fractional part of a second).

  • Z specifies UTC time (time zone 0). (It can also be specified by +00:00, but not by –00:00.)

  • (+-)hh:mm specifies the time-zone as difference from UTC. (One of + or is required.)

For a time value, the time-zone part is optional. If it is absent then UTC time is assumed.

No other ISO 8601 date-time syntax is supported. In particular:

  • Negative dates (dates prior to year 1 BCE), which begin with a hyphen (e.g. 2018–10–26T21:32:52), are not supported.

  • Hyphen and colon separators are required: so-called “basic” format, YYYYMMDDThhmmss, is not supported.

  • Ordinal dates (year plus day of year, calendar week plus day number) are not supported.

  • Using more than four digits for the year is not supported.

Supported dates and times include the following:

  • 2018–10–26T21:32:52

  • 2018-10-26T21:32:52+02:00

  • 2018-10-26T19:32:52Z

  • 2018-10-26T19:32:52+00:00

  • 2018-10-26T21:32:52.12679

Unsupported dates and times include the following:

  • 2018-10-26T21:32 (if a time is specified then all of its parts must be present)

  • 2018-10-26T25:32:52+02:00 (the hours part, 25, is out of range)

  • 18-10-26T21:32 (the year is not specified fully)

Previous PageNext Page
ISO 8601 Formatting Symbols

The following list explains the formatting symbols that are used tonotate the ISO 8601 dates, time, datetime, durations, and interval values:


specifies a number that represents the number of years, months, or days


indicates that the duration thatfollows is specified by the number of years, months, days, hours, minutes,and seconds


indicates that a time value follows.Any value with a time must begin with T.

Time values that are read by theextended notation informats that begin with the characters E8601 must usean uppercase T.

indicates that the duration isspecified in weeks.


indicates that the time valueis the time in Greenwich, England, or UTC time.

+ -

the + indicates the time zoneoffset to the east of Greenwich, England. The - indicates the time zone offsetto the west of Greenwich, England.


specifies a four-digit year


as part of a date, specifies a two-digit month, 01 - 12


specifies a two-digit day, 01 - 31


specifies a two-digit hour, 00 - 24


as part of a time, specifies a two-digit minute, 00 - 59


specifies a two-digit second, 00 - 59


specifies an optional fraction of a second usingthe digits 0 - 9:


use 1 - 3 digits for values read by the $N8601B informat and the $N8601E informat


War thunder best ship nation. use 1 - 6 digits for informat other than the $N8601B informat and the$N8601E informat


indicates that a year value proceedsthis character in a duration


as part of a date, indicatesthat a month value proceeds this character in a duration


indicates that a day value proceedsthis character in a duration


indicates that an hour valueproceeds this character in a duration


as part of a time, indicatesthat a minute value proceeds this character in a duration


indicates that a seconds valueproceeds this character in a duration

Writing ISO 8601 Date, Time, and Datetime Values

SAS uses the formats in the following table to write date, time, anddatetime values in the ISO 8601 basic and extended notations from SAS date,time, and datetime values.

Formats for Writing ISO 8601 Dates, Times, and Datetimes
Date, Time, or DatetimeISO 8601 Notation ExampleFormat
Basic Notations
Time with time zonehhmmss+ -hhmm155300+0500B8601TZw.d

Convert to local time with time zonehhmmss+ -hhmm155300+0500B8601LZw.d
Datetime with timezoneyyyymmddThhmmss+ -hhmm20080915T155300+0500B8601DZw.d


Write the date from a datetimeyyyymmdd
Extended Notations
Time with time zonehh:mm:ss.ffffff+ -hh:mm15:53:00+05:00E8601TZw.d
Convert to local time with time zonehh:mm:ss.ffffff+ -hh:mm15:53:00+05:00E8601LZw.d
Datetime with time zoneyyyy-mm-ddThh:mm:ss.nnnnnn+ -hh:mm2008-09-15T15:53:00+05:00E8601DZw.d
Write the date from a datetimeyyyy-mm-dd

An asterisk ( * ) used in place of a date or timeformatted value thatis out-of-range.

Writing ISO 8601 Duration, Datetime, and Interval Values

Duration, Datetime, and Interval Formats

SAS writes duration, datetime, and interval values from character datausing these formats:

Time ComponentISO 8601 NotationExampleFormat
Duration - Basic NotationPyyyymmddThhmmssfffP20080915T155300$N8601BA

Duration - Extended NotationPyyyy-mm-ddThh:mm:ss.fffP2008-09-15T15:53:00$N8601EA

Duration - Basic and Extended NotationPnYnMnDTnHnMnSP2y10m14dT20h13m45s$N8601B




PnW (weeks)P6w$N8601B


Interval - Basic NotationyyyymmddThhmmssfff/yyyymmddThhmmssfff20080915T155300/20101113T000000$N8601BA


Interval- Extended Notationyyyy-mm-ddThh:mm:ss.fff/yyyy-mm-ddThh:mm:ss.fff2008-09-15T15:53:00/2010-11-13T00:00:00$N8601EA


Datetime-Basic NotationyyyymmddThhmmss.fff+ -hhmm20080915T155300$N8601BA

(all blank)




Datetime-Extended Notationyyyy-mm-ddThh:mm:ss.fff+ -hhmm2008-09-15T15:53:00



(all blank)




Writing Omitted Components

An omitted component can be represented by a hyphen ( - ) oran x in the extended datetime form yyyy-mm-ddThh:mm:ss and in the extended duration formPyyyy-mm-ddThh:mm:ss.

Omitted components in the durations formPnYnMnDTnHnMnS aredropped, they do notcontain a hyphen or x. For example, P2mT4H.

The following formats write omitted components that use the hyphen andthe x:

FormatDatetime FormDuration FormExamples



Iso 8601 Utc Converter

Datetime values with omitted components that are formattedwith either the $N8601B format or the $N8601BA format are formatted in theextended notation using the hyphen for omitted components to ensure accuratedata. For example, when the month is an omitted component, the value 2008---15is written and not 2008-15.

The extended notation with hyphens is also used in place of the basicnotation if a duration is formatted by using the $N8601BA format. Using thesame date, P2008---15 is written and not P2008-15.

Writing Truncated Duration, Datetime, and Interval Values

Duration, datetime, or interval values can be truncated when one ormore lower order values is 0 or is not significant. When SAS writes a truncatedvalue using the formats $N8601B, $N8601BA, $N8601E, and $N8601EA, the displayof the value stops at the last non-missing component.

When you format a truncated value by using either the $N8601H formator the $N8601EH format, the lower order components are written with a hyphen.When you format a truncated value by using the $N8601X format or the $N8601EXformat, the lower order components are written with an x.

Iso 8601 Utc Format

The following examples show truncated values:







Normalizing Duration Components

When a value for a duration component is greater than the largest standardvalue for a component, SAS normalizes the component except when the durationcomponent is a single component. The following table shows examples of normalizedduration components:

DurationExtended Normalized Duration

If a component contains the largest value, such as 60 for minutesor seconds, SAS normalizes the value and replaces the value with a hyphen.For example, pT12:60:13becomes PT13:-:13.

Thirty days is used to normalize a month.

Dates and times in a datetime value that are greater than the standardvalue for the component are not normalized. They produce an error.

Fractions in Durations, Datetime, and Interval Values

Ending components can contain a fraction that consists of a period ora comma, followed by one to three digits. The following examples show theuse of fractions in duration, datetime, and interval values:

Iso 8601 utc python




Previous PageNext PageTop of Page