• The blueLine() is based on turns, so does not have the start and finish of the race. To get that we need to add the first and last timestation data to the blueLine marker data.
  
• Where there is a scale on the profile image it horks up the left to right alignment with the map, as the chart width data includes the scale.
  
• When the route travels west after going east for a while, the elevation profile can be really wild.
  
• In general the elevation sampling based on turn data is not very accurate, especially when the trend of the route is more south north than west east.
  
• When the blueLine() draws on the / map sometimes it just stops before the end of the route. Dunno why.
  
• On a slow connection the front page can sometimes not seem to do anything, leading to confusion. This appears to be related to the tiles for the map not yet being fully loaded, so perhaps we shouldn't establishRoute until the map is fully up. There is probably an event for that.