question about nasdaq basic chain quote time field
Hello, everyone,
When decoding nasdaq basic chain, I want to extract the quote real time from field dictionary. From the following document nasdaq basic RICs, I can find FID: 3855 named QUOTIM_MS in RefreshMsg and UpdateMsg with values like
So How can I interpret the UInt value here ? And How can I convert the QUOTIM_MS time to real time representation? Many thanks, expecting all's reply.
Best Answer
-
It is a time-of-day value. It is milliseconds since midnight, UTC. In other words: a value between 0 and 86400000.
In theory, the value may be from another day than the current. However, according to the document you've referenced, the value gets blanked out at market close. Therefore you can always safely assume that the value refers to the current UTC day.
0
Answers
-
Thanks for your reply. Now I can understand how to interpret the field.
But I have two more question. The first is about the field 'TRADE_DATE'
FieldEntry fid="16" name="TRADE_DATE" dataType="Date" value="22 MAR 2019"
is it also a UTC date?
Second, I found in logs that QUOTIM_MS's value could be quite small, like this:
FieldEntry fid="3855" name="QUOTIM_MS" dataType="UInt" value="73"
if far less than the offset in milliseconds between timezone EST and GMT.
So if field TRADE_DATE with value "22 MAR 2019" and QUOTIM_MS with value "73", what is the corresponding EST time ? Is it "2019-03-21 20:00:00" or "2019-03-22 00:00:00" ?
Expecting anyone that may help, thank you.
0 -
Your 4 hours difference got me confused until I realized that the US east coast is already using summer time.
Your example: If you are in New York on March 21st 2019 and observe that the QUOTIM_MS field has a value of '73' then it effectively means "2019-03-22T00:00:00.073Z".
I don't know if you can marry QUOTIM_MS and TRADE_DATE. Better ask that as a new question. I'm not sure those two fields would always update in unison. If anything I would expect that QUOTIM_MS can be married to QUOTE_DATE.
But personally I don't see the need to marry QUOTIM_MS with anything. Current UTC day is implied.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛