MapInfo Pro

Welcome to the MapInfo Pro community! Please feel free to start a discussion in the discussion tab or join in a conversation.

Here are some useful links where you can find more information:

Product Announcements Product Documentation Ideas Portal

View Only

Back to discussions

Expand all | Collapse all

MapInfo Monday: Small Workspace Habits That Prevent Big Performance Issues

1. MapInfo Monday: Small Workspace Habits That Prevent Big Performance Issues

Like
Employee

David Chevé

Blog This
Posted yesterday

Reply Reply Privately
Hi everyone,

You open a workspace that worked fine six months ago. Now it's sluggish, layers are slow to redraw, and you're not sure why. Sound familiar?

I hear this a lot, and the honest answer is that MapInfo Pro performance issues rarely appear overnight. In my experience, they start with small decisions made while building or maintaining a workspace, and they only become noticeable once projects grow, new layers get added, or a handful of other users start opening the same data.

The good news is that a few simple habits go a long way toward keeping a workspace responsive, and they're a lot easier to build in from the start than to retrofit once people are already complaining. Here's what I've learned works.

1. Use the Same Projection Whenever Possible

When layers use different coordinate systems, MapInfo Pro has to continuously reproject data on the fly every time you pan, zoom, or redraw. That work happens quietly in the background, but it adds up fast. I've seen workspaces with just a handful of mismatched layers spend more time recalculating coordinates than actually drawing the map.

If you're working in the same geographic area, standardize projections across your datasets wherever practical. It's a small fix that removes a recurring tax on every single redraw.

2. Store Large Background Data Locally

Network latency is the culprit I see overlooked most often when someone comes to me about a slow workspace. It's easy to blame the software when the real bottleneck is the round-trip your data is making across the network every time it's requested.

Large raster layers, aerial imagery, and other frequently accessed background data almost always perform better sitting on a local drive than pulled from a network share. Before you spend an afternoon adjusting layer settings, try the simple test first: copy the workspace and its data locally and see if the problem disappears. More often than not, it does.

3. Package and Test Workspaces Before Deployment

The Workspace Packager is one of those tools that quietly saves everyone a headache. It collects and localizes all of a workspace's resources into one place, which happens to make it one of the best diagnostic tools available too.

Packaging a workspace before you distribute it surfaces broken paths, missing files, and hidden network dependencies while you're the only one looking at it, rather than after five other people have opened it and started asking why half the layers are missing.

4. Use Zoom Layering

Not every layer needs to be drawn at every scale, and rendering everything all the time is one of the most common and most avoidable performance drains I come across. Picture a national-level view with postal code boundaries switched on: MapInfo Pro is dutifully drawing thousands of tiny polygons that no user could actually see or use at that zoom level.

Setting sensible minimum and maximum zoom ranges stops MapInfo Pro from rendering details nobody can see. The improvement in redraw and navigation speed on large workspaces is often dramatic rather than marginal. This is one of the more underused settings I come across, and often the single biggest win for the least effort.
There is a zoom layer for both the graphics (the layer) and the labels, as shown in the images:

5. Replace Multiple Raster Tiles with Seamless Layers

Managing dozens or hundreds of individual raster tiles doesn't just clutter your workspace. It multiplies the loading and rendering overhead every time the map redraws, because MapInfo Pro has to work out which tiles are relevant and stitch them together on the fly.
Where possible, replace tile collections with a seamless raster layer instead. It simplifies workspace management considerably and noticeably reduces display times, especially in workspaces where imagery is a core part of the map.

6. Convert Large Raster Datasets to MRR

This one deserves a proper explanation, because it's genuinely one of the most underrated tips I share. MRR (Multi-Resolution Raster) is MapInfo Pro's native raster format, purpose-built to store imagery at multiple resolutions within a single file and fetch only the detail needed for the current view, rather than the whole dataset.

Formats like ECW work fine, but they weren't designed specifically for MapInfo Pro, so the software has to do extra work to interpret them. Converting large ECW and other raster datasets to MRR gives you faster access and noticeably smoother navigation, particularly for users who spend their day panning and zooming around large imagery datasets. If your workspace leans heavily on raster imagery, this is one of the highest-impact changes you can make, and one of the ones I most wish more users knew about.

7. Keep Workspaces Clean

Over time, workspaces tend to accumulate layers, browser windows, layouts, queries, and tables that are no longer actively used: a browser window opened for a one-off query eighteen months ago, a test layer someone forgot to remove, a layout nobody's printed since a project wrapped up. Each one adds a little overhead on its own, but together they clutter the workspace and make it much harder to tell what's actually causing a slowdown when one shows up.

Periodically reviewing and removing components you no longer need keeps workspaces both faster and easier to maintain. And it makes troubleshooting much quicker, because there's less noise to search through.

If you want to avoid you and other users making changes to your existing workspace, consider making the workspace file read-only. In this way, it will be harder to overwrite the workspace file.

8. Verify Path Consistency

Performance troubleshooting gets messy fast when workspace resources are spread across different drives, servers, or mapped network locations that don't behave the same way for every user. I've lost time chasing a "slow workspace" complaint that turned out to be one user's mapped drive resolving through a different network path than everyone else's.

A consistent folder structure and predictable data locations make workspaces far easier to support, and they remove a whole category of loading delays that otherwise look random and are genuinely difficult to diagnose.

None of these eight habits is complicated on its own. What they have in common is that they're cheap to build in early and expensive to unwind once a workspace has grown and other people are relying on it. I've seen small oversights like these turn into hours of troubleshooting more times than I can count, usually because nobody thought to look at the workspace itself first.

What small setting, habit, or workspace design decision has had the biggest impact on your MapInfo Pro performance? We'd love to hear your tips and experiences.

Happy #MapInfoMonday!

------------------------------
David Chevé
Senior Support Engineer
Precisely | Trust in Data
------------------------------