How to Tell a 'Bad Map' from a 'Good Map' and Save Hours

Written by Tom Samuels on

When working with CAD maps, identifying quality at an early stage can save hours of frustration down the line. A poor-quality map often suffers from disorganised layers, fragmented geometry, and inaccurate spatial data, all of which complicate tasks like data editing and analysis. 

Here's how to tell which CAD maps will need a lot of formatting work doing.

Download the latest OS CAD maps here


VIDEO TRANSCRIPT

''Hello, today I'm going to be identifying the differences between a good and a bad map and to start I'm going to show you some reasons why a map can be considered bad. This is basically comes down to features that don't exist that I just going to make editing and using your map and more flexible manner it's going to take a lot of time to create and so all the information is now in one place which is going to create a lot of time when you're gonna do something like I'm gonna show you now for example if you wanted to separate the roads onto say a different layer I'm just going to give that a line style to turn straight this you're gonna have to be selecting the roads manually and then changing changing them to the layer and so yeah depending on the size of the map this this could take a lot of time and then one thing that you can see here that's a bit problematic is how these how these arcs are split into quite small segments so you can quite easily miss a piece of roads and have that on a long layer and this is going to be the same if you want to say create a building layer I'll just create another new layer here and I'll show this is this green make that my current layer so let's say I want to
create some hatches so I find it's quite useful to have your your buildings as a separate field layer as well as having a different outline if you ever want to do such a thing as a usage diagram for example that can be quite useful and here you can see a problem where these ones have filled quite quickly AutoCAD has seen a closed shape and filled it here due to some bad line work we we can't do that so that again creates more work more issues more time not just having to do this yourself manually but also potentially having to deal with some bad line work and then the last thing I'm going to show you on this map is how the test has come in it hasn't come through as text but it's confused as line work so this means I've got no option to say change the fonts or what's written and to show you how this these issues you know can work I'll show you the latest map serve simple map where we have layers clearly named clearly defined so if I wanted to quickly change the colours to all the buildings to be green that's done in a click of a button I've identified the layer and and how I can then change that and the same with text here this text is is real text so I've got the the option to change the font or if I need to I can add some text author and edit that so this is going to having a map set up with these layers it's world war we don't have that issue with geometry being all over the place it's all very clear it's where it should be and the layers clearly named editable so that I can change you know that again so for all the building outliers to be read it's just done quite quickly from that layer.''


Let’s explore some technical aspects that differentiate a good map from a bad one

1. File Size and Performance

One of the most immediate signs of a poorly constructed map is an unnecessarily large file size. Maps cluttered with redundant data or poorly optimised elements can take longer to process, which slows down project timelines. Efficient file size management, such as compressing high-resolution images and using vector-based files where possible, is crucial to ensuring smooth operation.


2. Proper Layer Organisation

A well-organised map will have clearly named layers that follow a logical structure. Each layer should represent a distinct set of data, whether it’s roads, buildings, or elevation contours. A bad map, on the other hand, may have messy or ambiguous layers, forcing users to spend extra time identifying and isolating relevant information. Grouping layers effectively helps maintain clarity and simplifies project workflows.


3. Consistent Projections and Coordinate Systems

Geospatial accuracy is key when working with CAD maps, especially when they will be overlaid with other datasets. A bad map may lack the correct projection or coordinate system, leading to misalignment with other data. A high-quality map will use standard, consistent projections and document these within the metadata. This is essential for integrating data across different platforms and ensuring that the map’s spatial representation is reliable.


4. Clean Geometry and Data Integrity

Good maps will feature clean geometry, free of unnecessary vertices, duplicated polylines, or gaps in the data. In contrast, bad maps often have fragmented or broken polylines, meaning additional time must be spent correcting errors before any real work can begin. A solid map will have verified geometrical data, ensuring it is accurate and complete.


5. Editable Text and Annotations

Another common problem with poor-quality maps is non-editable text. Good maps should feature editable text and annotations, allowing users to make changes efficiently. Non-editable elements add to the difficulty in modifying the map and can increase project completion time due to time-consuming workarounds.


6. Metadata and Documentation

Quality maps often come with comprehensive metadata, which is critical for understanding the map’s origin, scale, and purpose. This information includes the source of the data, the date of creation, coordinate system, and the scale of the map. Bad maps frequently lack this documentation, leaving users without important context and increasing the likelihood of misinterpretation.


7. Legibility and Symbology

A good map should not only be technically sound but also visually clear. Well-designed symbology ensures that map elements are easily understood. Overly complex or vague symbols on a bad map can lead to confusion and reduce the map’s usability. Consistent, clear labelling and a well-thought-out colour scheme contribute to a map’s legibility and effectiveness.


8. File Format Compatibility

Ensuring the map is in a compatible format with your CAD software is another important factor. Poor maps may be in formats that are difficult to import or manipulate, whereas good maps use widely supported formats like DXF, DWG, or shapefiles that integrate smoothly into most CAD workflows.


9. Efficient Use of Blocks and Symbols

In a well-crafted map, common elements like trees, buildings, or street furniture are represented with blocks or symbols rather than individual line segments. This not only reduces file size but also makes the map easier to edit and update. Poor maps, however, often depict these elements as fragmented lines or shapes, resulting in heavier files and tedious editing processes. By using standardised blocks and symbols, a good map streamlines the visual representation, enabling quick updates across the map and enhancing the overall readability and efficiency of the design.


10. Error-Free Topology

In high-quality maps, topology—the spatial relationship between different elements—is carefully managed to avoid errors such as overlapping or disconnected features. A good map will ensure that boundaries align accurately and that there are no unintended gaps or overlaps between polygons or line features. Poor maps often contain these errors, which can disrupt spatial analysis, cause confusion during editing, and require significant time for correction. By maintaining clean, error-free topology, a well-made map supports more accurate data representation and smoother integration with other geographic information systems (GIS).