#LGCTM Case Study: Tricky Duplicates

Sometimes you come across a duplicate on Google Maps that is quite easy to spot as the 2 points of interest (POI) are really close together, have the same name and the same category (and therefore also the same icon associated to that category) – one wonders how the Maps user who added that second place failed to see the one already on the map.

But in some cases the situation is much more intricate, and this is a detailed one of those and the measures I took when coming across it.

What did I find on the map?

Take a look at the Google Maps screenshot, showing the way it was when I stumbled upon this. It shows the city center of the beautiful Belgian city of Diest, where I have marked 3 POIs.

The first (bottom left) was called ‘KAAI DIEST’ and categorized as ‘Museum’ (whereby the name triggered 2 alarm bells right away: name in ALL CAPS and city name as part of the POI name), the second one (in the middle) had ‘De kaai’ as name and ‘Historical Landmark’ as category, and the third one (top right) was a ‘Café’ called ‘Café De Kaai’.

What did I do?

The first step, as always, was to take a detailed look at the information on the 3 POIs on Maps itself and also consulting other sources, like the official website of the city of Diest (which has a section listing the museums in the city, where no museum with that name or address is listed). The POI labeled as museum also turned out to have the same telephone number and website as mentioned on the café POI.

My best guess as to what might have happened: someone wanted to add the ‘KAAI DIEST’ as landmark, but did so with incomplete data and did not find a fitting category (finding the best category often requires you to know the exact term as it is listed within the Google Maps database of POI-categories, and those terms are at times not very intuitive), and therefore decided to select ‘museum’. Later on, this POI might then have been edited by another local guide - who thought the POI was referring to the café nearby – adding the telephone number and website URL.

Given this outcome for my research, I decided that 2 of the POIs needed to be merged, and that the ‘KAAI DIEST’ one was the best choice as the one to be reported as duplicate. But I also immediately realized that a straightforward reporting it would very likely lead to the dreaded ‘NOT APPLIED’ as the data on it were partially similar to the either of the other two.

So, before trying to report it as duplicate, I suggested 3 separate edits for ‘KAAI DIEST’ in a specific order, and in between waited until each of the edits was approved by the algorithms before making the next edit. The goal was to make the data almost identical with the café POI (as the telephone number and website – data points claimed to have a high weight within the total POI-data - were already the same).

  1. changed the category from Museum to Café

  2. edited the address & map marker

  3. changed the name from KAAI DIEST to De Kaai

All 3 edits were approved instantly, as you can see in the screenshot below (notifications are always sorted with the newest at the top of the list).

What was the result?

Once all this was done, I felt pretty confident about reporting the POI as duplicate. And the confidence was justified: the suggested removal was also approved within seconds.

This post is part of the Local Guides Clean The Map project (#LGCTM). All details and links to loads of other posts can be found here.

And here’s an overview of the case studies published so far:

48 Likes

Thank you for sharing this helpful information .

2 Likes

Wow, great idea @JanVanHaver . I will try it.

2 Likes

@Irfan_dPriyanto keep me posted then :grin:

1 Like

@JanVanHaver I have already tried it but why when removing it as a duplicate place, long agreed? Am I pausing too fast between equalizing places and deletions?

3 Likes

Hard to say @Irfan_dPriyanto there can be a lot of different things playing there. Did you get a list of other POIs where you could select the ‘correct’ POI when submitting the duplicate?

Ans also: for certain categories (e.g. banks) it will never work, no matter what you do, so Google must have some extra protection on those.

1 Like

In Spanish

@JanVanHaver

Gracias por compartir estos pasos. Yo he intentado esto en un caso y varios pasos mas, imagínate, es un lugar que me lleva tres años trabajando en él y aun continúa incorrecto en Maps. Cuando te envían una notificación que no se pudo editar tu modificación porque no puede verificar los datos, eso es un muro grande y la gran clave o ver que tu edición desapareció, pues una foto que yo subí ya no la encuentro en mis fotos.

Espero no haber comentado fuera del tema o spam, mi idea esta lejos de eso.

Saludos cordiales.

1 Like

@LuaPL if it can be of any consolation: this is just an example of a case where things went all as expected. In other cases I also get ‘not applied’ without any clear reason why that happens.

My advice: do not worry about individual places, just move on to the next one - there are enough things to be corrected on the map :wink:

2 Likes

You’re welcome @DeepayanS , I hope you can use it for your own area.

1 Like

yes I am using this .

1 Like

@JanVanHaver This is a great example for others to follow on how to remove duplicates. Thanks for sharing.

1 Like

Fortunately I had the reflex of taking a screenshot before starting to fix it @StephenAbraham :slightly_smiling_face:

2 Likes

@JanVanHaver It is working very fast :sunglasses: .Approved just after the edit . :grinning:

1 Like

Excellent news @DeepayanS . Thx for keeping us updated.

1 Like

@JanVanHaver Thank you for this instruction, it’s should help to make the Maps more precise and accurate.

1 Like

@JanVanHaver Thanks for sharing this interesting tips with us. I faced this Issue exact same way you have explained.

But I also immediately realized that a straightforward reporting it would very likely lead to the dreaded ‘NOT APPLIED’ as the data on it were partially similar to the either of the other two.

My initial report back in 2019 for a place duplicate which I know very well was not applied may due to reasons you have mentioned. Then I also did the same way you did, editing the wrong additions’ attributes as the other one and then it approved instantly. Following day I reported for duplicate again but it still being reviewed since January.

3 Likes

Well, pending is not the worst possible outcome @kasunaaa - and as you probbly already know: as local guide you need a lot of patience :grin:

2 Likes

@JanVanHaver Yeah, No worries. Keep Calm and Clean the Map!

2 Likes

You just gave me a great idea for a #LGCTM t-shirt design @kasunaaa :joy:

2 Likes

@JanVanHaver Oh really? that’s cool

2 Likes