For the route to Lok Ma Chau Control Point

Dear Waze Map editors,

For the route to Lok Ma Chau Spur Line Immigration Control Point, the map have a route through San Tin Tusen Road (22°30’08.0"N 114°04’48.8"E) and Tun Yu Road (22°30’16.9"N 114°04’38.6"E). The two mentioned roads are wrong and they cannot get to Lok Ma Chau Spur Line Immigration Control Point. At the end of Tun Yu Road is closed and it is a construction site.

Instead of going through that two road, going through Lok Ma Chau Road (22°30’15.6"N 114°04’54.8"E) is the right way to go to the Lok Ma Chau Spur Line Immigration Control Point. Follow the Lok Ma Chau Road all the way, and you will get to Lok Ma Chau Spur Line Immigration Control Point. And it is the only way to go to Lok Ma Chau Spur Line Immigration Control Point.

Moreover, Lok Ma Chau Spur Line Immigration Control Point will be closed at 11 pm. After 11pm, all of the cars should go to the Lok Ma Chau Control point. The opening hours of Lok Ma Chau Spur Line Immigration Control Point are 6.30am to 11.00pm. The way to go to the Lok Ma Chau Control point is go to the San Tin Interchange (22°30’04.9"N 114°04’53.5"E), and take the exit of San Sham Road (22°30’08.2"N 114°04’51.7"E) and follow the road all the way and you can get to the Lok Ma Chau Control point. And it is also the only to get to Lok Ma Chau Control point.

Thank you so much. I hope this error will be fixed and Waze is a good app to use!

1 Like

I have break off Tun Yu Rd 惇裕路 at the moment to avoid Waze from using this route.

https://waze.com/en-US/editor?env=row&lat=22.51518&lon=114.06932&marker=true&s=55628889312049614846&zoomLevel=18&segments=450860906,450860905

I have reformatted and rejoined Tun Yu Rd with a disallowed turn for going straight at its very north end. The misdirection problem occurred because there was originally not a break at the border of the frontier closed area along the road. A closed gate was installed there in reality to physically break Tun Yu Rd, disallowing through traffic.

The error should be completely fixed now. Thanks for reaching out!