# NORTH SHORE — 2026 / Printable Revision 01

**These are actual printable STL models at 1:2,500.** This is the first physical-prototype revision, not a field-verified 2026 survey or a completed detailed-roof model. Mesh checks are in `validation.json`; physical fit still needs testing.

## Print first

1. `hardware/Fit_coupon_carrier.stl` — one.
2. `hardware/Fit_coupon_receiver_D4.3.stl` — one.
3. `hardware/Locator_pin_D4.0_L5p8.stl` — two copies.
4. After checking fit, `tiles/NS26_B04_1-2500.stl` and `tiles/NS26_C04_1-2500.stl` — one each.
5. For that pair, two copies of `hardware/Carrier_160mm_pitch_3mm.stl`, four locating pins, and one carrier alignment bridge.

Use your current 0.6 mm nozzle for these first tests. All STLs use millimetres, face upward, and have their underside at Z=0. Slice at **100% scale**. The terrain tiles are 159.7 × 159.7 mm and repeat on a 160 mm pitch. Do not scale the whole tile to adjust connector fit: that also changes its geography. Use local hole compensation, separate pin sizing, or the editable CAD/code. Slicer settings can tune tolerances; editing G-code does not conveniently redesign the sockets.

Check the slicer's underside-pocket bridges before printing. The blind receivers span 4.3 mm and the magnet pockets span 6.3 mm. This package has no machine-specific G-code or untested temperature/speed profile. The D4.2 and D4.4 coupon alternatives, and D3.9/D4.1 pins, provide fit options around the nominal dimensions.

## What is included

- **32 terrain/building STLs**, A01–D08. Buildings are integral with each terrain tile in this revision. No separate redevelopment-site inserts are included yet.
- **Nine reusable hardware / coupon STLs:** one carrier, one bridge, three pin sizes, one coupon carrier, three coupon receiver sizes.
- Adjustable reference OpenSCAD for the pins, coupons and bridge, plus Python generation scripts.
- Assembly map, tile index, previews, source snapshots, documented pier estimates, and per-file geometry reports.

## Assemble the first pair

The pins pass through the carrier's 4.15 mm holes. Place the carrier on a flat surface and seat the 5.8 mm pins flush with its bottom; 2.8 mm should project above its 3 mm top. Secure the pins in the carrier after the coupon establishes the fit. The terrain tile's round receiver and horizontal slot lift onto those pins. The slot accommodates small variation in pin spacing.

The full carrier has four 10.3 mm diameter × 1.05 mm deep top pockets for nominal 10 mm diameter × 1 mm steel discs or washers. The tile has four 6.3 mm diameter × 2.2 mm deep underside pockets for nominal 6 × 2 mm magnets. Actual hardware thickness and magnetic retention must be checked. Magnets retain the tile; pins establish its position.

B04 goes west/left of C04, with north/up matching the assembly map. Their physical body edges are 0.30 mm apart. Both carrier and terrain use the same 159.7 mm body size and 160 mm pitch. The long slot direction is east–west. Mark each tile ID on the underside during removal from the bed.

The 23.7 × 8 × 1.8 mm bridge fits underside recesses at the carrier edges. **It is an alignment insert, not a locking transport fastener.** It can be glued within a four-tile group after fit testing. Use a stiff backing board or a verified fastening system for carrying loaded panels; carrier stiffness and retention have not been physically established. The earlier eight-panel concept remains a handling arrangement, not a claim that these thin carrier plates alone safely support a lifted full model.

You can also use a flat carrier board and place the same locating pins and steel pads using the carrier STL as a drilling/position template.

## Full layout and quantities

Four columns × eight rows = 32 tile positions. Each tile represents 400 × 400 m, and each group of four represents 800 × 800 m. The nominal assembly is **640 × 1,280 mm**, about 25.2 × 50.4 inches, before an outer frame. The trimmed outer body envelope is 639.7 × 1,279.7 mm. D01 is a plain water tile with the same underside interface.

For a complete printed-carrier version: 32 carriers, 64 nominal pins, 128 magnets and 128 steel pads. There are 52 shared tile edges if every adjacent carrier connection uses one bridge. These are maximum whole-model quantities, not a recommendation to buy hardware before the coupon test. Eight panels P01–P08 each group four tiles; the map and CSV identify membership.

## Scale and height rules

- Horizontal and vertical scale both equal 1:2,500; no vertical exaggeration.
- All terrain tile undersides share Z=0. **Z(mm) = 8 + 0.4 × elevation_NAVD88(m).**
- The 8 mm offset is a physical base allowance. A carrier adds the same 3 mm to every tile.
- Water uses a chosen flat display plane at NAVD88 0 m, hence Z=8 mm. This is not a measured tide level.
- A 0.15 mm strip is trimmed from every tile edge; the geography itself is not rescaled.
- Receiver centres in nominal 160 mm tile coordinates: (32,32), (128,32). Magnet centres: (12,12), (148,12), (12,148), (148,148). Subtract 0.15 mm from X and Y for the actual exported STL coordinates.
- Terrain is sampled on a shared 1 m grid (0.4 mm in the print), with extra exact edge samples. Each tile uses one common source surface and datum.

## Accuracy and known limitations

Building footprints and recorded ground/roof heights come from the September 2026 NYC OTI dataset snapshot. Roofs are flat height caps. Unknown building heights are not invented; canopy/non-building records and invalid-height features are excluded and logged. Several recorded roofs conflict with the older terrain at some footprint locations. Their original elevations are retained and flagged; terrain can partly obscure them. See each tile's building audit and the combined report before treating individual buildings as verified.

Terrain is from the 2017 NYC/NOAA topobathymetric DEM, bilinearly resampled from one US survey foot to one metre. The source is older than the building snapshot. The 2026 DCP water-excluded borough outline defines displayed land and water.

The DEM lacks elevations on some piers and narrow shoreline edges. These have **estimated elevations copied from the nearest surveyed land point**, never from underwater bathymetry. The resampled source crop is retained unchanged, the working raster is separately named, and the estimate mask and per-tile counts are included. These are placeholders for later measured deck elevations, not survey-grade geometry. No claim is made that a nearest shore height is a pier's actual height.

Buildings receive a 0.01 mm outward footprint buffer to close sub-resolution contacts, clipped to the tile body. Mesh simplification tolerances used to avoid binary-STL numerical defects are recorded in each mesh report. Detailed roof shapes, road/pavement graphics, site sockets and field checks remain future work.

The rectangular extent is our project framing, not an authoritative NorthShoreNYC planning boundary. The footprint snapshot uses the earlier spatial query, so outer-edge context should be reviewed before a finished exhibit.

## Regenerate / edit

Install `requirements.txt`, then run `python scripts/acquire_terrain.py`, `python scripts/build_tiles.py`, and `python scripts/build_hardware.py` from a compatible Python environment. The acquisition script reuses a cached DEM if present. The tile script skips tile IDs already accompanied by success reports. To rebuild an edited tile, remove its matching `reports/ID.json` success report and pass its ID, for example `python scripts/build_tiles.py B04 C04`. Do not delete source files.

Change the receiver/pocket dimensions in `scripts/build_tiles.py`; hardware dimensions are in `scripts/build_hardware.py`. For quick pin and coupon edits, use `hardware/Adjustable_hardware.scad`. Existing successful tiles keep their original geometry when the generation script is rerun.

## Source references

- NYC OTI building dataset: https://data.cityofnewyork.us/resource/5zhs-2jue.json
- NYC DCP water-excluded borough boundaries 26b: https://data.cityofnewyork.us/resource/gthc-hcne.json?borocode=5
- NOAA DEM URLs and processing: `sources/terrain_sources.json`.
- Earlier snapshot provenance: `sources/source_manifest.json`; this describes Pilot 01 and is retained as provenance, not as this revision's status report.

Prepared for Mike's NORTH SHORE — 2026 physical model. No L4-specific batch layout or prototype-printer capability is assumed.
