Hi arctic-rocinante,

thanks for the additional details and the screenshots! Whether or not OSM or OrganicMaps interprets and renders "more correctly" in this instance is probably arguable but the layer=4 in a context of layer=2 paths was definitely inconsistent and seemed like a previous, slightly misguided lower-level attempt to fix a higher level issue. I've changed this path to level 2 (which also, as mentioned, follows equivalent objects in its context). I'm not sure how often OrganicMaps update their data that the client uses, so it might take a while for the change to come through, you might know better. Let me know once it's resolved so we can close the issue.