Generate point-based results

[fvacek]

In Spain, it is common to use the 1000-points formula (i.e. 1000 * best time / runner’s time)

[sergiogpajares]

As a Spaniard, let me explain what the requirements for Spanish competitions are.

We usually run weekend trophies with prize-giving ceremonies, totally independent of league rankings. These trophies involve combining the results of all (or some) of the stages of the event. Organisers mainly use two formulas to compute the overall result for the event:

• Sum of times
• Sum of points (most popular). Points for each stage are computed as 1000 * (best time / runner's time).

Sum of times is already available in QuickEvent. Sum of points is considered fairer by Spanish orienteers, as we usually mix long distance, middle distance and urban sprint all together in these trophies.

1000-point formula
The computation has the following additional requirements:

• If a runner is disqualified by any reason (e.g. MP, DNS...), the runner gets 0 points but still receives points for the rest of the stages.
• A race for a specific class in any stage could be voided. In this case, all runners in that class get 0 points. The fact that a stage was voided should be stated in the PDF results and CSV export. It would be great if a message explaining the reason is included.
• For events with many stages, you should be able to choose the best X out of Y races. For example, imagine a competition with 6 stages in which only the best 5 are considered. If a runner has points 450, 690, 342, 980, 790, 653, then the resulting score will be 450 + 690 + 980 + 790 + 653 = 3563, and the lowest score (342) is dropped. Dropped stages should be indicated in both PDF results and CSV export.
• You should be able to set the number of decimal places displayed in reports.
• In rare cases, you may not want a stage to be considered at all in the overall result. You should have an option to select which stages count towards the overall result. This is the least important requirement. For example, in a three-stage event (middle, sprint, long), you may only want to include the middle and long distances.
• It would be useful to configure the maximum number of points available for any stage (e.g. 100 or 1000). Spanish rankings often use 100 * (best time / runner's time), while most timekeeping software only supports 1000 * (best time / runner's time).
• It would also be great if you could print awards for the overall classification, as is currently done. However, this is not a requirement.

UX proposal
I think this should be configured at the event level. That way, when you have a multi-stage event, you can define how the overall results are computed once. Then, the different print/export procedures are unaffected, and when you use them, you get the desired output without having to review their configuration each time.

[fvacek]

1. Are you talking about multi-stage events only or does 1000-point formula apply also to single-stage ones?
2. Should be the points printed in new report column, next to time one? We are fighting with A4 page size.

[sergiogpajares]

I'm talking about multi-stage events only. On a single stage we only use time-based results (at least for regular foot-o races).

About reports. Ideally, I think the best option will be to have two reports:

1. Condensed report displaying only final points.
2. Extended report displaying the points and time for each of stages.

Most competitions will only provide report 2. So, we only need to be able to generate report 2.

Report 1
For this report I will just replace times by points

Report 2
I think the easiest way to fit everything on a single A4 is to stack time an points on top of each other.

You can find here a real example.

[sergiogpajares]

By the way, you can find examples of how we display this multistage results at OReplay. Click the runner to see the detail information from each of the stages. (Design targets smartphones)

• Time-based
• Point.based