how to get GMT offset in Raw data request for version 2?

muneish.adya
muneish.adya Explorer
in TRTH

for version 2, I am using the following settings...

MessageTimeStampIn = GmtUtc

ReportDateRangeType = Range

ExtractBy = SingleByRic

however, I do not get the GMT offset in v2 rest api

RIC,Domain,Date-Time,Type,MsgClass/FID number,UpdateType/Action,FID Name,FID Value,FID Enum String,PE Code,Template Number,Key/Msg Sequence Number,Number of FIDs
03V1.DE,Market Price,2017-08-17T02:20:00.976588577Z,Raw,UPDATE,CLOSING_RUN,,,,3348,,16942,134

with same settings, I am getting GMT offset in version 1

#RIC,Date[G],Time[G],GMT Offset,Type,MSG/FID Number,Message Type,FID Name,FID Value,FID Enum String,PE Code,Template Number,RTL,Sequence Number,Source RIC,Number of FIDs
BNPP.PA,16-AUG-2017,01:25:20.865,+2,Raw-TAS,84,CORRECTION_PC,,,,8132,0,53584,6098,BNPP.PA,236

Tagged:

Best Answer

  • veerapath.rungruengrayubkul
    veerapath.rungruengrayubkul LSEG
    Answer ✓

    @muneish.adya

    Below is the related information in the Tick History v1 - v2 Comparison (June 2017). It seems that there is no GMT Offset column in V2. However, the Date-Time column includes timezone-offset notification if the client chooses to have the data display in
    local timezone.

    image

    If the MessageTimeStampIn = LocalExchangeTime, the Date-Time will be in Local Exchange Time with GMT Offset.

    #RIC,Domain,Date-Time,Type,MsgClass/FID number,UpdateType/Action,FID Name,FID Value,FID Enum String,PE Code,Template Number,Key/Msg Sequence Number,Number of FIDs
    ICBK.NS,Market Price,2016-07-26T05:05:53.313602012+0530,Raw,UPDATE,UNSPECIFIED,,,,5438,,6320,2

Categories