PZ< let's qualify. It is not recommended unless it truly necessary. If you have another way around it that's reasonable, avoid it. For example, if both COULD be a keep or both COULD be a turn, that might be better. Or you can sometimes accomplish this with a wayfinder, which is more acceptable.
The main reasons hacks are discouraged:
1) They are awkward, many editors won't recognize them, and may think they are just a bad edit
2) Since they rely on some esoteric behaviors of the routing engine (or other part of Waze), it is possible that these behaviors may change and turn the hack into a bad map edit
But we won't let those stop us from making a map work today if it is currently misbehaving in a significantw ay and there is no alternative.
The main reasons hacks are discouraged:
1) They are awkward, many editors won't recognize them, and may think they are just a bad edit
2) Since they rely on some esoteric behaviors of the routing engine (or other part of Waze), it is possible that these behaviors may change and turn the hack into a bad map edit
But we won't let those stop us from making a map work today if it is currently misbehaving in a significantw ay and there is no alternative.
Re: [Page Update] How Waze determines turn/keep/exit maneuve