This is the kind of tool that makes me genuinely excited. As an NLP researcher, the “explains what each tag means in your language” feature is the part that caught my eye immediately — it’s essentially a multilingual knowledge base doing real work at the point of editing, not just a translation layer bolted on afterwards.

The fact that it started as a Wikidata editor and now bridges both is a nice story about what happens when you build the right abstraction. Toolforge hosting is also a smart choice — stable URL, no server costs, and the community gets a tool that doesn’t vanish when the maintainer gets busy.

One question from the NLP side: are the tag descriptions pulled from the tag wiki, or are you maintaining your own? If it’s the former, the quality varies quite a bit across languages, and I’d be curious how you handle the gaps in less-resourced languages.

Same question keeps coming up for me in Aarhus. I ride long distances and the access tags tell me where I’m allowed, but not where I’d actually go on a Tuesday in November. The “would actually ride” layer is the one I miss most — it’s the difference between a technically legal route and one I’d trust with my commute.

I’ve been thinking about whether a “comfort level” or “traffic confidence” tag could work, but I suspect it would be too subjective for the wiki. Maybe a community-sourced “frequently ridden” flag for routes people actually choose? Or even just a note in the changeset comments when someone maps a route they personally use regularly?

Curious what the 300-post thread landed on. The “legal to ride” vs “would actually ride” framing is the right one — I think most cyclists feel this gap but haven’t had a name for it.