One continuing issue, I think, is the location accuracy of the driver. A similar problem with many locals, resulting in wildly inaccurate map positions.
Ask someone to send you their location, and it will be a general location accurate to a kilometre or two.

Now add that into a map and the updating is sporadic. The built in map generates a best guess routing of the drivers location based, accurate maybe to a kilometre or so, on a trip that may only be a couple of kilometres.

I experienced this recently on a family trip. The location reference was the default geographic location of the town, because they were restricting data usage.

The whole country is reliant on using data services to conduct everyday business, and then limiting these services to save on data.
A byproduct of a telephone network that’s in its infancy, despite the length of time in actual service.

As mike alludes to- the map embedded for use in the app is out of date. But the optimised routing based on poor location data is following a route that has long since been dug up, resulting in a ridiculously rough ride because that is the shorter ‘optimised’ route.

But! As the general culture here is to make something, and let it degrade naturally, I believe there is no effort to maintain and improve- only to replace when serviceability has become so poor as to be impassable.

Some currently acknowledge developed nations are having similar issues with massively pot-holed roads where once efficient highways lay. Yet building new highways takes precedence over maintaining existing ones.

verdebandit wrote: ↑Sun Jul 23, 2023 5:58 am Grab recently added sharing your actual location and not just the pin you put with the driver which will hopefully help with pickups. Overall grab is still better than pass app for location and routing.

It frequently fails. Numerous times around Daun Penh, despite the app.map acknowledging the pickup location- eg, Harry’s or some other specific location, it then frequently defaults to a generic pickup point. Which the driver duly misses. In the torrential rain, I’ve seen the driver finally realise that we are standing there waiting, and they expect us to cross the road in pouring rain.
2 or 3 minutes of this standoff leading to cancellation seems not to worry them much.

I haven't had any real map issues with Grab in Phnom Penh. I'm careful when selecting pick-up and drop-off locations and it has generally worked very well.

When searching for a map location by name of a building, it's obviously important to double-check the result. Many buildings have been put in the wrong place by some idiot, but there's often another search result of the same place (or one next door) available with the correct location.

I've saved my most common pick-up and drop-off locations, so that I don't have to deal with the selection process again and again. That probably covers about 90% of my trips by now.

Siem Reap is a different story though. Many Grab drivers there seem pretty much unable to find you without calling you first, which I find quite annoying. No idea why, if anything things should be easier there compared with Phnom Penh.

Not a single Grab problem on my most recent visit, save for a few of the drivers failing to stop at the destination pin that's sitting on their map right in front of their faces. A minor issue, nothing to sweat over. PassApp, however, was often incorrect on my location, same as Jerry, just had to drag the pin to where I actually was.