Skip to main content
9 events
when toggle format what by license comment
Mar 29, 2016 at 10:19 comment added Peque Thanks for taking the time to answer and for your comments.
Mar 22, 2016 at 0:02 comment added Richard at NorgateData Another reference point: Thomson Reuters, in their premium desktop product Eikon, use timestamp-on-close for intraday/daily/weekly/monthly/quarterly/yearly bars. Source: A business contact that uses that platform.
Mar 21, 2016 at 9:57 comment added Richard at NorgateData Also note that some data points actually arrive some nanonseconds/millseconds/seconds/minutes after "the closing bell". For example, the official close of NYSE:GE is transmitted to the tape somewhat after 16:00:00.00000 New York time due to the way the DMMs aggregates various trades for the official close.
Mar 21, 2016 at 9:50 comment added Richard at NorgateData *ending last day in March
Mar 21, 2016 at 9:39 comment added Richard at NorgateData The "de facto" standard relates to my experience as a daily data vendor and how data is presented to us from different institutional-level data feeds. For various items, the timestamp given is the close timestamp. It may be that we are biased to longer timeframes data (such as weekly/quarterly). In accounting terms, the fiscal ending timestamp is the appropriate one to use (eg. companies that have a fiscal year boundary of March would refer to the current fiscal year as the "2016 fiscal year").
Mar 21, 2016 at 9:29 comment added Peque Also, it seems that NinjaTrader disagrees with you in "There is no particular advantage to either method". It seems for them it is better to use on-close "to plot multiple series of differing time frames within a single chart all accurately synchronized to time".
Mar 21, 2016 at 9:10 comment added Peque Could you please back-up your "is the de-facto standard" argument with some references/links? As you can see in the references section in my question, 3 tools out of 4 that I tried where using timestamp on open, rather than on close.
Mar 21, 2016 at 9:02 history edited Richard at NorgateData CC BY-SA 3.0
added 226 characters in body
Mar 21, 2016 at 8:56 history answered Richard at NorgateData CC BY-SA 3.0