That is fine. what about the high and low values. What is the time frame which we are receiving these values
how do we calculate the open and closed price knowing that we have more than 15 ticks per millise...

Best Answer
-
As @Gurpreet said, Tick History can offer you the intraday dataset.
Otherwise, you have to create a function that calculates the OHLC of each interval.
If you already capture every single ticks to your database, then it is easier to do the calculation from the database.
Every price or quote ticks have their time fields. For example, the quote tick from forex has Quote Time "QUOTIM" field.
name="AUD="
FieldEntry fid="22" name="BID" dataType="Real" value="0.7982"
FieldEntry fid="393" name="PRIMACT_1" dataType="Real" value="0.7982"
FieldEntry fid="25" name="ASK" dataType="Real" value="0.7986"
FieldEntry fid="275" name="SEC_ACT_1" dataType="Real" value="0.7986"
FieldEntry fid="875" name="VALUE_DT1" dataType="Date" value="16 FEB 2018"
FieldEntry fid="1010" name="VALUE_TS1" dataType="Time" value="09:09:00:000:000:000"
FieldEntry fid="5" name="TIMACT" dataType="Time" value="09:09:00:000:000:000"
FieldEntry fid="11" name="NETCHNG_1" dataType="Real" value="0.0039"
FieldEntry fid="17" name="ACTIV_DATE" dataType="Date" value="16 FEB 2018"
FieldEntry fid="32" name="ACVOL_1" dataType="Real" value="49175"
FieldEntry fid="56" name="PCTCHNG" dataType="Real" value="0.49"
FieldEntry fid="114" name="BID_NET_CH" dataType="Real" value="0.0039"
FieldEntry fid="115" name="BID_TICK_1" dataType="Enum" value="2"
FieldEntry fid="134" name="MID_PRICE" dataType="Real" value="0.7984"
FieldEntry fid="135" name="MID_NET_CH" dataType="Real" value="0.0038"
FieldEntry fid="211" name="NUM_BIDS" dataType="Real" value="49175"
FieldEntry fid="270" name="ACT_TP_1" dataType="Enum" value="27"
FieldEntry fid="831" name="CTBTR_1" dataType="Rmtes" value="RBS "
FieldEntry fid="836" name="CTB_LOC1" dataType="Rmtes" value="LON"
FieldEntry fid="841" name="CTB_PAGE1" dataType="Rmtes" value="RBSL"
FieldEntry fid="1025" name="QUOTIM" dataType="Time" value="09:09:00:000:000:000"
. . .You should use the time field when you do the interval cut-off.
0
Answers
-
Could you please elaborate more on the question or the issue you are trying to resolve?
Usually, you don't have to calculate the open and closed price as there are Opening Price (OPEN_PRC) field and Historic Close (HST_CLOSE) field.
0 -
That is fine. what about the high and low values. What is the time frame which we are receiving these values
0 -
There are TODAY'S HIGH (HIGH_1) and TODAY'S LOW (LOW_1) fields.
HIGH_1 and LOW_1 will update in real-time when there are new high or new low trades during trading hours.
0 -
Thanks but we need to calculate the OHLC price for 1 minute time frame, 5 minute time frame etc. How can we do that from the data we receive?
0 -
Are you trying to create an Intraday Minute Charts? Which means you want OHLC of each minute interval, not the OHLC of the day, right?
0 -
Yes we are: m1, m5, m15, H1, H4, H8, H12, D1, W1, M1, Y1
We will do it at database level, but thing is that we also have the historic price service and our calculations need to match exactly you historic periods.
0 -
@liyarthomas Thomson Reuters Tick History will readily offer a data set like that. It has a REST interface to access that data. It is however a separate service from the Elektron real time.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 650 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛