Quote from: Wiss on June 28, 2018, 08:52:56 PM

Here an other example (ETH/BTC on bittrex exchange time +2h):

28-06 22:47:03 FINE Added Streamdata: Time : 22:47:02.00000267 Price: 0.07155973 Name: BTC-ETH Nounce:35404 Ordertype: BUY Filltype: null
28-06 22:47:05 FINE Added Streamdata: Time : 22:47:05.00000080 Price: 0.07155974 Name: BTC-ETH Nounce:35406 Ordertype: BUY Filltype: null
28-06 22:47:10 FINE Added Streamdata: Time : 22:47:10.00000110 Price: 0.07155976 Name: BTC-ETH Nounce:35411 Ordertype: BUY Filltype: null
28-06 22:47:11 FINE Added Streamdata: Time : 22:47:11.00000110 Price: 0.07155976 Name: BTC-ETH Nounce:35412 Ordertype: BUY Filltype: null
28-06 22:47:19 FINE Added Streamdata: Time : 22:47:18.00000830 Price: 0.07155973 Name: BTC-ETH Nounce:35419 Ordertype: SELL Filltype: null
28-06 22:47:19 FINE Added Streamdata: Time : 22:47:18.00000830 Price: 0.07155974 Name: BTC-ETH Nounce:35419 Ordertype: SELL Filltype: null
28-06 22:47:22 FINE Added Streamdata: Time : 22:47:21.00000783 Price: 0.07155976 Name: BTC-ETH Nounce:35421 Ordertype: BUY Filltype: null
28-06 22:47:22 FINE Added Streamdata: Time : 22:47:21.00000703 Price: 0.07141003 Name: BTC-ETH Nounce:35421 Ordertype: BUY Filltype: null

this is to complete stream of the 1 min candle of 22:47:000 - 22:47.999

Tradingview shows a candle with the following value:
Open -->0.07155973 (correct)
High --> 0.07155976 (correct)
Low --> 0.07141003 (correct)
Close -->0.07155976 (NOT CORRECT)
because there was one additional tick with an price of 0.07141003 so the close must be 0.07141003

the strange thing is that tradingview considers the 0.07141003 as low but not as close!

You should order the trades by time. Look at last two trades. Sometimes trades does not comes in order...