Flood extent modeling identifies which areas will be inundated during events such as 100-year, 200-year, or 500-year floods. This is the critical first layer of risk assessment.

Flood extent visuals help planners:

• Identify high-risk zones that are unsuitable or restricted for new development
• Establish zoning boundaries, buffer zones, and construction setbacks
• Understand how changes to land use or infrastructure might alter future flooding patterns

Ultimately, flood extent answers the fundamental question: which areas will be underwater?

Water depth modeling shows how much water will cover the ground across different parts of the floodplain. This matters because 30 centimeters of water and three meters of water pose very different risks to homes, roads, embankments, and utilities.

Water depth estimates directly influence:

• Minimum floor elevations and design heights
• Foundation choices and flood-proofing strategies
• Infrastructure resilience (roads, utilities, pump stations, substations)

Overall, when it comes to water depth, it answers: how severe would the flooding be at this location?

Even moderate water depth becomes dangerous when combined with high velocity. Fast-moving floodwaters can:

• Undermine foundations
• Erode riverbanks and engineered slopes
• Damage bridges, culverts, and retaining structures
• Transport debris that increases structural impact forces

Water velocity modeling is especially important near river bends, constrictions, levee transitions, and urbanized floodplains where flow paths accelerate. Velocity answers: How much force will the water exert and where?

Governments depend on accurate, easily interpretable models to issue permits, enforce development standards, and make policy decisions. Clear visuals help regulatory authorities:

• Understand whether proposed developments meet safety and zoning requirements
• Evaluate compliance with national and EU water management directives
• Identify where mitigation or adaptation measures are required
• Communicate decisions transparently during public consultations

When flood models are intuitive, governments spend less time deciphering technical details and more time evaluating the implications. This helps reduce delays during environmental review, improve trust between agencies and planners and engineers, and aligns construction decisions with regulations. 

Developers and design teams rely on clear modeling outputs to create infrastructure that withstands future conditions. When visuals clearly show flood pathways, depth variations, and high-velocity zones, engineers can more confidently:

• Select suitable building sites
• Determine foundation elevations
• Integrate flood-proofing or adaptation measures
• Avoid areas prone to erosion, structural stress, or impactful to surrounding communities

Clear maps lead to better design decisions and fewer costly redesigns. They also help developers justify construction choices to regulators, investors, and the public, reinforcing that projects are not only compliant but resilient.

For residents and property owners, flood models can easily feel abstract unless they’re visualized clearly. Understandable models help communities see the why behind construction decisions and protective measures, equipping them to take informed action.

Clear visualizations help property owners:

• Understand why certain areas require elevated structures or flood-proofing
• Recognize their personal risk and prepare accordingly
• See how future river behavior may affect their homes or land
• Trust that engineers and planners are basing decisions on robust, transparent science

When flood risk communication is visual, intuitive, and grounded in clear modeling, it empowers communities rather than overwhelming them. This is especially important in regions where water shapes everyday life, as it does throughout the Rhine–Meuse delta and other European lowlands.

Every flood model reflects a series of inputs and assumptions. When any of these components shift, so do the results. Key sources of uncertainty include:

• Input data quality: DEM resolution, land-cover classifications, and drainage data all influence how water appears to move across the surface. Small errors can produce large differences in predicted flood behavior.
• Boundary and initial conditions: Assumptions about upstream inflow, soil saturation, levee performance, snowmelt rates, or storm intensity shape a model’s scenario. Real-world events rarely match these conditions perfectly.
• Climate assumptions: Relying solely on historical datasets risks underestimating future hazards. Climate-adjusted scenarios introduce additional uncertainty but also critical realism.

Because of these variables, two models of the same river may produce slightly different outcomes. This variability represents the space where engineering judgment must take over, where the data reaches its limit.

Effective construction planning actively incorporates uncertainty. By designing with safety margins, conservative thresholds, and flexible strategies, planners and engineers can account for a bigger range of plausible outcomes—not just the “most likely” one. This could mean:

• Choosing sites completely outside—not just barely outside—high-risk zones
• Elevating structures above modeled flood depths rather than meeting minimum requirements.
• Designing foundations that account for erosion potential, not simply water depth
• Ensuring infrastructure can withstand both modeled and unmodeled extremes

In low-lying regions like the Netherlands, building in buffers is good engineering and planning.

One of the most impactful additions to this Surfer release is the introduction of contact surfaces, a feature that makes interpreting and modeling the subsurface clearer and far more intuitive. If you work with drillhole data, this update is especially meaningful.

Contact surfaces equip you to automatically connect matching lithologies or horizons between drillholes, transforming scattered intervals into continuous 3D surfaces. Instead of manually inferring where a layer begins, ends, or changes elevation, Surfer now helps you visualize those boundaries directly, giving you and stakeholders a more complete understanding of what’s happening underground.

With contact surfaces, you can:

• Define and interpolate key geological contacts (e.g., the top and bottom of a coal seam, aquifer boundary, mineralized zone, or confining layer).
• Generate upper and lower surfaces for any material of interest and save them as grids.
• Perform calculations like volume estimates by pairing your surfaces with Surfer’s Grid Volume tool.

Take this example: perhaps you’re working with a series of drillholes that intersect a coal seam. With this new tool, you can mark the seam’s upper and lower contacts, create surfaces from those picks, and then instantly calculate the seam’s total volume to get a clean, continuous model that helps you quantify resources with confidence.

Surfer’s new 3D View Image Along a Polyline makes it easy to select any polyline or polygon from a base layer and use it as the spatial reference for an image. Surfer handles the placement, alignment, and orientation automatically, even when the path curves or cuts across the model at an angle.

What does this mean for your workflow? There are two big benefits:

• Non-linear cross-sections, curving trenches, or angled profiles snap into place instantly.
• Batch placement becomes far easier, which is ideal when working with multiple slices or datasets.

The result? You save significant time, avoid alignment errors, and get the clean, accurate 3D profiles you intended without any challenges. 

For many geoscience and engineering projects, CAD files are a central part of the workflow. With this release, Surfer now supports DWG import and export, giving you a smooth, reliable bridge between Surfer and CAD environments. You can bring DWG files straight into Surfer without conversion steps, preserving geometry, structure, and symbology with far greater fidelity. And when your work is ready to share, you can export your updated or newly created layers back to DWG.

The impact on your workflow is significant. This seamless integration means you don’t have to convert formats or risk errors introduced during third-party conversions. Instead, you get faster collaboration across platforms and a smoother path from analysis to design.

For many 3D workflows, you need to accurately reuse 3D surfaces and structures in Surfer or CAD environments. Today, Surfer equips you to export 3D geometry directly from the 2D plot view to DXF or DWG while retaining all elevation (Z) data. That means every ridge, valley, horizon, and modeled surface stays fully three-dimensional the moment it leaves the 2D View.

Why this matters for your workflow:

• Your exported files remain true 3D objects—no flattening or no manual reconstruction.
• CAD users and engineering teams receive geometry that behaves exactly as expected.
• You eliminate error-prone rework and accelerate cross-platform collaboration.

In other words, your 3D data stays 3D, even when you export it from 2D. This upgrade empowers you to transfer surfaces, models, and structural interpretations seamlessly between Surfer and external tools, ensuring accuracy, protecting data integrity, and keeping your workflow moving forward without interruption.

Surfer’s new 3D View video recording feature is a game-changer for anyone who needs to communicate complex 3D models clearly and confidently. You can now record a smooth, high-quality MP4 video directly from the 3D View that captures exactly what you want others to see. Whether you’re rotating a surface, highlighting a contact boundary, or zooming into an area of concern, Surfer records it frame by frame.

This feature is especially valuable when:

• Clients struggle to interpret 3D PDFs
• Static images fail to show key spatial relationships
• You need to guide someone’s attention to the right location in the model

Ultimately, with video recording in the 3D View, your models look their best, your message comes through clearly, and stakeholders see your data the way you intended. The result? Clearer communication that leads to more informed decision-making. 

Clear communication is not only about the map but also the legend that explains it. In this release, Surfer introduces a series of legend improvements that will help you present your data with more clarity. Below are the main updates. 

• Add Drillholes to the Legend Without Symbology: Now, Surfer automatically includes drillhole symbols in your legend, even when those drillholes don’t have assigned symbology. The benefit is that stakeholders immediately understand what the drillhole markers represent. 
• Automatically Create Contour Entries in Your Legend: Contour layers are an essential part of many geological, hydrological, and environmental maps. With this update, Surfer can automatically generate contour legend entries, leading to clearer communication. 
• More Intuitive Pie Chart Legends: When you’re using pie chart fills, Surfer now shows a boundary line around each pie-slice sample in the legend. This small but meaningful visual enhancement helps viewers immediately connect the legend slices to what they see on the map.
• Templates With Layer Name Directive Support: Legends now support layer name directives across multiple symbology types, including base classed and unclassed symbol and color symbology, base unique values symbology, and post layers. This means a single sample—or even a single drillhole—can automatically use its layer name (e.g., “Sample Locations”) as its legend entry. This results in descriptive, informative legend text, ensuring your maps become easier to interpret.

The main point? Whether you’re mapping drillholes, contours, pie charts, or post data, your legends can now explain your visuals more effectively and with far less effort.

Line charts imply continuity and progression. They connect points as if one value flows naturally into the next. But in some geoscience and engineering workflows, your categories aren’t continuous. Examples are sampling locations, material types, field sites, treatment conditions, and borehole IDs. Using a line chart here artificially suggests a trend where none exists. A bar chart avoids that trap by keeping each category independent and clearly labeled.

Scatter plots are powerful for relationships, but when your goal is comparison—not correlation—they can introduce unnecessary noise. If you simply need to show that Site B has twice the concentration of Site A, or that Sample 4 produced the lowest value, a bar chart does that in a single glance. It doesn’t require axes interpretation, point clusters, or guesswork.

Tables are great for storing values, but they’re ineffective at communicating patterns. Your stakeholders would have to scan numbers, calculate differences mentally, and search for the highest or lowest value. Bar charts eliminate that cognitive burden by turning comparisons into immediate, visual insight. Instead of reading, calculating, and interpreting, your stakeholders can simply see the insights.

Because bar length visually represents value, starting the axis anywhere other than zero can exaggerate small differences and distort your data. A zero baseline keeps comparisons honest and easy to interpret.

Bar charts shine when a stakeholder can compare values quickly. Overloading your chart with too many categories makes bars thin, labels cramped, and patterns difficult to spot. A focused set of categories keeps your chart readable and the insight clear.

Color should clarify relationships, not complicate them. Consistent color choices help reinforce grouping and comparison, while avoiding unnecessary or overly vibrant palettes keeps attention on the data rather than the design.

If someone has to squint, rotate the document, or guess at a label’s meaning, your chart loses its impact. Choose straightforward category names, keep axis values legible, and position labels horizontally whenever possible; if you find yourself tilting or rotating text to make it fit, it’s usually a sign you should switch to a horizontal bar chart.

Excessive gridlines, 3D effects, heavy borders, and ornamental design elements often obscure the point of the chart. Simplicity is your ally. A clean layout puts the focus exactly where it belongs: on the differences between the bars.

Because user-friendly tools like Grapher give you full control over lithology colors, symbols, labels, axes, and other template elements, you can tailor visuals to highlight important data and meet project standards and requirements. This ensures critical insights like subsurface changes and patterns are easier to interpret, reducing ambiguity and strengthening understanding.

You need to keep borehole logs visually consistent, especially across large projects. Templates help with this by standardizing depth scales, column widths, symbology, and layout structure. If you’re comparing dozens of boreholes, for example, uniform formatting helps patterns stand out and ensures cleaner, more credible interpretation.

Templates maintain precise alignment between columns, ensure labels are presented clearly, and apply typographic consistency throughout the log. These small but meaningful details give your visuals a polished, professional look that resonates with stakeholders. When your borehole logs look refined, they’re more likely to trust your analysis.

Templates eliminate repetitive formatting work. Once your structure is set, you can quickly produce multiple logs with identical styling. There’s no need to rebuild layouts or manually align anything from scratch.

Because templates are already presentation-ready, you can export clean, high-quality visuals directly from your software. This removes the need for putting screenshots together or fixing formatting in external design tools.

Whether you’re resampling a well or adding drilling phases, templates let you swap in refreshed data without overhauling your layout. Your visuals update instantly, leading to faster iteration and reducing the chance of errors.

Templates make collaboration easier and smoother. Sharing a template gives teammates a structured, ready-to-use starting point that helps them create professional-quality logs without extensive guidance from you. That’s especially true when a template comes with instructions on how to use it.

By standardizing your borehole visualization process, templates help your entire team work more efficiently when similar projects arise. Instead of starting from scratch, future initiatives can rely on the same template foundation.

When your visuals need to stand up to scrutiny—whether from clients, regulators, or multidisciplinary teams—templates help provide borehole logs that are polished, legible, and easy to interpret. High-quality visuals reduce confusion, build credibility, and help stakeholders trust your conclusions.

If you’re working across several wells, sites, or datasets, templates keep everything consistent. Instead of manually recreating formatting for each log—which can be an error-prone process—you can maintain the same color schemes, symbology, depth scaling, and layout to make comparisons straightforward.

Projects involving quarterly sampling, long-term remediation, groundwater monitoring, or repeated exploration phases benefit tremendously from templates. You can quickly recreate the same visuals with new data, ensuring an identical structure each reporting cycle.

In many cases, borehole visuals aren’t just explanatory but also actionable. When logs inform remediation strategies, drilling locations, safety planning, or resource allocation, there’s little room for ambiguity. Templates help ensure those decisions are grounded in visuals that are consistent, precise, and easy to interpret, reducing the risk of missteps caused by unclear or inconsistent graphics.

I love Hawaii. I have a wish that I could spend a month there every winter. I love the ocean, the greenery, and the culture; the vibe is very chill. It’s a nice break from the dry climate and lack of water in Colorado.

The first time I went to Hawaii was in the early 2000s with my dad. We went to Oahu, and a few years later, the Big Island. I went back to Oahu with my mom about five years ago. Then, after a very busy 2024 with almost no vacation time, I decided to start taking two vacations a year. Last year, I did a road trip through Utah, Arizona, and New Mexico, followed by this trip to Kauai with my mom. This was our first time on Kauai.

The most interesting thing was driving around the island. Kauai is not large, yet it contains seven microclimates. You go from the tropics to the desert to the rainforest very quickly. It’s obvious when you change zones because the plant life shifts drastically. For example, the mountain peak gets over 600 inches of rain a year, but only 45 minutes away on the west side, there is a rain shadow that gets less than 17 inches annually. Kauai also has what they call the “Grand Canyon of the Pacific,” which is the Waimea Canyon. It’s a massive canyon that forces the road to go all the way around the island because you can’t drive through it.

We were definitely at the mercy of Mother Nature. We stayed in a condo community, but our building was just a little bit off the coast. Even just walking out to the water, the wind was insane. There were very few calm days, and you didn’t really want to stay exposed to that wind for very long.

It was also hard to know what the weather would be like in one area of the island versus another. We went to this beautiful beach and got lucky because the rain stopped right as we arrived. But when we went to explore the town, the rain rolled in again. We had to head to a completely different part of the island to find something else to do. You just had to be flexible in your plans.

The weather apps only predict “rain” for the day; they can’t predict those one- or two-hour gaps of sunshine. And the news channels weren’t helpful because they give the weather for the whole of Hawaii across multiple islands, which doesn’t help when you’re dealing with specific climate zones on one island.

They actually have this “Coconut Weather Station” that was really funny, but it’s a silly joke. If the coconut is wet, it’s raining; if the coconut is moving, it’s windy. It’s a way of saying you truly cannot predict the weather there. If you want to know what the weather is, you just have to look outside.

A huge percentage of the plant life on the island is actually non-native and invasive. Because the climate is so hospitable—with rich soil and plenty of water—invasive species have drastically changed the landscape from what the Native Hawaiians would have seen centuries ago.

We went to a luau where they explained the history of hula and the various cultures it came from. I learned that there was a long history of war among island nations—Tahitians, Polynesians, and others—fighting over the different islands. The culture we know today as “Native Hawaiian” is a combination of all those older island cultures. That context made the hula even more interesting. I loved it so much. It was more than just a performance. 

We also went to a hula demonstration at a big hotel that was put on by the woman who taught our lei-making class. The demonstration was incredible because it was up close with just two dancers.

We didn’t get out on the water this time, but I know there are major reef protection efforts. You can actually see the importance of the reefs just by watching the water; the waves break far out on the reefs or rocks rather than hitting the shore with full energy. Without those reefs, the shorelines are under much more threat from erosion and intense waves. 

The last day. We had “perfect” Hawaii weather. It was a completely clear day. We got into the ocean, went to a nice restaurant right on the water, and watched the sunset. It was a lovely end to the trip.

It was definitely a much-needed mental break. I successfully managed not to check my email or Slack the entire time, which was a big win for me. But beyond just the break from work, I came back with a renewed desire to pursue my creative interests. I do a bit of everything—sketching, painting, knitting, pottery, glasswork, and quilting. Being in Kauai really sparked that again.

The island’s beauty was a big part of inspiring my creativity. I found myself taking pictures specifically thinking, “Oh, this would make a beautiful painting.” We also did a few hands-on creative things while we were there. We took a lei-making class, where we learned to weave real leis using orchids and ti leaves. It was so cool that I actually brought home some ti leaves so I can teach my nieces how to make them this summer. 

The other reason I came back inspired was because my favorite souvenirs are pieces of artwork. I tend to visit a lot of art studios whenever I travel. The artist I was most impressed by on this trip to Kauai was Troy Carney. He makes these 3D art pieces by cutting out intricate designs and layering them in epoxy.  He has a video of the process on his website.

It would be neat to visualize the historical sailing routes between the islands, showing where the different villages were set up and coloring the routes by island culture, like Polynesian versus Tahitian, for example.

When working in 2D, it’s common to either stack all your surface and subsurface data onto a single map, making relationships hard to distinguish, or to separate them into different maps entirely, which fragments the story your data tells. Both approaches make it difficult to fully grasp how features connect below the surface, but 3D visualization solves that problem. It brings every layer—surface topography, mineralized zones, and subsurface features—together in one cohesive view, allowing you to see how they interact spatially and in context. The result is fewer assumptions, clearer interpretations, and more confident conclusions.

Drilling decisions depend on understanding what’s happening below the surface, and 3D visualization gives teams that insight with unmatched clarity. Seeing drillholes and targets in 3D makes it easier to plan precise drilling paths and identify areas with the highest potential. This not only improves accuracy but also cuts costs and reduces wasted effort in the field.

Resource exploration brings together diverse datasets, including geological maps, geophysical grids, geochemical assays, drillhole data, and more. In 2D, comparing these side-by-side or on one map can be cumbersome and disconnected. In 3D, everything comes together in a single, unified model. You can overlay, align, and analyze multiple data types spatially, revealing patterns and correlations that are impossible to see otherwise. The result is a more holistic understanding that leads to stronger interpretations and smarter decisions.

Even the most accurate technical insight can lose its impact if stakeholders can’t visualize what it actually means. On a 2D map, complex concepts like depth, overlap, scale, or uncertainty often require explanation to provide additional context. For non-technical audiences, that can quickly become overwhelming or decrease their engagement.

3D visualization removes much of that friction by sharing data in a more realistic, intuitive way. Instead of asking stakeholders to mentally reconstruct what’s happening below the surface, 3D shows it to them. Mineralized zones have thickness, drillholes have depth, and geological structures appear as they exist in the real world, not flattened onto a page. This realism makes complex findings easier to grasp, builds confidence in the interpretation, and helps decision-makers engage with the data without needing a technical background.

When every dataset, layer, or variable is shown at once, the main insights get buried. Instead of clarifying the takeaways, the visual becomes overwhelming, leaving stakeholders confused about what matters and what they should focus on. The result? A misinterpretation of the findings, leading to delayed decisions.

Default color scales, contour intervals, or axis scales are great, but they’re not always tailored to your specific data. They can unintentionally mask important variations or exaggerate patterns that don’t actually exist. Relying on them every time—without considering customizations you can make—leads to maps, models, and graphs that don’t effectively honor your data, creating confusion rather than clarity.

Because you’re familiar with every assumption, limitation, and nuance of your data, it’s easy to forget your audience isn’t, especially if they’re non-technical stakeholders. When labels, legends, or visual cues aren’t clear, your audience will have to guess at meanings, and guesswork almost always leads to misunderstanding or hesitation.

The foundation of effective data presentation is choosing the visual format. No single map or graph works for every scenario. Different visuals highlight different relationships, and selecting the wrong one can unintentionally obscure your insights. Below is a quick look at common and specialized map and graph types and when each one is the right choice.

When to Use Different Map Types

• Contour Maps: Best for showing smooth, continuous variation across a surface—like groundwater levels, temperature, or topography.
• Color Relief Maps: Ideal when you want audiences to quickly grasp spatial gradients or intensity changes using intuitive color scales.
• Shaded Relief Maps: Use these when terrain interpretation matters; shading creates a realistic sense of elevation and slope.
• 3D Surface Maps: Choose this when elevation, volume, or surface geometry is essential to understanding your data, especially when depth relationships influence interpretation.
• Base Maps: Useful when your goal is to anchor your data to real-world locations using imagery, streets, or land cover for context.
• Classed Post Maps: Best for showing how sample locations fall into key categories or thresholds (e.g., contamination levels, soil types).
• Vector Maps (Arrows, Quivers): Choose these for directional data, such as groundwater flow, wind direction, or current movement.
• Volumetric or Isosurface Maps: Best for visualizing 3D plumes, ore bodies, or subsurface concentration zones that cannot be interpreted easily in 2D.

When to Use Different Graph Types

• Line Graphs: The go-to for showing change over time, trends, or continuity between data points.
• Scatter Plots: Use these to highlight relationships or correlations between two variables, which is great for exploratory analysis.
• Bar Charts: Best for comparing discrete categories or summarizing grouped data.
• Histograms: Ideal for understanding data distribution, spread, or skew—commonly used in QA/QC or statistical analysis.
• Box Plots: Use this visual when comparing distributions across multiple groups; they quickly show medians, variability, and outliers.
• Ternary Diagrams: Choose these when analyzing three-component systems, such as soil composition or geochemical ratios.
• Stiff, Piper, or Durov Diagrams: These are essential for water chemistry interpretation, equipping you to compare ionic composition and classify water types.
• Polar or Wind Rose Plots: Great for directional datasets where frequency and magnitude depend on angle (e.g., wind speed, flow direction).
• Bubble Charts: Helpful when you need to show relationships among three variables (x, y, and bubble size) in a compact visual.

Ultimately, you have a lot of visual formats at your disposal, but choosing the right one is the first step toward ensuring you communicate your data-driven insights well.

Overloaded visuals bury your message. When a map, model, or graph tries to show everything at once—too many layers, labels, symbols, or colors—the most important takeaways aren’t easily identifiable. To overcome that issue, prioritize the insights stakeholders need to see first, then strip away anything that doesn’t directly relate to those points. 

The wrong color scale can misrepresent gradients, hide subtle variation, or introduce bias. Likewise, poorly chosen contour intervals, axis limits, or symbol sizes can distort meaning.

Choose color scales that reflect the nature of your data, set scales that accurately represent values, and maintain consistent symbology across figures. When every stylistic choice supports clarity, stakeholders can immediately focus on the meaning behind your insights rather than the mechanics.

Even strong visuals can fall flat if stakeholders don’t know what they’re viewing. That’s why annotations are great. Labels, callouts, and legends guide your audience through your visual so they understand the main takeaways. However, please remember that just enough context prevents confusion; too much creates noise. Use annotations where necessary to ensure stakeholders have the insights they need and don’t get bogged down by the details. 

Data presentation is storytelling. A strong narrative follows a logical arc: Question → Method → Insights. Your visuals should follow this same progression. Sequence it so each design element builds on the last, helping your audience connect steps and arrive at your insights naturally. When the story flows, decision-making becomes faster and more confident.

3D visualization is an incredibly powerful tool, but like any tool, it’s most effective when used intentionally. Not every dataset or deliverable needs a 3D model, and using 3D at the wrong time can confuse your audience. The key is understanding when 3D genuinely enhances clarity and when a well-crafted 2D visual communicates the message more effectively.

Here are general guidelines for when each approach works best:

• When 3D helps: Subsurface mapping, overlapping features, volume interpretation, and spatial relationships that can’t be seen clearly in 2D.
• When 2D is better: Simple comparisons, regulatory deliverables, quick checks, or time-sensitive workflows.

Ultimately, using 3D should be a thoughtful decision to ensure you get the most benefits from it. Choosing the right dimensionality will support your ability to effectively communicate insights from your data.

Different audiences bring different levels of technical expertise, priorities, and expectations to the table. A visual that works perfectly for an engineer may overwhelm a community stakeholder, and a simplified public-facing graphic may be too imprecise for a regulatory agency.

Understanding what each group needs to see is essential to ensuring your message lands. For example:

• Clients and regulators typically need accuracy, analysis, and defensibility.
• Internal teams may need more technical depth to collaborate effectively.
• Public audiences often require simplified visuals without losing factual accuracy.

The strongest data presentations meet viewers where they are. They give each audience exactly what they need to understand the insights so they can make informed decisions.

3D models equip stakeholders to validate designs early by seeing geometry, volume, and relationships in context long before construction begins. This clear spatial understanding reduces guesswork, helping teams spot inconsistencies, conflicts, or risks that might not be easy to spot with 2D visuals. The result is more accurate designs, fewer costly revisions, and safer, more reliable outcomes once work begins in the field.

Engineering projects often rely on different datasets, from geotechnical logs and CAD files to LiDAR and hydrologic data. With 2D, visualizing all of these datasets can either feel fragmented if you create multiple simple maps to communicate the information, or convoluted if you try to put all the information onto one map. With 3D, you avoid those challenges. The different datasets can come together in one cohesive model, empowering stakeholders to clearly see how layers, systems, and features interact so they can gain deeper insight and make more confident decisions.

Explaining technical details to non-technical stakeholders can be challenging, but 3D visualization bridges the gap in understanding. It transforms complex data into intuitive visuals that make design intent, constraints, and outcomes easier to grasp. Whether sharing progress with clients or collaborating with cross-disciplinary teams, 3D helps everyone stay aligned regardless of their technical background and expertise.

In 2D, testing design alternatives or updating project assumptions can be slow and disjointed. You often have to recreate multiple views or manually adjust overlapping data layers, which makes it difficult to see how one change affects the rest of the project. In contrast, 3D visualization makes iteration seamless. You can quickly adjust parameters, test “what-if” scenarios, and instantly show stakeholders how updates ripple across the model. This ability to quickly visualize change leads to faster decision-making, more adaptive planning, and greater project agility overall.

One of the biggest problems with weak documentation is lost context. When the reasoning behind your choices isn’t recorded, future you—or anyone else touching the project—has no way of understanding why certain decisions were made. This can show up in a few ways:

• No notes explaining how a visualization was designed or how it should be updated.
• Missing justification for customization choices around color scales, symbology, filters, or gridding settings.
• No record of parameters you tested and discarded, which makes it easy to repeat mistakes.

Without this context, even a polished graph, map, or model becomes difficult to reuse, update, collaborate on, or defend. The “what” is visible, but the “why” is lost, and that part matters when making data visualizations.

When your documentation is weak, the next phase of the project—like updating your visual with new data—often requires retracing your own steps instead of building on prior work. That slows momentum and forces you to investigate rather than focus on analysis. When that happens, three consequences appear: 

• You spend too much time trying to remember how you produced a map, model, or graph.
• Recreating workflows becomes guesswork instead of straightforward execution.
• Long pauses between project stages lead to unnecessary restarts because the original process wasn’t documented.

Over the course of a project—or an entire career—these inefficiencies add up to hours of avoidable rework.

Geoscience is collaborative by nature, but poor documentation makes it harder for teams to work together effectively. When teammates can’t follow your process, collaboration slows and feedback becomes less actionable. You’ll start to notice that: 

• Colleagues struggle to understand how results were generated or what assumptions were used.
• Reviews take longer because they require extra explanations.
• Decision-making is delayed by repeated clarification cycles.

Weak documentation creates barriers where there should be alignment, and that affects project timelines as well as project quality.

In technical and regulated industries, your work must be able to stand on its own. Without clear documentation, you lose the “paper trail” that connects your raw data to your final conclusions. This creates a two-fold risk:

• Increased Misinterpretation: When workflows, assumptions, and datasets aren’t explicitly recorded, stakeholders are forced to guess. This leads to misread results, incorrect decisions, and a breakdown in trust between you and your audience.
• Vanishing Accountability: If a regulator or client challenges a specific model or map, you must be able to show exactly how you got there. Weak documentation leaves you unable to justify your parameters or symbology, making your conclusions difficult to defend under scrutiny.

Ultimately, documentation is your professional insurance policy. Without it, even the most accurate analysis can be dismissed if it can’t be traced and verified.

Strong documentation starts with your digital file names. Clear naming conventions help you and others instantly identify the latest version, the correct dataset, or the appropriate visual without digging through folders or opening multiple files.  Consequently, it prevents confusion and speeds up workflow transitions.

For a concise, standardized naming structure, consider including:

• Project or site name
• Date or sampling round
• Version number or milestone

This simple practice will eliminate ambiguity and ensure the right file is always easy to find.

One of the biggest challenges in long-term or seasonal projects is remembering exactly how you built a visual or the settings you used. The same problem arises when handing a project to a colleague who must decipher your filters, styling choices, or workflow from scratch.

You can solve this by leaving comments explaining the reasoning behind your choices inside the project file itself. These embedded notes will preserve the context behind your work, so you never have to retrace your steps, rely on memory months later, or create confusion among team members.

Consider creating comments to record:

• Why a specific filter or setting was chosen
• What a color scheme, axis range, or symbol style is meant to highlight
• Instructions for collaborators on what to review, adjust, or replicate
• Assumptions, limitations, or considerations for future updates

When comments live in the same document as the visualization, nothing gets lost—and both you and your team work faster.

Good version tracking prevents accidental overwrites, supports defensibility, and captures the evolution of your project. That said, instead of constantly overwriting files, save milestone versions as the project progresses. Each version will become its own snapshot, which can be useful for audits, regulatory review, team collaboration, or retracing earlier conclusions.

When tracking versions, helpful things to add include:

• Brief notes on what changed and why
• Distinct version numbers (v1, v2, v3) aligned with project checkpoints

Ultimately, intentional versioning reduces confusion and preserves a clean historical record.

A project overview acts as a roadmap for anyone who opens a file, including you if you open an old document months later. The short summary will provide essential context without requiring a deep dive into the full workflow.

A strong overview typically includes:

• Project goals or questions being answered
• Primary datasets used
• Current status or progress
• Any unresolved questions or known limitations

This quick reference will dramatically reduce onboarding time when either reopening a project after significant time has passed or handing it off to a colleague midstream.

Data rarely speaks for itself. Recording details about where it came from, how it was processed, and its limitations makes your work transparent and repeatable. This is essential during QA/QC, regulatory reporting, peer review, or collaboration with technical teams.

Key metadata you should capture includes:

• Data source, collection date, and sampling method
• Coordinate systems and units
• Processing steps, filters, or transformations applied
• Known limitations or uncertainty

When metadata is clear, the credibility and defensibility of your work increase significantly.

All geoscientific interpretation involves assumptions. Failing to document them can lead to misinterpretation, miscommunication, or incorrect decisions down the road. So, writing down the why behind your decisions acknowledges uncertainty while strengthening trust in your outputs. 

Here are examples of assumptions to share:

• Reasoning behind boundary interpretations
• Areas of uncertainty or sparse data
• Conditions you assumed to be constant

Clear assumptions enable clearer conversations with stakeholders and smoother technical review.

Documentation is easiest and most accurate when added gradually—not saved for the end of a project. Natural checkpoints such as sampling rounds, analysis, internal reviews, or draft-report stages are ideal moments to update notes. Providing context at each major milestone keeps documentation fresh and accurate.

Documentation loses value when it’s scattered across personal folders, email attachments, and chat messages. Centralizing your data, notes, and outputs ensures everyone has access to the same information. Consider using a shared and consistent structure (team drive, SharePoint, secure cloud folder, etc.) to keep project knowledge accessible and prevent critical context from disappearing.

Consistency is one of the most powerful documentation tools. Standardizing your approach to naming, note-taking, summaries, data visualization, and version tracking removes friction and makes it easier to switch between projects and get up to speed. One easy way you can start standardizing documentation is to create checklists or standard operating procedures (SOPs) for everyone to follow. 

Before submitting a report, exporting visuals, or delivering results, take a moment to ensure your documentation reflects the current project state. This final review reduces last-minute confusion and protects your work from avoidable questions during stakeholder review. 

During the review, confirm the following:

• Decisions and assumptions are clearly recorded
• Metadata is complete
• Version notes reflect the latest file
• Instructions for future updates are accurate

This final check strengthens both the clarity and defensibility of your results.

When documentation preserves the “why” behind your decisions, picking a project back up becomes far easier. Instead of spending hours retracing your steps or reverse-engineering old settings, you can quickly reorient yourself and resume progress with confidence. This is especially valuable for seasonal work, long-running studies, or projects with lengthy pauses between phases. Clear documentation shortens the ramp-up time and gets you back to productive work sooner.

Good documentation eliminates the guesswork that often slows collaboration. When teammates can clearly see your assumptions, decisions, and workflows, they don’t have to interpret your process; they can just build on it. This leads to faster reviews, sharper feedback, and fewer back-and-forth clarification cycles. Whether you’re working across departments or handing a project to a colleague, strong documentation keeps everyone aligned.

When you document the reasoning behind your maps, models, and graphs, explaining results becomes easier and far more defensible. You can clearly articulate how an output was generated, why certain parameters were chosen, and what assumptions guided the analysis. That transparency strengthens trust with clients, regulators, project managers, and internal reviewers alike. It also reduces repetitive questions and skepticism during presentations or reporting.

When comments, assumptions, limitations, and workflow notes are captured along the way, errors are less likely to slip into final outputs. Good documentation serves as a built-in QA/QC tool, helping you spot inconsistencies earlier and produce cleaner, more accurate maps, models, and graphs.

Strong documentation not only helps the current project team but also strengthens institutional knowledge. Processes, lessons learned, and repeatable workflows become easier to preserve, share, and scale across other projects or departments. Over time, this builds a more efficient, informed, and capable team.

Walking on a 3D model gives stakeholders the opportunity to navigate your insights at their own pace, moving through results as if they were walking across the project area. This freedom to explore equips stakeholders to focus on the areas most relevant to them—whether that’s a potential drilling location, a suspected contamination zone, or a region of structural complexity. Instead of relying solely on your chosen viewpoints, stakeholders can inspect the project area from angles that help them build their own understanding. As a result, they’re more likely to grasp subtle relationships, like how a proposed site sits relative to slopes or drainage. 

Fly-throughs are an excellent way to set the stage. By providing a pre-recorded tour of your 3D model, fly-throughs can establish spatial context early. This can help stakeholders understand where key features sit relative to each other—like watershed boundaries, elevation changes, infrastructure locations, or regional geological patterns—before the conversation shifts into more granular analysis.

Also, because fly-throughs are pre-recorded, they offer a structured narrative that gently leads stakeholders through the insights you want to share. They prevent information overload by introducing complexity in a gradual, intentional way. Instead of overwhelming stakeholders with a model they must explore on their own, fly-throughs equip you to curate the experience, ensuring everyone receives the same clear orientation before deeper discussion begins.

Videos are one of the most accessible formats for communicating 3D insights, especially when sharing results with audiences who may not have the software or technical background needed to explore a model interactively. A well-made video equips stakeholders to absorb the information without navigating any tools themselves, removing barriers and ensuring consistent understanding across the group.

Repeatability is another major advantage. Unlike a live demonstration, a video can be replayed, paused, and reviewed as many times as needed—whether during internal discussions, stakeholder meetings, or regulatory reviews. This makes videos incredibly powerful for communicating complex insights.

Animations help show progression, movement, or relationships as they unfold. Whether you’re visualizing plume migration, changes in groundwater elevation, or the evolution of terrain, motion reveals trends that would otherwise remain hidden. The key advantage of animations is that they control the pace of information delivery. Smooth transitions highlight what’s changing—and what isn’t—helping your stakeholders detect relationships that could be missed when comparing individual snapshots. 

Exporting your model to a 3D PDF will lead to an intuitive file that anyone with Adobe Reader can open, explore, and use to understand key insights. With a 3D PDF, stakeholders can rotate, zoom, and pan the model. Most importantly, they can toggle layers on and off, a powerful way to help them focus on the insights that matter most. For example, a regulator reviewing a remediation plan may want to isolate the plume layer, then add stratigraphy, then add monitoring wells to understand spatial relationships step by step.

Every rotation, zoom, or camera path should serve a purpose. Ask yourself: What insight does this movement reveal that a static view cannot? If the motion doesn’t help clarify a relationship, show a transition, or draw attention to something important, it’s most likely unnecessary. Only purpose-driven movement is recommended.

Even the best visuals lose impact when they move too quickly. Slow, deliberate pacing allows stakeholders to absorb details, understand spatial context, and connect what they’re seeing to what you’re explaining. Whether you’re creating a fly-through or animating a plume boundary over time, err on the side of clarity over speed.

Too much movement, too many layers, or overly dramatic transitions can work against you. If stakeholders are dazzled by the animation but unclear about the insight, the visualization has failed its purpose. Keep the interactivity simple wherever possible and reserve motion for the moments that truly elevate understanding.