A map of a city is more useful when it has an opinion about what to leave out

A map of a city is more useful when it has an opinion about what to leave out

There is a difference between a map that shows you everything and a map that helps you decide where to eat. The second one is much rarer, and it is much more useful when you are actually in the city.

The reason is simple. A complete map is a data dump. A curated map is an answer.

The city, not the street

When you are in a place you do not know, the question is never "what is on this street". It is "where do I go, and what am I walking past on the way".

That is a much smaller question, and a much more specific one, and it does not need the full street grid to answer.

Mapas.place is organised around that: places by city, with the listings grouped by what you would actually do there rather than by administrative boundary. It is at Mapas.place, and the site is at https://mapas.place.

The same idea in a different register is what a store map is. Which boutiques are worth the detour, which neighbourhoods cluster what, and which of them is a ten-minute walk from where you are standing.

Place Luxe does that for shops and destinations. It is at Place Luxe, and the site is at https://place.luxe.

What makes a list of places worth trusting

The failure mode of every city guide is the same. Somebody visits, has a good time, writes about the three places they went to, and the list becomes a monument to that trip rather than a description of the city.

There is a way to tell. Ask whether the list tells you what to skip.

A list that only contains good things is not a guide, it is an advertisement for those things. A list that also says this street is nothing special, this area is closed on Sundays, and this place has queues for two hours is giving you information.

That is the difference between a recommendation and a map. The recommendation tells you where to go. The map tells you where to go and what you are choosing between, which is the thing you actually needed.

The part that makes it usable while you are walking

Two practical things decide whether a city guide works.

Distance and time, not straight lines. A place four kilometres away is a different proposition depending on whether you are walking, driving, or on a train line that does not go there. A map that tells you the address and leaves the rest to you is making you do arithmetic.

Area grouping that matches the question. Grouped by district is right for "where should I stay". Grouped by what the place is for is right for "where do I eat". Grouped by price is right for a different trip entirely. One list cannot be right for all three, which is why a single list of everything usually ends up being good for nothing in particular.

The other thing, which sounds small and is not, is that the page has to load fast on a phone with a bad connection, because that is the moment of use.

It is the same rule that applies to any page you read while doing something else, and it is worth checking it on a real connection rather than on the office wifi. The same goes for the other kind of city page, the one that tells you where the printing and the small local services are when you are in a town you do not know: ImpressorasBR does that for printers across Brazil, at https://impressorasbr.com.

A practical way to use these

When I am going somewhere I do not know, I do the same three steps.

1. Pick the area, not the venue. One neighbourhood to start, not one restaurant.
2. Look at what the map leaves out. If everything is recommended, the map is not telling me anything.
3. Check the one place that looks closest to where I will be anyway, and make that the plan. The rest is what happens if the queue is bad.

It takes about ten minutes and it beats picking at random on the street, which is the alternative most people end up with.