Updating a map or model with new data isn’t necessarily difficult—but depending on the software you’re using, it may not be as straightforward as you’d like. Most platforms offer some way to incorporate updated information, but the process varies, and some tools make it easier than others.

If you’re working with large, complex software packages, updating your maps and models can feel like a project in itself. These platforms often come with a steep learning curve, requiring you to navigate multiple settings, configurations, and workflows just to get your new data reflected properly. So, even if the update you want to make isn’t significant, all the steps you must take can be grueling. More user-friendly tools, on the other hand, make the process much simpler. 

The key is finding software that equips you to quickly integrate new data without unnecessary steps or complications. After all, your time is better spent analyzing trends and equipping stakeholders with actionable insights—not wrestling with software to get a map or model updated.

So, what’s the best way to keep your visualizations current without the hassle? The good news: there are efficient methods for updating your maps and models with new data when using a user-friendly platform.

To provide the most specific insight possible, we’re going to explain how to quickly update a map or model in Surfer. Depending on how your data is saved and whether you’re comfortable with automation, there are three primary methods you can use to update your maps and models efficiently in the program:

1. Reload Data – This solution is best when updating an existing data file with new information. It’s the quickest and easiest option if your more recent insights are in the same data file that was used to create an original map or model.
2. Replace Source Files – You’ll benefit from this option when working with datasets in separate files. For example, if your new data is saved in a different file rather than appended to an existing one, this option will let you replace the source file in each layer of a visualization to get the updated map or model you need.
3. Use Automation – This method can be as easy as clicking a button, and it’s great if you frequently update your maps or models but want a repeatable, automated process. With this solution, all you need is a script that creates your maps and models from raw data. Then, you can rerun the script with new data to get your updated visualization. 

There are critical factors and steps to understand if you want to approach each option effectively in Surfer. Let’s walk through them in more detail so you’re set up for success.

If you’re regularly appending new information to an existing data file—such as adding monthly groundwater levels to an Excel sheet or updating a shapefile with new infrastructure information—then reloading the data file you’re using for a particular map or model is the best way to update it.

How to Reload Data Efficiently:

• Save a successful project file as a template file. You can name the successful project file as “Template.SRF” or something more specific. The most important thing is that you save the successful project file as a separate Surfer file. Doing this will ensure you don’t overwrite your original work and can always return to a customizable document.
• Make sure your new data is saved in the same file as your old data. If you’re working in Excel, for example, this means adding new rows or columns of information to an existing sheet rather than creating a separate file to store new data.
• Open your “Template.SRF” project file. This step is as simple as it sounds. All you need to do is open your template project file in Surfer to start making updates.
• Reload your data file. Once your “Template.SRF” project file is open, reload its data file since it now includes new information. Afterward, your visualization will update to reflect your new insights.

Key Considerations:

• This method doesn’t work for any map layers created from grid files. If layers within your map are created from a grid file, you must re-grid the new data and save the new grid using the same name and location as the original grid. Then, you can reload it to see the appropriate updates. See the next option below for more details about this process. 
• It works best when your updates are stored in the same file. If your new data is saved separately, this method won’t work.
• Be mindful of coordinate systems. If the map or model in your template file is in UTM coordinates but your new data is in latitude/longitude, your updated visualization will look odd initially. However, you can easily fix this by adjusting the coordinate system in the appropriate layers to match your new data.
• The data structure must remain consistent. If column names or formats change in your data file, your visualization may not update correctly, so make sure you keep everything consistent to get a high-quality design. 

To put this option in greater context, here’s an example. Say your original map is based on a post layer created from an Excel spreadsheet called Groundwater_Levels.xlsx, and it includes data from April and May. If you add data from June to the bottom of the same Excel sheet, all you have to do is reload the file in Surfer, and your visualization will update accordingly. 

Not all updates come in the form of a simple append to an existing file. Sometimes, you receive data in completely different files. Maybe it’s a new shapefile with recently collected geological survey data or groundwater readings from a different source. In these cases, reloading a single data file won’t work. Instead, you’ll need to replace the source file for the existing layers to showcase the updates—but you can do so quickly.

How to Replace the Source File:

• Save a successful project file as a template file. Similar to the first step for option one, it’s helpful to save a great project file as “Template.SRF” or something else that better suits your needs. That way, when you have new data from completely different spreadsheets, you can build on a foundation instead of starting over. 
• Open your “Template.SRF” project file. Again, this step is straight to the point. Simply open your template file in Surfer. Then, you can start making updates.
• If working with grid files, re-grid your data. With this step, it’s all about re-gridding your data to get a new grid. That way, you can easily go through each map layer and replace the old grid with the new one. Keep in mind that you can skip this step if your new data is only for a post or base layer, not for creating a grid.
• Go through each layer individually. With your “Template.SRF” project file open and your new source files ready to go (including your new grid if necessary), select each map layer and replace its source file, whether that’s the new grid you just created or a new image, spreadsheet, or vector file. 
• Update metadata. Be sure to adjust any project details, such as titles, dates, or client information, to reflect your new data accurately in your map or model.

Key Considerations:

• Double-check coordinate systems and data structures. Mismatches in any of these can lead to distorted visualizations. So, if your updated map or model looks a little odd, it might be that a specific layer is expecting a certain coordinate system or format that the new data file isn’t in. You can easily solve this by ensuring there’s alignment between your source file and the coordinate system and data structure for a particular layer. 
• Despite having to update each layer, this process isn’t as long as you think. If you have about 10 layers to update in your map or model, making the changes can take less than an hour. If your new dataset follows the same structure as the previous one, updates can be even quicker.

Overall, this approach is relatively easy—you don’t need to start from scratch to create an updated map or model. You can just swap out data sources in a template file to get the job done. To give more context on how this works, consider this example: perhaps you had a client that required you to create a model showcasing groundwater levels. If the model was a success, maybe you saved it as a template file. Fast forward months later and you need to create a similar model for a different client using data from new files. In this scenario, all you’d have to do is open the template file and replace each layer’s data source with the new information to quickly generate a new and updated visualization.

If you’re frequently getting new insight—like weekly well monitoring data—automation can be a game-changer. By writing a script, you can streamline the entire updating process, ensuring consistency and saving you significant time.

How to Approach Automation:

• Write a script. In Sufer, write a script that prompts you for a new data file and that grids the data and creates visualizations with all the colors and customization you need. You can do this using Scripter, a script-writing program that comes with Surfer. There are multiple how-to articles and videos with tips that can walk you through this step so you complete it efficiently. 
• Provide all the new datasets. Once you have a script and deliver it new information, it will automatically make the necessary updates to your visualization. For example, it’ll grid new data and load new shapefiles, base layers, and aerial imagery to update your map or model. 
• Get the final output. When using automation, the script can export your final visualization to your desired format (e.g., JPEG, TIFF, or a PDF for reporting).

Key Considerations:

• You’ll experience better consistency. The script applies the same formatting, gridding and visualization settings each time, reducing human error.
• It requires some scripting knowledge. While automation is powerful, it does require some programming skills (e.g., Python, VBScript, or a built-in scripting language). But it’s easy to learn, even if you’re not a programmer. In fact, you don’t need to be a programmer to write scripts in Surfer—you just need a willingness to learn some beginner-level tips and tricks.
• Not all features may be supported. Sometimes, there are limitations on what can be automated, so you may need to check if your desired functions are supported.

You might hesitate when hearing or seeing “script” and immediately think, “I’m not a programmer!” But again, automation doesn’t have to be intimidating. With a willingness to learn, you can create a script to significantly improve efficiency when updating maps and models. You can also get a more consistent, high-quality visualization every time with minimal effort.

Ultimately, all of the methods have value and are quick ways to update your maps and models with new information in Surfer. The method you choose to implement will simply depend on your data, preferences, and technical comfort level. To quickly discern the option that works best for you, check out the table below.