How to timing a race with start and finish in the same location

Situation and common solutions

When the start and finish are in the same location, there may be difficulties with timing. There are two common solutions:

1. Device location change
   Devices can be moved manually or scheduled to switch automatically based on a specific time. 
2. Maximum start time
   By setting a maximum time on the “Start” point, for example 10 minutes, subsequent reads will be assigned to the next point in that location, usually “Finish”.

The problem

In some events, the first runners reach the finish while others are still "starting". This creates two challenges:

• Device location change: It isn't possible to reconfigure devices from “Start” to “Finish” because both points are active at the same time.
• Maximum start time: If applied, the reads of runners still starting after the configured time will be assigned to “Finish” instead of “Start”.

Keep in mind that, by default, start-type points assign the last read. 

If we cannot use the previous solutions, we need other options to assign times correctly.

Solutions in Copérnico

Copérnico offers two key features:

1. Assign the first read
   Allows configuring the valid read as the first one at any point, including start-type points. This way, the first read is assigned to “Start” and the next read at that location to “Finish”.
2. Assign times based on later points
   Copernico will not assign times to previous points if there is a time in a later point. For example, adding an intermediate point (such as km 5) to assist timing:
   • If the runner crosses the intermediate point, the finish time will be assigned correctly, as it is a later time.
   • If the runner does not pass (or has no time) at the intermediate point, it will be necessary to have the first read configured at the start point.

Additionally, when there are no runners starting, you can configure the "maximum time" at "start" point so that subsequent reads are assigned to the finish.

Practical example: 10K race with start and finish at the same location

Runner with times at all points

Starts → time assigned to “Start”.
Time at km 5 → having time at this point means no time can be assigned to "Start". It does not matter if first or last read is configured.
Finishes → time assigned normally.

Runner without time at start

No start time, but with time at km 5 → consolidates start. Having time at this point means no time can be assigned to "Start".
Finishes → time assigned normally.
Start point remains with time 0.

Runner without time at intermediate point

Has start time, but doesn't has at km 5 → start isn't consolidated.
It is necessary to have the first read configured at start to assign the finish correctly.

Runner without time at start or intermediate point

Generates an issue: it's impossible to determine if the runner was starting or finishing.
It can be estimated by the finish time, but it isn't reliable.