Which observation does each display support?
Bookmap documents its heatmap as current and historical order-book liquidity, with separate volume dots, volume bars, and bid/ask lines. TradingView provides several chart views and a broker-connected DOM. Having a live DOM is not evidence that the same depth history is available to every chart, replay, or script.
| Research task | Bookmap | TradingView |
|---|
| Follow resting liquidity over time | Heatmap of the depth updates available from the connection. | Broker DOM shows available depth. Verify historical depth access separately from chart history. |
| Inspect executed volume | Volume dots and bars with configurable aggregation and filtering. | Volume bars and footprint distributions, with documented intrabar classification. |
| Review a past session | Replay suitable feed files containing recorded market data. | Bar Replay advances through available historical chart data. |
| Test a documented candle rule | Check the available data and study interface for that rule. | Pine studies can calculate rules from supported price and volume inputs. |
A volume dot is not a limit-order wall
Bookmap volume dots aggregate executed volume. Zoom, clustering, and minimum-display settings can change the visible grouping. A large dot therefore need not be a single large transaction. A bright heatmap area instead represents displayed resting liquidity; orders can be canceled before price reaches them. Neither display establishes trader identity or intent.
- TradingView footprints distribute volume across price rows and categorize buy/sell volume using intrabar price direction. The documentation says older history can use coarser intrabar intervals as finer data runs out. Do not assume its categories equal another feed's aggressor-side records.
- Compare volume units, price-row width, interval, filters, and classification before comparing delta. Equal total volume does not guarantee equal side allocation.
- Bookmap warns that when a feed lacks full depth, it can retain the last known values for price levels outside the updated range. A visible level may therefore require a freshness check.
- Repeated executions near a level can motivate an absorption hypothesis. OHLCV alone cannot establish the resting quantity, replenishment sequence, hidden orders, or reason for a cancellation.
The same OHLCV can conceal two different order books
Consider a hypothetical one-minute interval with four successive executions: 100 units at 100, 200 at 101, 300 at 99, and 400 at 100.50. Both cases below use those exact executions. Their candle is open 100, high 101, low 99, close 100.50, volume 1,000. No execution reaches 102.
- Any deterministic calculation using only these identical OHLCV inputs must return the same result for both cases. More elaborate chart coloring cannot recover which order-book history occurred.
- Even a complete record of the four executions would not reveal those unexecuted asks. The missing input is depth history, not a different moving-average setting.
- The example proves an information limit. It does not imply that the canceled quantity was spoofing or that either case predicts the next price.
| Observation | Case A | Case B |
|---|
| Executed volume | 100 + 200 + 300 + 400 = 1,000 | The same 1,000 units |
| Displayed asks at 102 | 500 units appear, remain briefly, then cancel within the minute. | No asks are displayed at 102 during the minute. |
| OHLCV output | 100 / 101 / 99 / 100.50 / 1,000 | 100 / 101 / 99 / 100.50 / 1,000 |
| Depth history needed | Updates at 102 reveal the appearance and cancellation. | Updates covering 102 establish the absence of that displayed quantity. |
What can you reproduce from OHLCV?
Use this checklist when translating an observation into a study. OHLCV means only open, high, low, close, and total volume for each bar. Additional datasets can support additional questions, but their availability must be checked explicitly.
- A reproducible example rule: after the bar closes, mark it when volume / mean volume of the previous 20 completed bars is at least 1.25, and (close - low) / (high - low) is at least 0.75. Exclude the current bar from the volume baseline.
- Assume the previous 20 volumes average 800. The example candle gives 1,000 / 800 = 1.25 and (100.50 - 99) / (101 - 99) = 0.75, so both inclusive thresholds pass. It passes in both order-book cases.
- At volume 999, the ratio is 1.24875 and the rule fails. At close 100.49, the range fraction is 0.745 and it fails. If the baseline is zero, history is incomplete, inputs are missing, or high equals low, return no decision.
- This rule describes relative activity and closing location. Calling its result a liquidity wall or confirmed absorption would add a claim the inputs cannot support. No trading performance is asserted.
| Observation or rule | From OHLCV alone? | Required boundary |
|---|
| Close above a prior high | Yes | Define the lookback, session, and completed-bar timing. |
| Volume relative to prior bars | Yes | Use comparable units; skip missing or zero baselines. |
| Close location within the bar range | Yes | A zero-range bar has no defined range fraction. |
| Exact executions at each price | No | Requires finer trade or price-level data. |
| Aggressor-side volume or delta | No | Requires side information or an explicitly labeled classification estimate. |
| Resting quantity and cancellations at 102 | No | Requires depth updates covering that level and time. |
| Position in an order queue | No | Requires appropriate order-level data and queue assumptions. |
Check the connection and the replay file before paying
Bookmap separates software access from data and brokerage services. Its connection table distinguishes depth coverage and supported features, and its documentation distinguishes backfill from data used in Replay. TradingView says DOM data comes from the broker and can differ from chart data. A platform subscription alone does not establish that both screens receive the same market observations.
- Record the exchange, exact contract or trading pair, provider, session, timezone, and live/delayed status. A continuous futures chart and an individual expiry are different comparison inputs.
- For Bookmap, confirm the depth levels, update coverage, and recording interval you need. Feed files (.bmf) contain recorded market data, including depth and best bid/offer, and open in Replay mode. Save a short sample and reopen it to check the needed interval and levels.
- Do not assume backfill shown before the connection started is automatically in the recording. Bookmap documents separate recording and export behavior. Check the resulting file rather than relying on what was once visible on screen.
- For TradingView, choose the historical start point and step Bar Replay forward. Its help page warns that server-side alerts and connected Paper Trading or broker orders still use realtime data. Those are separate from a replay practice workflow.
- Use a known event as an acceptance check: record its timestamp, price, traded quantity, and required depth changes. A replay that lacks the event cannot validate a rule depending on it. This page does not quote subscription prices or claim a live feed benchmark.
Carry the observable rule into Pineify
After deciding which observations your study needs, give Pineify the rule in plain language, the required inputs, and expected results for normal and boundary cases. For the OHLCV example above, specify completed bars, the prior-20-bar baseline, inclusive thresholds, and no decision on invalid inputs. Request a Pine draft and syntax diagnostics, then compare its marks with the expected cases in TradingView.
- Keep a depth-dependent study in a workflow that actually supplies its required history. Replacing missing depth with a price/volume proxy changes the study and should be labeled as a separate hypothesis.
- Syntax validation checks code structure; it does not prove feed equivalence, profitable results, or faithful reconstruction of a proprietary indicator.
