Out of bounds, crossings, uncrossable etc.

These things are often part of the overprint (purple bits) along with the course and are not on the OCAD map file that is used for the background map in RouteGadget. So are not visible when someone is looking at routes etc.

Crossing points

If the planner puts in a compulsory crossing point in a course within Condes or OCAD, the XML export file confuses Routegadget and it treats it as a control on the course. This means that there is a split time missing as far as RG is concerned, and so it will not allow the route to be recorded.

Java issues

RG is a Java applet and Java must be installed for RG to work. If you don’t already have it on your computer you may be asked if you want to download it. Java is used in a lot of web applications and is very common on mobile phones. You can find out more by visiting www.java.com.

Missing control data

Faulty controls or timed crossing points (later removed from the splits) will cause problems to RouteGadget.
The files that RG creates contain a string of times in seconds from the start for each control, separated by a semi-colon. It depends on the event software being used as to what happens.

Page 1 of 1