Manager Guide

Contents

1. Installing RG2
2. Using the RG2 Manager

Accessing manager functionality

The login page can be accessed by adding "?manage" to the normal web address (e.g. http://www.club.routegadget.co/uk/rg2?manage).

There is an introductory video that shows an event being set up.

Once you have logged in you will have access to three tabs:

1. Add event
2. Edit event
3. Add map

Add event

Supported formats:

• Results file: RG2 reads the first line of a CSV file and tries to find all the necessary fields. Your CSV file must as a minimum have columns with the following names: 'Database Id', 'Surname', 'First name', 'Start', 'Time', 'Classifier', 'City' OR 'Club', 'Short', 'Course', 'Course controls', 'Place' OR 'Pl', 'Start punch', 'Control1', 'Punch1', 'Control2'. Sportident CSV files, or any other CSV file that meets the BOF results file requirements should work. RG2 will automatically detect if you are using commas or semicolons as the separator. If you are using Autodownload then you need to generate the file using the "Export OE splits" option. Emit Spklasse.csv files are also supported.
• Results file: IOF XML 2.0.3 and IOF XML 3.0. Tested successfully with Autodownload and SportSoftware files.
• Course file: IOF XML 2.0.3 (tested from OCAD, Condes and Purple Pen) and IOF XML 3.0 (tested from OCAD and Condes).

If you have a georeferenced map and course file (IOF XML 3.0) then the controls will be automatically aligned when you import them.

The Results file must be in UTF-8 format. If you see invalid characters in results then it probably means that your results file does not have this format. This can often be corrected by opening the original results file in Notepad (on Windows) and selecting "Save as..UTF-8". The results should then import correctly to RG2.

Edit event

Select the required event in the dropdown.

The available options are then:

• Edit event details
• Delete route
• Delete event.

Locking an Event

When you create an event, or at any time afterwards, it is possible to lock it by selecting the checkbox. This will make the event read-only. It shows up as a lock icon in the title bar, and the Draw tab is greyed out. People will be able to see the map, courses and results but they will not be able to draw routes. This will allow you to check that everything has been set up correctly. The event can be unlocked on the "Edit event" tab.

Add map

RG2 supports JPG and GIF files. The original Routegadget converted all maps to JPG. RG2 now keeps a GIF file if that is what was initially uploaded, so this should allow smaller file sizes. It also creates a JPG file from the GIF file for compatibility with the original Routegadget. See the Map files page for further guidance.

If the map is georeferenced then it is possible to read in the associated world file. This will allow alignment of courses and GPS files. See the Georeferencing Maps page for further details of how to create georeferenced maps.

Security

RG2 uses similar principles to RG1. It stores an encrypted password file (rg2userinfo.txt) in the kartat directory. User names and passwords must be at least five characters. If the file does not exist then it is created the first time that anyone tries to log in. The file can be deleted at any time if you have the necessary privileges. This would normally be via an FTP account. There is no ability to reset or retrieve passwords (other than by deleting the user file), and only one user can be created.

This is NOT the same login and password as an RG1 account.

If you are having problems then the first thing to do is log on to your site via FTP and delete the rg2userinfo.txt file. You will then be able to create a new user name and password.

Caching

You can improve the RG2 response time quite a lot (at least 0.5 seconds for big events!) by enabling caching of the JSON files. To do this create a directory called "cache" in the kartat directory. Every time RG2 gets a request it will look for a cached JSON file first, and will only recreate details from the .txt files if it cannot find one. The save functions delete the cached files every time something changes, so it should all work automatically. You can always delete any of the .json files or the whole cache directory at any time to force things to be done from first principles.