Liquidity Cartography [JOAT]JOAT Liquidity Cartography
Introduction
JOAT Liquidity Cartography is an open-source liquidity mapping overlay built to organize where price has swept obvious pools, where imbalance still exists, and where repricing blocks remain active.
It combines prior-day and prior-week references, equal-high and equal-low clustering, sweep-state persistence, displacement logic, imbalance arrays, repricing block arrays, and confluence scoring.
The problem it solves is fragmented liquidity analysis.
Many traders watch prior highs and lows separately from fair value gaps, separately from equal highs and lows, and separately from displacement.
This script turns those references into one coordinated chart map.
That makes it easier to judge whether the market is merely tapping a level, actually sweeping it, or accepting away from it with structure and participation.
The script is useful because it tracks the sequence, not just the level.
A prior-day low by itself is only a reference.
A sweep below it is more informative.
A sweep followed by displacement and structure recovery is a different condition again.
Liquidity Cartography is built around those transitions.
The box system is managed over time.
Zones are extended, aged, and deleted when invalidated or expired.
That keeps the chart focused on currently relevant liquidity rather than permanent drawings.
Core Concepts
1. Daily and Weekly Reference Liquidity
The script tracks PDH, PDL, PWH, and PWL.
These are the major reference pools used to judge whether price is probing obvious liquidity.
= request.security(syminfo.tickerid, "D", [high , low ], lookahead = barmerge.lookahead_on)
= request.security(syminfo.tickerid, "W", [high , low ], lookahead = barmerge.lookahead_on)
2. Equal-High and Equal-Low Tracking
Confirmed pivots are compared in ATR terms to identify clustered highs and lows.
3. Sweep-State Persistence
Sweeps remain active for a configurable confirmation window.
That allows follow-through logic to validate the narrative.
4. Displacement Validation
The script checks whether the reaction away from a pool is meaningful through body expansion and gap behavior.
5. Imbalance Management
Imbalance zones are stored and extended as long as they remain active.
6. Repricing Block Management
Order-block style repricing areas are created after structural breaks and managed over time.
7. Filter Stack
Trend, RVOL, RSI, and session filters can refine signal quality.
8. Confluence Scoring
The indicator counts alignment across the active liquidity narrative.
Features
Prior-day and prior-week levels: major reference pools are tracked
Equilibrium levels: daily and weekly range centers are shown
Equal-high / equal-low detection: clustered pools are identified
Sweep persistence: active sweep context remains available for confirmation
Displacement checks: strong rejection is separated from weak noise
Imbalance boxes: active FVG-style zones extend until mitigation or expiry
Repricing blocks: revisit zones are stored and managed
Filter stack: trend, RVOL, RSI, and session alignment are available
Confluence scoring: current liquidity alignment is summarized
Dashboard: active pool, trend, confluence, and signal state are displayed
Input Parameters
Reference Levels:
Show Prior Day Levels
Show Prior Week Levels
Show Equilibrium
Track Weekly Sweeps
Sweep / Zone Logic:
Structure Length
Sweep Reset Bars
Zone Extension
Equal Pool Tolerance ATR
Zone Max Age
History Limits
Validation:
Require Displacement
Displacement Multiplier
Use Trend Filter
Use RVOL Filter
Use RSI Filter
Use Session Filter
How to Use This Indicator
Step 1: Identify the active daily or weekly liquidity pool.
Step 2: Check whether price only touched the pool or actually swept it.
Step 3: Look for displacement and structure response after the sweep.
Step 4: Watch active imbalances and repricing blocks for later revisits.
Step 5: Use the confluence count to separate weak narratives from stronger ones.
Indicator Limitations
Obvious liquidity pools can be tapped or swept multiple times before direction resolves
Object-heavy overlays may appear dense on low timeframes if many zones remain active
Pivot-based pool detection confirms after the swing completes, which is intentional non-repainting behavior
Zones are analytical references, not guarantees of reversal or continuation
Originality Statement
This script is original in how it combines sweep persistence, equal-pool detection, imbalance inventory, repricing blocks, and confluence scoring into one coordinated liquidity framework.
The components are integrated because they all describe the same process:
price probing liquidity, taking it, and either failing or accepting beyond it.
Disclaimer
This indicator is provided for educational and informational purposes only.
It is not financial advice.
Liquidity reactions can fail.
Sweeps can repeat.
No level or zone guarantees a directional outcome.
Always use independent judgment and risk management.
Best Use Cases
Mapping where obvious daily and weekly liquidity is likely resting
Studying how price behaves after a confirmed sweep
Tracking whether displacement and imbalance support the sweep narrative
Marking revisit zones after structural repricing
Interpretation Notes
A sweep by itself is only the beginning of the story.
The more useful sequence is sweep, displacement, structural response, and active zone support.
Equal-high and equal-low references are helpful because they often identify where liquidity may accumulate before the sweep occurs.
The confluence score should be interpreted as a narrative-strength read, not a promise of reversal.
Publication Notes
This script is intended to be published with a clean chart that clearly shows the active liquidity pool, the current sweep state, and one or two relevant active zones.
Do not overload the publication chart with unrelated drawings.
The value of the visual example should come from clarity rather than chart decoration.
-Made with passion by jackofalltrades
Chart Reading Framework
1. Start with the active daily or weekly pool.
2. Determine whether price only touched or truly swept the pool.
3. Check displacement, break state, and confluence.
4. Review active imbalances and repricing blocks for the next revisit path.
5. Use the dashboard to verify whether the liquidity narrative is strengthening or fading.
Why This Matters
Liquidity logic becomes much more useful when it is organized as a process instead of a list of disconnected levels.
This indicator is meant to help the user see that process clearly.
Open-Source Notes
This script is published open source so users can inspect how sweep persistence, imbalance management, and zone aging are handled.
Who This Is For
This indicator is for traders who want a structured liquidity map rather than isolated levels.
It is especially useful for users who think in terms of sweeps, repricing, and revisit zones.
Summary
JOAT Liquidity Cartography turns scattered liquidity references into one organized live framework.
Its main value is clarity.
Additional Notes
The strongest use of this script comes from following the sequence of events rather than reacting to a single box or line in isolation.
Clean publication images should make that sequence obvious.
Pine Script® indicator






