The Setup
The Houston Ship Channel corridor — the bounding box 29.55°N to 29.85°N, 94.7°W to 95.3°W covering the channel, Galveston Bay approach, and the refining and petrochemical berths along it — logged 11,465 AIS position reports in the 24 hours ending 2026-08-19, out of 717,337 tracked worldwide in the same window. That is 1.6% of global vessel-position traffic moving through one US industrial waterway in a single day, more than New York Harbor's 6,968 positions and ahead of the Los Angeles/Long Beach complex's 7,286, in the same 24 hours.
The Chain
Locus scores 130 H3 cells across the Houston metro. Each carries a composite score assembled from eight weighted signal groups — demographics, accessibility, amenity demand, business vitality, economic strength, safety/environment, population momentum, and development pipeline — and each cell's signal_scores payload lists Sobol sensitivity indices for exactly those eight groups and no others. None references vessel density, port throughput, or any AIS-derived measure. The five highest-composite cells in the metro, all scoring 62, sit in the 88446c/88446ca8/88446ca9 H3 neighborhood directly adjacent to the Ship Channel. Their scores are driven mostly by developmentPipeline (Sobol total-order sensitivity 0.77–0.83, the single dominant factor in four of the five) and economicStrength — but the development_pipeline sub-score itself sits at just 33 out of 100 in every one of them, and nothing feeding that number draws on the 11,465 daily position reports moving through the same five cells.
The Implication
The Ship Channel corridor is one of the highest-value industrial waterfront strips in the country, and Overwatch already measures its traffic volume in near-real time. Locus's composite score for the same five-mile stretch has no path for that measurement to arrive at all. A refinery expansion, a new terminal berth coming online, a sustained congestion event, or a multi-week drop in vessel calls — any of which would move real industrial CRE demand in that corridor — would have to first surface as a permit filing or a civic record before it could touch the score. The traffic itself, visible the same day it happens in a different Axiom product, isn't wired into the pipeline that scores the land next to it.
What to Watch
Whether Houston's roughly 1.6%-of-global-traffic share holds as a stable baseline or swings with petrochemical shipping seasonality and refinery turnaround schedules. A single-digit-percentage share of global AIS traffic concentrated in one metro's waterway is unusual enough that tracking it weekly for a quarter would show whether it's a structural feature of the corridor or a one-day read. If it moves by more than roughly 20% week over week, that alone is an argument for treating channel-level vessel density as a live scoring input rather than a one-time observation.
Limitations
Vessel density in a channel is a proxy for activity, not for investment — heavy tanker traffic can mean a terminal running at capacity, or it can mean a weather delay or channel obstruction backing vessels into a queue, and a single day's position count can't distinguish those cases. The bounding box used here is a rectangle drawn around the channel and bay approach, not the channel's actual navigable geometry, so some of the 11,465 positions are vessels anchored in Galveston Bay rather than transiting the channel itself. And a one-day comparison against New York and LA/Long Beach establishes only that Houston was the busier corridor on this specific day — not that it reliably is.
--- Data as of 2026-08-19. Sources: Overwatch `ais_positions` (24h trailing, Houston Ship Channel bounding box), Locus `cell_scores` (metro_slug=houston, 130 cells, latest computed_at 2026-08-19).