This page summarises the different ways to register competitors for a stage. All methods can be mixed for a stage, depending on the present needs.
There are two ways to easily register lots of competitors before a race.
Beware that there is no way to directly set course for each runner with the original OE CSV format. Instead, you rely on runner category and link each category with a course. Before an import, first create courses and categories in the stage configuration, then link courses with categories. By default, runners will be registered on the [Auto] course.
Both CSV import and archive import automatically create club and category necessary for the import.
With the OE CSV format, the only mandatory fields are the last and first names, the club and the category (short/long names). Start number, ecard, archive id, NC field, and start time are all optional. Other fields are ignored by Geco. The same constraints applies to the archive format, which uses less fields.
The Start time field allows you to give a registered start time, without the need for a start station. The given hour should be relative to the zero hour of the stage.
Geco 2 can also import a custom version of the OE CSV format, with courses already assigned to runners. Using this format, one can export heats as a startlist for the next stage. This trick involves two columns unused by Geco in the original format:
When importing a startlist, Geco will look for the tag ‘Geco-course’ in each entry : if set, Geco processes the next column as the runner course. Otherwise, Geco falls back to the classic behaviour by registering the category course or the default [Auto] course.
For registration on race day, many options are available:
+
button (or pressing mod+I
) and edit the entry by hand;With the auto handler, it is possible to minimize pre-registrations, or even bypass them for lightweight organizations. Geco will create entries only when ecards are actually read. On the fly registration can be done either in racing or training mode.