Provide extra info allowing to identify specific object such as bicycle parking

[matkoniecz]

Use case
Sometimes there are multiple bicycle parkings next to each other (wheelbender and proper stands). In such case asking about bicycle parking capacity is impossible to answer.

getHighlightedElements is not helping in case when parkings are directly next to each other.

And yes, it is an actual problem and I run into it.

Current label is

Bicycle Parking

or

Operator Name (Bicycle Parking)

I propose it to become

Bicycle Parking - wheelbender

or

Operator Name (Bicycle Parking - wheelbender)

Proposed Solution

Show bicycle_parking tag (translated using text from bicycle parking type quest)

Opening an issue as I suspect that @westnordost may veto this due to worry that getNameAndLocationLabelString may start growing more complex.

Though I think that it is worth it.

[westnordost]

Your use case could be solved by displaying different Icons for different types of bicycle parkings? If yes, which bicycle parkings would need to be distinguished?

On May 24, 2022 1:52:20 PM GMT+02:00, Mateusz Konieczny ***@***.***> wrote: **Use case** Sometimes there are multiple bicycle parkings next to each other (wheelbender and proper stands). In such case asking about bicycle parking capacity is impossible to answer. `getHighlightedElements` is not helping in case when parkings are directly next to each other. And yes, it is an actual problem and I run into it. **Proposed Solution** Show `bicycle_parking` tag (translated using iD presets) Opening an issue as I suspect that @westnordost may veto this due to worry that `getNameAndLocationLabelString` may start growing more complex. Though I think that it is worth it. -- Reply to this email directly or view it on GitHub: #4058 You are receiving this because you were mentioned. Message ID: ***@***.***>

-- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

[matkoniecz]

Your use case could be solved by displaying different Icons for different types of bicycle parkings? If yes, which bicycle parkings would need to be distinguished?

The problem is that sometimes parking are next to each other and icons are too close to be distinguishable.

What worse, if mapped as nodes it is not possible to distinguish them just from positions, and different mappers would place them differently. Often making nonobvious which refers to which one.

Following one is case which I encountered multiple times, decent parking and whellbender next to each other:

[FloEdelmann]

Why not modify the title of these quests to include the translated iD preset?

E.g. How many bicycles can be parked here? → How many bicycles can be parked here (%s)?

[westnordost]

Why not modify the title of these quests to include the translated iD preset?

E.g. How many bicycles can be parked here? → How many bicycles can be parked here (%s)?

Is it 2021 again? The translated iD preset name is already displayed below the question! Don't you remember, we change this?

[FloEdelmann]

The %s should then of course be filled with "wheelbender" or "stands", which is not yet part of the iD preset name.

[westnordost]

Nah, don't want to have (temporary) workarounds like that.

[westnordost]

To summarize:

• different icons don't really work if the nodes are really close to each other
• but displayed names (OP suggestion) also don't work in that case
• I do not want to have temporary workarounds like suggested by Flo

Hence, the solution should be that the bicycle parking subtypes should be iD presets. In the meantime, leaving notes should be just fine.

[matkoniecz]

the solution should be that the bicycle parking subtypes should be iD presets

not entirely sure, iD can more or less distinguish it and there is no need to change feature name

(translatable names of types would be even better but that is kind of separate issue)

[westnordost]

It is possible to have presets that add several tags at once.