With w3w, Gare Du Nord is sunshine.frame.acted while sunshine.frames.acted is Abu Dhabi and sunshine.frame.actor is in Malaysia.
https://what3words.com/sunshine.frame.acted https://what3words.com/sunshine.frames.acted https://what3words.com/sunshine.frames.actor
While in wherewords.id, changing rate to fate or late or gate still produces Paris, but wrong location.
https://wherewords.id/juniper/detailed/rate/thunder https://wherewords.id/juniper/detailed/fate/thunder https://wherewords.id/juniper/detailed/late/thunder
Having an accurate location is important for emergency services. If you’re on a phone call trying to get an ambulance for someone having a seizure, or reporting a fire, shooting, whatever, it’s important to get the accurate location straight away.
If the call centre person misheard your location, but the code is still in Paris, they will think it’s correct and dispatch to the wrong location. It would take too much time after realising the mistake to get the correct location. So with w3w it is far more obvious when these issues happen as suddenly the map is showing as Middle East or Asia, not Paris!
I don’t think an emoji checksum would help here either. Wink. Was that a tongue wink or smirk or etc.
(Full disclaimer: I don’t see the point in w3w either. It assumes people are prepared in advance to have the app on their phone, otherwise if they need to download it/visit its site they have internet so there are better ways of getting the location)