Martin Raifer

PS: do you have a clue what could cause [this CI error](https://github.com/openstreetmap/iD/actions/runs/14036599855/job/39295988320?pr=10911#step:6:457)? Error: AssertionError: expected [ 'en' ] to strictly equal [ 'en-US', 'en' ]

Let's prioritize #11082 for now, as that one is addressing the more often occurring situation in practice (i.e. a user has multiple locales as their preference and also solves the...

I would agree that the use of lifecycle tags (e.g. `abandoned:*`, `razed:*`, `was:*`, `not:*` etc.) would be preferred for these.

@SomeoneElseOSM You linked this issue in https://www.openstreetmap.org/changeset/155217400, but I don't really see how this would have helped in that case: Both relations are tagged essentially equally: `type=route + route=bicycle +...

> Omitted from the iD display are useful information such as "what sort of route is this - local, regional, national?" and "what is the reference number?". For the ref,...

> The only reason there would’ve been “less confusion” with superroute is that we don’t have a dedicated preset for superroute Well, ideally we would also add a preset for...

I cannot reproduce the issue anymore. It's probably been fixed upstream on NSI's side.

fixed in #8911

I can confirm that the two attributes [`addr-housenumber`](https://github.com/GIScience/ohsome-quality-api/blob/1.8.2/ohsome_quality_api/attributes/attributes.yaml#L38-L41) and [`housenumber`](https://github.com/GIScience/ohsome-quality-api/blob/1.8.2/ohsome_quality_api/attributes/attributes.yaml#L6-L9) are duplicates. `addr-housenumber` is newer and was added with #810 //cc @Gigaszi was that on purpose?

I think the addition of the `operator` tag is relatively straight-forward, even though the wiki did not explicitly mention it in the past. It can be useful to distinguish city-run...