How to actually produce a usable offshore wind farm diagram

Most offshore wind farm diagram projects start with a jumbled folder of bathymetry files, geotechnical reports, and vendor specs that don't talk to each other. The diagram you end up with is only as clean as the data pipeline feeding it. Here's how I've learned to build one without losing my mind in week three.

Reading an Offshore Wind Farm Diagram Correctly

A proper offshore wind farm diagram is really three drawings layered on top of each other: the turbine layout, the electrical collection system, and the export path. Most people combine all three into one messy figure and wonder why nobody can read it. Start by separating them. I keep a clean base map layer, a turbine array layer, and a cables-and-substation layer. They all share the same coordinate system and the same depth contours. When I hand this to an engineer, they immediately know which layer to toggle on or off depending on what they're reviewing. The turbine spacing in the diagram matters more than you might expect. Standard practice is somewhere between 5 to 9 rotor diameters apart in the crosswind direction and 8 to 15 diameters downwind. A 14 megawatt turbine with a 220 meter rotor diameter would sit roughly 1.1 to 2 kilometers apart laterally and 1.7 to 3.3 kilometers apart in the prevailing wind direction. Put these numbers in a constraint model and watch the layout options collapse fast. I spent three days once trying to fit a proposed array into a site where the exclusion zones for pipelines and shipping lanes ate nearly 40 percent of the available area. The fix was adjusting the row angles by about 12 degrees, which shifted the whole farm out of the conflict zone without losing significant capacity.

What Tools Actually Work

The industry still runs on a mix of ArcGIS, QGIS, and AutoCAD Civil 3D for the spatial side, and then Excel or a basic Python script for the sizing calculations. If you're working alone on a small project, QGIS is free and handles the geospatial heavy lifting. For anything larger, ArcGIS with the Spatial Analyst extension saves you hours. I use Python to batch-process turbine position coordinates into shapefiles so I don't have to click-point each one by hand. It's the difference between a five-minute job and a two-hour job. For the electrical portion, PSCAD or DIgSILENT PowerFactory will show you the fault levels and voltage profiles, but those are full simulation environments and overkill if you just need a system diagram. I usually sketch the collection network in Visio or even draw.io and then overlay it on the GIS base. The trick is syncing the scale. Nothing looks worse than an electrical schematic that visually contradicts the physical layout. I set the real-world scale to 1:100,000 for the overview and add a zoomed-in detail view for the substation area.

Common Pitfalls That Waste Time

One thing beginners consistently miss is the seabed gradient on the diagram. I learned this the hard way on a North Sea project where the charted depths turned out to be inaccurate near the proposed cable route. The survey team had used older multibeam data that didn't account for recent sediment migration. When we went to install the inter-array cables, the burial depth requirement wasn't being met in several sections because the actual seabed was higher than the map showed. The workaround was running a targeted side-scan sonar survey along the cable corridor before finalizing the diagram. That added about a week to the timeline and four figures in cost, but it saved us from having to redesign the whole collection system afterward. Another frequent error is ignoring vessel access routes. The turbine diagram might look perfect on paper, but if the service operation vessels can't physically reach the offshore substation during winter conditions, the whole layout is flawed. I always check beam sea limits and wave height thresholds against the expected vessel specifications. Most contractors use S9 class SOVs with a significant wave height limit around 4 meters. If your turbine positions push the transit time beyond reasonable operating windows, you'll get complaints from the O\&M team before anyone else does.

The Data Sources You Need to Wire Together

The diagram pulls from multiple datasets and they rarely align perfectly. You'll need bathymetry from the local hydrographic office or a recent survey, geotechnical borehole data from the foundation vendors, meteorological data from buoys or lidars, and environmental constraints from the relevant marine authority. Each comes in a different projection and datum. I always reproject everything to the same EPSG code early on, ideally EPSG:3857 for web mapping or a local UTM zone for accuracy. Failing to do this consistently is how you end up with a turbine position that's 200 meters off from what the foundation designer is working with. The cable route itself needs a separate corridor analysis. I run a least-cost path algorithm through the GIS that weighs seabed stability, existing infrastructure conflicts, fishing activity zones, and military training areas. The output isn't the final route but it cuts the routing time dramatically. From there I manually adjust based on site knowledge and whatever the cable lay vessel contractors prefer.

A Note on What These Diagrams Can't Do

No diagram replaces a proper site survey or a geotechnical campaign. I've seen teams treat the visual layout as sufficient for permitting and then get hit with conditions they completely missed because their data was five years old. The diagram is a communication tool and a planning aid, not a substitute for field verification. If you're producing this for a stakeholder presentation, make the data source dates and accuracy disclaimers visible on the figure itself. It's annoying to add but it prevents follow-up questions that could have been answered upfront. One practical thing I do is include a north arrow, a scale bar, a coordinate grid, and a legend on every version. These seem obvious but I've reviewed diagrams missing all four. The absence makes the drawing look sloppy and undermines confidence in everything else on the page.