Five-Tool Harbor Seawall Design Pipeline

Resumo

Pixel shares a harbor design workflow using five platforms in a fixed order to guide reconstruction of a granite seawall at Corbin's Landing. The project combines georeferenced survey data, 3D visualization, and building massing to address flooding, raise the promenade, maintain ferry operations, and inform community meetings.

DEV Community

Five Tools, One Seawall: A Harbor Design Pipeline in Order

A seawall project looks like construction. Most risk sits earlier, in handoffs: one team's elevation, another team's surface, a sheet referencing last week's alignment. At Corbin's Landing we rebuilt a failing granite wall with five platforms in a fixed order. The town is small, the tide range is about nine feet, and the parking lot floods roughly thirty times a year. The design had to raise the promenade, keep the ferry running, and leave the 1920s cannery alone. 1. Halfmaps: one base map first Inputs: state elevation tiles, a 2022 orthophoto, parcel lines, and the mean high water line. Output: one georeferenced map in state plane feet. The survey added 612 shots along the wall and both piers. Two checks mattered. Units: one raster set arrived in meters while the survey was in feet. Ground: the old grading plan showed the lot flat, but the tiles showed a 1.4-foot fall toward the seawall. That changed the pavement design and explained the northwest corner. 2. GenAnywhere: a four-minute model, used carefully I framed the harbor on a map, about 900 by 600 feet, and GenAnywhere generated a 3D model in roughly four minutes. It was useful for orientation, relative position, and a first read on slope. The cannery owns the only high ground; the fish pier is longer than the parking plan suggests; the lot drains toward the wall. It was not useful for elevations. Roofs were flat, pilings were missing, and there were no utilities. We kept it in the visualization pile. When a council member asked if that model was the design, saying no plainly saved a longer conversation. 3. PlaceMaker: massing at meeting scale PlaceMaker turned aerial imagery into about 140 building volumes, plus streets, trees, and piers. The value was scale: a taller wall against the cannery, a second-story addition shading the promenade. At the February meeting, people found their own houses, and the questions got specific. One check: imagery date. A demolished shed was still in the model and made the addition look smaller than it is. We removed it. 4. InfraWorks: put every option in water We combined survey terrain, Halfmaps elevations, and PlaceMaker massing, then tested a normal spring tide at 10.5 feet and the design storm at 12.5. • Raise the wall in place. Keeps the view, closes the lot for two summers. • Move the promenade inland. Cheaper, but clips the fuel dock's truck turn. • Keep the wall line, add 480 feet of steel sheet pile, raise the promenade 2.5 feet. The third won. At 12.5 feet, water crosses the cap in the model, runs over a sloped apron, and exits through a flap-gate outfall. The turning path killed option two in one frame. 5. MicroStation: where mistakes get expensive MicroStation produced 41 sheets: six wall sections, pile layout, rail, ramp, drainage, and the cap detail. The granite blocks are numbered so they can go back in order. Referencing caught a 12-inch water main 3.5 feet below the north promenade, deeper than the utility map. Four piles moved; a sleeve was added. Handoffs that broke • Units. One elevation set in meters, the survey in feet. • Imagery date. A demolished shed stayed in the massing. • Surface drift. InfraWorks and MicroStation surfaces differed by 0.2 feet at the wall; reconciled at six control points. • Sheet index. Two versions circulated after the pile shift. • Expectations. GenAnywhere geometry was never design geometry. None of these are exotic. They are the normal ways a small project loses a week. Preflight I would reuse One datum and one unit, written at the top of the project folder. Every surface has a source and a date. Every visual model is labeled as context. One owner for the sheet index. A field walk with the contractor before bid. The order matters more than the tools. Cheap questions go first, expensive decisions last, and the water surface gets a number before anyone draws a wall. Bids close in January; crews arrive after mud season. The lot will flood again before then, which is a decent reminder of w...
Five-Tool Harbor Seawall Design Pipeline
Powered by Readybot.io

As últimas novidades de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …