D5 Data file different format TRTHv1 <-> DSS
Hi all,
we are loading a daily D5 data file via the TRTHv1. I now checked the file in the new API and there are some differences in file size and in file content (see screenshot). Can you please advice if the same format is still availalbe via DSS and where we can find it?
This is the format we need:
#RIC,Date[G],Time[G],GMT Offset,Type,Last Bid,Last Ask,Average Trade,Cumulative Volume,Last Traded Price AED=D5,02-SEP-2016,08:18:11.000000,+0,Dealing,0,3.67295,,0, AED=D5,02-SEP-2016,10:04:49.000000,+0,Dealing,0,0,3.672950,2,3.67295 AED=D5,02-SEP-2016,10:04:50.000000,+0,Dealing,0,0,,0,3.67295 AED=D5,02-SEP-2016,11:34:35.000000,+0,Dealing,0,3.67295,,0,3.67295 AED=D5,02-SEP-2016,13:00:20.000000,+0,Dealing,0,0,3.672950,1,3.67295 AUD=D5,01-SEP-2016,21:53:49.000000,+0,Dealing,0.755,0.7553,,0,0.7552
Best Answer
-
Hi Philipp
In DSS (TRTH v2), data for D5 RICs will be tick-tick (TAS). The format of the new FXD5 is consistent with the standard exchange-by-day (or VBD) offering.
FXD5 data in TRTH v1 is 1 seconds conflated with summarized fields such as last trade price, aggregated 1 sec volumes.
FXD5 data in TRTH v2 is minus conflation, you will receive every trade and (best) quote messages from the Thomson Reuters Matching platform.
1 seconds FXD5 conflated data will not be supported in DSS (TRTH v2)
0
Answers
-
You have accepted the reply below now on your own? And not it looks like I have accepted it. Intersting approach in this forum.
0 -
Ok, now I have an explanation, why the current format is no longer available in TRTHv2 but still I see it as a problem, because this causes quiet some additional development work on our side. Can you please check if it is possible to deliver both formats in the future in parallel?
Can you please also provide some information or a generall overview about all the non compatible changes between TRTHv1 and TRTHv2. It is a frustrating approach to find out about these changes in a kind of reverse engineering process.
Thx in advance.
0 -
Thanks for the offer. It's fine like it is at the moment. We are tracking this separately. Thanks again!
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
- 684 Datastream
- 1.4K DSS
- 614 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
- 248 ETA
- 552 WebSocket API
- 37 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
- 639 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛