We didn’t quite do a complete loop last time. Today we have done a complete loop.
Read the map.
Best route to run in summer, the road is completely tree lined.
As usual we decided to detour to the dirty trail since it’ll be less up and down and a bit longer, I can’t shoot below unless I’m closer to the water
This reservoir loop is probably the shortest in distance among reservoirs on the Kowloon side.
We need more rain this year
Below is from the Bing satellite image in Garmin, I can’t post their map as it’s too lousy and you don’t even see the resevoir.
The Google map in RunKeeper is a lot better
I used iSmoothRun app, distance tracked was 8.09k which is very close to Garmin’s 8.19k. I disabled the auto pause feature of the app as I noticed there are minor glitches of this feature and I prefer to stop the app myself. I also noticed another issue when I stopped to shoot a picture. I manually paused the app, minimized it, shot a picture, bought ISmoothRun to foreground again then the app cued me that workout has been resumed?! The expected behavior would be for me to manually resume my run as I may want to do something else rather than resuming my run as soon as I bring the app back to foreground.
This route is good for a sunny hot day because of the trees, it’s official named “forest trail”. The elevation gain isn’t a lot but the climbs are pretty steep so it’s probably better to hike than run.
The route was also a test ground for running apps. My brother and I used iSmoothRun and my friend used RunKeeper. My friend obviously didn’t notice the GPS signal strength at the start, even if he did there was nothing he could do. My Garmin locked onto satellites alright, iSmoothRun has nothing about GPS signal strength at the start up screen.
It turned out, as you can see from below, that RunKeeper had a wrong fix at the start and my friend started off from the middle of the reservoir.