Cannot upload changesets when an element in a relation whose type has a prefix is edited

[Swarkin]

Description

When editing an element that is a member of a relation which is tagged with for example disused:type=, both iD and Rapid refuse to upload it even though there have not been any edits to these relations as it doesn't detect the type field.

Screenshots

https://i.imgur.com/bkGV0tD.png

[mibe]

Here is the changeset causing this issue. AFAIK the error message pops up even if no relation tags were changed. For example, AFAIK splitting a way which is a member of the causing relation is enough for triggering this error.

Background: We got completely new bus lines at the turn of the year. IMHO it was/is not feasible to adapt the change to the old route relations because the change is so significant, that just creating new relations is quicker and easier. But I did not delete the old relations yet, because I wanted to still have them for reference while creating the new relations. So I deactived the relations by adding the disused: prefix to the type=route and route=bustags of the relation.

[k-yle]

According to the wiki¹, a relation must have the type tag, so I believe this behaviour is intentional.

type=route + disused:route=bus would be a valid alternative.

Footnotes

1. https://osm.wiki/Relation#:~:text=A%20relation%20element%20must%20have%20at%20least%20the%20type=*%20tag ↩

[tyrasd]

What @k-yle says ☝️

[tyrasd]

That said, iD should not prevent a user from uploading a change that does not directly modify an existing relation without a type tag: e.g. to reproduce:

• load any way of https://www.openstreetmap.org/relation/25872 in iD
• split the way
• try to upload the change

--

For reference: There are currently about 2k relations without a type tag.