Inconsistence between trading conditions and polygon 1min bars

Discussion in 'Data Sets and Feeds' started by foxden, May 28, 2025 at 12:40 PM.

  1. foxden

    foxden

    Based on https://polygon.io/glossary/conditions-indicators, trade condition P (22, Prior Reference Price) should be used to update high/low price. But here is the example that it does not follow:

    the trade is:

    upload_2025-5-28_12-5-50.png

    but interval does not show this price (59.00) as high. Note that I define BAR_TIME as end of bar time.

    upload_2025-5-28_12-2-31.png

    A similar problem happens to condition O. For CTS, it is defined as "Market Center Opening Trade" and UTP is defined as Opening Prints. https://polygon.io/glossary/trade-conditions define 17 as CTS O condition "Market Center Opening Trade". And https://polygon.io/glossary/conditions-indicators define 25 as O with UTP definition. What I see is, this price is not used for open price or for volume update (the documents says yes to volume at least). For CTS, in this doc https://www.ctaplan.com/publicdocs/ctaplan/CTS_Pillar_Output_Specification.pdf page 82, it defines "O" as Market Center Opening Trade", which means 17 at Polygonio, and it should be used to update all bar fields.

    Here is the bar data. And the last column is the end of bar time.

    upload_2025-5-28_12-26-53.png

    with trades at that time:

    upload_2025-5-28_12-27-46.png

    Can anyone shed any light on these issues?
     
  2. SunTrader

    SunTrader

    Your bar time (set as 24 hour time sequencing) in first two instances are showing -04:00 as close - shouldn't it be 16:00?

    Anyway this is "all greek to me".
     
  3. foxden

    foxden

    "-04:00" is EDT or US eastern summer time zone. And it is 1 min bar not daily bar.
     
  4. qlai

    qlai

    What does the “correction” field mean? I used to work for a major market data provider and I can tell you that it is not straight forward. Ticks get corrected which makes keeping track of daily high/low a bit tricky. Fortunately, most systems don’t care about infra-day high/low or they just calculate them based upon “last eligible” trades.
    To report daily high/low correctly, we had to have logic to search for previous eligible tick, which some vendors might not bother doing. Thankfully, most professional data consumers only cared about daily values.
     
  5. SunTrader

    SunTrader

    Then what is 15:17:00?

    And yes I know it is a 1 min bar.
     
  6. foxden

    foxden

    the correction code of 12 trade is as below. It is a price correction not volume correction. Even if it is point of time and polygon didn't go back to fix the data error, the volume should be there.

    upload_2025-5-30_15-51-39.png

    But if you look at all trades at that intervals, the interval says volume 2600 and trades 6. So clearly the first trade is not included.

    upload_2025-5-30_15-47-2.png