I'm going to re-open a discussion that we had earlier here on whether or not to include the directionality on road labels.
When I first asked about it, I was told that it was essential to include the direction of carriageways (for example, labelling a road as I-10 W), and the argument was that this was necessary to make traffic alerts useful.
The reason I'm bringing it up is that now that we're starting to see useful traffic alerts here in the UK, I've noticed that if you click on a traffic alert, Waze very helpfully shows you WHICH carriageway is affected through a map where the impacted carriageway is shown in yellow/red, with arrows also helpfully showing you which direction is involved.
I also noticed that in the case of an alert I saw last night, Waze actually inserted the direction involved on it's own. (The alert I saw last night said "A4 W Heavy Traffic" - I'm fairly sure that nowhere along the A4 is it actually labelled as "A4 W", so it must have worked out the W bit on it's own and inserted it?)
If this is indeed how the client renders traffic alerts, I really don't see any further point in inserting directionality onto carriageway labelling as it really does clutter up the map and should be avoided if possible.
(I also note that on all of the existing maps I've seen in the US, directionality isn't included on the interstates there either... Add in the problem that in different languages, "East", "West", etc., are going to be abbreviated differently (something we need to consider here in Europe), I think that having the client work out the directionality and display it in the local language is preferable, and I think, something that the client is now doing? (can someone confirm this?)