Deduplication issue with transit stops

Hi there,

I encountered an issue concerning the dedupe strategy.
Autocomplete/search for "Manneken Pis" does not return the little peeing guy I am expecting. Instead, only the Bus stop is returned.

After some debugging, I found that they are considered duplicates:

• they have the same layer and parent hierarchy
• they both have the same name in some languages
• the statue node does not have an address or postal code
• The bus stop does have an address and postal code
  (if one element does not have an address they are considered equal)

Then, the bus stop is preferred because it has a zipcode.

This issue can possible happen many times as bus/metro/train stops often have the name of a nearby famous venue.

Suggestion:
Should we add a dedupe rule, maybe on category and/or addendum? venues with different categories should not be considered as duplicates.
Although, this could generate real duplicates since venues on osm are often duplicated and do not necessarily have the same tags.

Alternatively, another solution could also involve popularity. In this case, the statue has a higher popularity than the bus stop. But if you are actually looking for the bus stop, then this does not work either.

Any idea?

Thanks

https://pelias.github.io/compare/#/v1/autocomplete?focus.point.lat=50.843183&focus.point.lon=4.371755&text=Manneken+pis&debug=0

Reproduce the Manneken Pis autocomplete case from the linked Pelias compare URL, then read helper/diffPlaces.js around lines 166-172 and middleware/dedupe.js around line 113. Determine how transit stops and nearby venues should be distinguished, and define tests that preserve valid deduplication while returning the expected result.