SC is sometimes asking for kerb height for crossing nodes that already have nodes tagged barrier=kerb and kerb=* describing the kerb heights at that crossing. As an example, the 3 nodes where the paths (steps) cross the road on this way https://www.openstreetmap.org/way/157690082 already have separately mapped kerb nodes with kerb heights, but SC is asking for kerb height at the node in between the kerb nodes that are shared between the crossing oath and the road. This leads to duplicates, for example at the middle crossing where I answered the quest.
I think SC should not ask the kerb height quest for such nodes, but should filer them out.
I think this is related to #4939 and should probably be considered in connecting with that issue (a solution to that issue will probably solve this one too).
SC is sometimes asking for kerb height for crossing nodes that already have nodes tagged
barrier=kerbandkerb=*describing the kerb heights at that crossing. As an example, the 3 nodes where the paths (steps) cross the road on this way https://www.openstreetmap.org/way/157690082 already have separately mapped kerb nodes with kerb heights, but SC is asking for kerb height at the node in between the kerb nodes that are shared between the crossing oath and the road. This leads to duplicates, for example at the middle crossing where I answered the quest.I think SC should not ask the kerb height quest for such nodes, but should filer them out.
I think this is related to #4939 and should probably be considered in connecting with that issue (a solution to that issue will probably solve this one too).