Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by okw

  1. The change from a dawn-morning race to a dust-night one will affect significantly some runners' strategy. Mine as well. For previous SCSMs, many had the "clock-more-miles-before-it-gets really-hot", and then leave it to fate when the sun reveals itself. Negative/neutral splits were rare, especially for non-elites. For this year's edition, I would be very conservative for the first 10-12km depending on the heat/humidity, knowing for sure it will only get cooler for the remaining route. Ideally attempting a negative split.
  2. I'll highly recommend you do this. It's an evening race and 6 weeks before SCSM. Almost ideal :)
  3. And now a new 32km category is added. https://www.spacebib.com/events/view/sg-run-2019-471
  4. What I was trying to highlight is, there are many ways to plot. Following the middle of road/lane tends to give a longer distance than what most runners will run. Most of the numbers I see in Strava fall within 20.4 to 20.8km. I guess it's quite reasonable the official one is very close to 21km.
  5. No leh, mapometer didn't say 21.1, it depends on how one plots it. I didn't participate in the race so I can't comment much. I did however plot one based on the official route map, multiple Strava activities and my own knowledge of various segments. It turns out to be about 20.7km. Those interested can view it here: https://sg.mapometer.com/running/route_4904351.html
  6. If one knows how GPS works, it's not surprising to know the discrepancies. In a highly built-up area, especially in downtown Singapore with lots of high-rise glass towers, GPS signals get bounced all over the places, causing perceived surges in speed and jagged lines. Many runners get their 1km "PBs" due to this, myself included. For sharp turns or u-turns, most GPS watches will not be able to "fill up" the gaps in between the data points. With a very cloudy sky and we have fewer satellites to lock on to, resulting in inaccurate positioning.
  7. Yea, I think so too. Certified routes follow the shortest possible paths within the designated lanes, so if the official route is measured along the middle of the lanes, most runners will come out short.
  8. Finally result is out: http://results.racetime.sg/cgi-bin/common/results/2xu2019/search.pl
  9. Well, at least 3 members posted their own plots in this thread. Range from 20.7km to 21km. Most runners' data from what I saw on Strava were less than 21km. PA might plot correctly, and they might give an allowance of 300m deviation, I guess it's fair.
  10. Multiple pacers' GPS watches (different brand and models). I used a foot pod as well. And for most seasoned runners, they know when certain segments were reported too fast/slow due to GPS signal errors and mitigations can be made.
  11. Hello Beast, good questions! My replies below (to my best knowledge and memories) 1) How long was this planned route run before the actual run start date? Several weeks before the race day. The route was published and it was based on online plotting. The "on-site" run was to confirm and make adjustments. 2) Did they say what "logistic inconvenience" they were facing? I am guessing that it refers to their re submission the route to the relevant authorities for approval, which they might find it troublesome or do not have enough time to do it. Ease of placing a u-turn point for easy access, e.g. timing mat. I do encounter another race where a segment was removed due to rather late notice from the authority. 3) In another event, why did the person checking the planned route feel disappointed when told by runners one of the category distances was short? If he has done his checking and ensure that it was accurate enough, he has done his job right? Well, I don't know how many times had he tried and specifically what method. But at least he is travelling along the entire route and not just by plotting on the map. He was probably disappointed he made mistake(s) somewhere and not trying to dismiss it. Regarding the chicken rice analogy, it was to highlight that, runners have varying values what they want to get from an event. Health/safety are obvious for most (if not all) people. Distance to me is amongst the top. If I felt shortchanged, I want to know why (or how). No hard feelings ah...
  12. I do care if they screw up the distance. Of course, it's up to the individual. I was involved in pacer duty awhile back and the pacers were asked to run the planned route (in this case, no road closure required), and we proposed how to make up for the shortfall. Eventually, they opted for logistics convenience at the expense of distance accuracy. In another event, the person responsible for the route did the run/ride himself, he was disappointed when told by runners one of the category distances was short, but spot on for the others. Give a break to those who care about distance accuracy and measurement techniques, it's not wrong and not nonsense. As for the chicken rice analogy, if a consumer gets food poisoning after eating, he probably wants to know how the food was prepared, unless it doesn't bother him.
  13. Refer to the image, I bet they plotted along the red lines which were not passable due to constructions along Tanjong Rhu water line. That's easily a difference of 300m+. Any decent organizer would have made adjustments. These are not blockages put up the week before.
  14. There's no need to apologize to anyone, my friend . I'm a sucker for more accurate distance and I'm not apologetic for it. Each of us values various things differently. I don't bother about medal, race pack, baggage management. But I ask for safe route/path, good marshalling, sufficient water point and aid station. One aspect we all agree though, run well, run safe, run happy.
  15. Such discrepancy, in my opinion, is shortchanging the runners. With today's technology, it is not rocket science to get distances within 200m for a flat HM. The serious runners will feel their timings (especially PBs) are not qualified. Others may have the false impressions they are better than they really are, albeit 1-2min difference. If anything, I rather the organizers err on the other side, make it longer than shorter.
  16. My own plot, based on the multiple sources (other runners' GPS data and organizer's map), is 20.72km. So it's somewhere between 300-500m shorter. The are many wide segments, e.g. between National Stadium and Stadium MRT where runners might run shorter or longer than the official path. The segment along Fullerton is a common place where the tall buildings with lots of glass causing sporadic GPS data, usually adding to the distance.
  17. 2012 was my first NC. One big loop and a smaller loop, 9 + 6 + 6 + 9.
  18. I missed the earlier years of Newton Challenge flagging off from The Big Splash. Not a big crowd, only 18 and 30km categories. The runners then were more "seasoned" and had better etiquette (my opinion). I am kinda hoping this one will bring back some of those vibes... (nostalgic mood) haha...
  19. Well said @Ender. Though the much lower prices, many participants would still expect top notch support and goodies. Efforts should be focused on the race pack collection, good crowd control, flag-off timeliness, sufficient on-route hydration. Anything else would be a bonus.
  20. Many significant changes (mostly positive ones) for this edition. Could be largely due to a different event organizer? I think last year it was HiVel, the year before was PinkApple and this year is MetaSport.
  21. A few of my friends got the same email without registering anything. One thing in common, they were participants of previous years' events.
  22. I'm curious about the venue and routes across the 4 legs. Will it be 4 routes with no overlap? That will be interesting.
  23. What was the saga ah? Care to refresh the old mind? I recall KOTR was held in a few Asian cities. It was like 16.8km.
  • Create New...