Skip to content

Conversation

@burrscurr
Copy link
Contributor

Summary

I noticed that the set of highlighted elements for the two board type quests (name and type) was different, which could be confusing when the quests trigger on the same (or nearby) elements. This PR aligns both by expanding the set of highlighted elements for the board type quest. This is a follow-up on #6418.

Screenshot

https://www.openstreetmap.org/node/9199014037#map=19/50.705403/10.695204

board type highlight


override fun getHighlightedElements(element: Element, getMapData: () -> MapDataWithGeometry) =
getMapData().filter("nodes with tourism = information and information = board")
getMapData().filter("nodes with tourism = information")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interestingly, the board type quest only triggers on nodes (see elementFilter above), while the board title quest also includes ways and relations. I mirrored this for the highlighting (don't include ways+rels here in the highlighting filter as was done for the board title quest).

Should this be aligned as well? Its probably of low consequence, since information=boards are almost exclusively nodes (about 1 in 400 is a way).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aligning them makes sense, my instinct would be to treat way ones as tagging mistakes or nanomapping reaching parody levels

but investigating them to check is this guess true would make sense

@matkoniecz
Copy link
Member

I see it was tested and seems to make sense to me

I looked at file history including earlier name and #5882 and it does not seem discussed/changed so far

@matkoniecz matkoniecz merged commit 5d5f8b0 into streetcomplete:master Jul 30, 2025
@matkoniecz
Copy link
Member

And thanks for a PR!

westnordost added a commit that referenced this pull request Aug 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants