# Netting reference review

Reviewed October 4, 2026. Covers all 30 default MLB home venues in the site. Sources are official club pages and dated MLB/MiLB announcements; this research used no live Chrome session and decoded no stadium assets.

The machine-readable records are in [data/netting-reference-review.json](data/netting-reference-review.json). Each record preserves venue ID, source-model hash where compatible, published section labels, height datum, current-versus-historical status, unresolved evidence, and empty 3D registration anchors.

There are 27 live club coverage notices, one diagram-only reference, one historical numeric installation record, and one venue with current extent unresolved. Seven live notices publish numeric heights. **No park has a surveyed or independently verified 3D net footprint in this review.** A reachable club page is evidence of its published guidance; its copyright year is not an installation date.

| Park index | Venue | Evidence status | Source |
| --- | --- | --- | --- |
| 0 | Oracle Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/giants/ballpark/seat-map) |
| 1 | Chase Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/dbacks/ballpark/netting) |
| 2 | Truist Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/braves/ballpark/information/guide) |
| 3 | Oriole Park at Camden Yards | Published coverage; 3D pending | [Club reference](https://www.mlb.com/orioles/ballpark/seating-map) |
| 4 | Fenway Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/redsox/ballpark/netting) |
| 5 | Wrigley Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/cubs/ballpark/information/guide) |
| 6 | Rate Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/whitesox/ballpark/seat-map) |
| 7 | Great American Ball Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/reds/ballpark/netting) |
| 8 | Progressive Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/guardians/ballpark/netting) |
| 9 | Coors Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/rockies/ballpark/seating-chart) |
| 10 | Comerica Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/tigers/ballpark/seat-map) |
| 11 | Daikin Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/astros/ballpark/information/guide) |
| 12 | Kauffman Stadium | Diagram only; dimensions pending | [Club reference](https://www.mlb.com/royals/ballpark/seating-map) |
| 13 | Angel Stadium | Published coverage; 3D pending | [Club reference](https://www.mlb.com/angels/ballpark/netting) |
| 14 | Dodger Stadium | Published coverage; 3D pending | [Club reference](https://www.mlb.com/dodgers/ballpark/netting) |
| 15 | loanDepot park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/marlins/ballpark/information/guide) |
| 16 | American Family Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/brewers/ballpark/netting) |
| 17 | Target Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/twins/ballpark/seat-map) |
| 18 | Citi Field | 2017 dimensions; current review pending | [Club reference](https://www.mlb.com/mets/ballpark/information/guide) |
| 19 | Yankee Stadium | Published coverage; 3D pending | [Club reference](https://www.mlb.com/yankees/ballpark/netting) |
| 20 | Sutter Health Park | Current coverage unresolved | [Club reference](https://www.mlb.com/athletics/ballpark/seating-map) |
| 21 | Citizens Bank Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/phillies/ballpark/information/facts-figures-fun-features) |
| 22 | PNC Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/pirates/ballpark/seating-map/3d) |
| 23 | Petco Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/padres/ballpark/netting) |
| 24 | T-Mobile Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/mariners/ballpark/seat-map) |
| 25 | Busch Stadium | Published coverage; 3D pending | [Club reference](https://www.mlb.com/cardinals/ballpark/netting) |
| 26 | Tropicana Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/rays/ballpark/netting) |
| 27 | Globe Life Field | Published coverage; 3D pending | [Club reference](https://www.mlb.com/rangers/ballpark/seat-map) |
| 28 | Rogers Centre | Live notice; old labels require review | [Club reference](https://www.mlb.com/bluejays/ballpark/netting) |
| 29 | Nationals Park | Published coverage; 3D pending | [Club reference](https://www.mlb.com/nationals/ballpark/seatmap) |

## Corrections to use during integration

- White Sox and Rangers now have current section notices rather than only an old announcement or unresolved guide.
- The Mets installation announcement took effect July 14, 2017. Current numeric coverage still needs verification; the 2026 game report confirms a support pole exists, not its complete surveyed placement.
- Toronto's live notice retains the section labels from its 2020 announcement. Reconcile those labels against the rebuilt lower bowl before using them as current geometry.
- Sacramento is venue 2529. Its 2019 River Cats notice describes an increase in backstop height, not an absolute top elevation. Oakland's section numbers, netting, and model cannot be transferred there.
- Kauffman's current wall and seating configuration requires a 2026 edition check. [Official change announcement](https://www.mlb.com/royals/press-release/royals-announce-new-dimensions-for-kauffman-stadium).

Numeric values and full coverage summaries stay in the JSON to avoid duplicating installation notices. Preserve their datums: some heights are relative to the field, one is relative to the warning track, and Yankee measurements are relative to the wall. An unspecified datum remains unspecified.

The October 4 follow-up reconfirmed [Fenway's live notice](https://www.mlb.com/redsox/ballpark/netting) (Field Boxes 79–9, variable approximate 12 ft 8 in above the field) and [Seattle's live notice](https://www.mlb.com/mariners/ballpark/seat-map) (115–146). Seattle explicitly specifies 13.5 ft above the field for 115–125 and 135–146. Its central 126–134 notice says 27 ft high without explicitly specifying the reference surface; that datum remains unresolved in both registry copies. Seattle's narrower 2018 installation announcement cannot substitute for the current extent.

The simple fan view now shows each park's published coverage, numeric heights with their actual datums, and an explicit **3D netting is not mapped yet** status. The renderer and contact logic are implemented and tested; the number of actual registered panels remains **zero**. Height inputs that cannot register the source model are hidden rather than presented as a working park editor.

## Overlay design and review gates

The intended visual is a subtle, optional translucent panel following the actual net, with a slightly stronger outline on hover or selection. A single shader grid can suggest mesh strands. Avoid modeling thousands of wires, casting shadows, continuously animating the net, or rebuilding it every frame. One shared material and a small number of panels keeps this feature lightweight.

1. Confirm the venue, season, and geometry source hash; keep historical editions separate.
2. Register the actual field-side base line, bends, endpoints, and top anchors on the current model using dated installation plans or independent photographs. Where coordinates cannot be established, retain the club notice without drawing a verified footprint.
3. Use published heights only with their correct reference surface. Record gaps, access openings, support poles, tension cables, and whether movable portions are raised or lowered.
4. Validate against separate control points and a holdout photograph or video; record measured residuals rather than assuming chart pixels are feet.
5. Store first contact with a net separately from the ball's final destination or bounce. Keep observed reports even when they contradict a model.
6. Publish a reviewed, versioned overlay with its sources. A display toggle must not change the physical obstruction version silently.

The overlay should not swallow ordinary map clicks. Its inspection mode can identify a net panel, show the source, and explain whether height and registration are verified. Section notices alone are suitable for informational labels, not collision or probability masks.

The present native registration schema describes one continuous base/top polyline. Disjoint runs, access openings and stepped installations require explicit separate-run support before those configurations can pass spatial QA. Do not bridge a real opening with an invented panel.

Netting does not establish a zero chance of catching a ball behind it. Balls can travel above a net or reach an area after a bounce; net openings and flexibility also matter. Verified observations stay in the database. Catch-rate estimates must treat coverage, height, first contact, final destination, and uncertainty separately.

## Remaining queue

Every record has pending base/top XYZ polylines and independent controls. Start spatial registration with parks that publish heights and have compatible models, then resolve notice-only heights and bends. Toronto, Sacramento, and Kauffman require explicit edition review. The historical Mets installation needs a current confirmation. No generic bowl arc or default height should pass a physical QA gate.