In this article, company founder Andy Allan explains what’s involved in creating maps, what the challenges are, and how often maps need updating.
The first step in creating a new map is to have a strong reason for it, like a particular feature to show or a type of activity in mind. Then if that doesn’t fit into one of our existing maps, we create a new one.
Our newest style, Atlas, was based on lots of customer feedback, and shaped by many of the custom map styles that we were creating for customers.
We use OpenStreetMap for almost all of our map data. The big advantage of using OpenStreetMap, over any other data source, is that it contains so much detail about so many different types of things, often not normally available.
So if I want to show ski routes, it has the data. It has the difficulty level, the type of grooming, nordic vs alpine skiing, and so on. It usually has even more information than is possible to show, even on a specialist map.
I usually consider three factors:
Other maps sometimes go overboard, where every street and path has a different colour depending on some attributes in the data. Too much detail can be confusing, so I need to be selective.
The main challenge is to make sure the map can be widely understood. I don’t want to create maps that only a few experts can use, or that need end-users to spend a long time pouring over a key to work out what the colours and symbols mean.
The other main challenge is icon design. Trying to create small, clearly understandable icons is hard. Dealing with the situations where there are too many features in one particular spot, and choosing which icons should be prioritised, that’s also hard.
I need to really think about the end users to know which icons are the most important for them.
The software that we use is not very user-friendly, but it’s powerful. So there is a steep learning curve to use it proficiently.
You also need a sense of aesthetics, to be able to choose colours that work well together and that complement each other without clashing.
You definitely need an eye for detail. I spend a lot of time making sure the halos around text are just the right width and opacity, making sure that there’s enough gaps between different icons, and ensuring that paths and roads look just right when they join.
Being able to create a map can be about a lot of small things that people don’t notice. But when it’s not done exactly right, then people do notice that something isn’t right, even if they can’t tell exactly what it is.
I like to make new maps available at a fairly early stage for feedback, so I can iterate.
I also need to see how the maps look in different parts of the world. Often there’s something that doesn’t look right in one city, or I realise a feature is missing. Then I can fix it.
For example, on one map I didn’t realise that roads were being drawn above tram lines, which isn’t an obvious problem in London but was obvious when I looked at Kraków.
Maintaining a map consists of three different challenges:
Most of our maps see small changes every few months, usually when an improvement to one map is copied across to the others. Major changes to a particular map are much less frequent – and much less frequent than I would like.
I really enjoy that stage where I know a map is going to be useful to someone else. If someone uses our maps to find a cycle route they didn’t know was there before, or they need a drink and they see a cafe shown on our map, then all the effort is worthwhile.