Define details for area scanning: API, scoring

[smaria]

• When can we give details on the positioning API?
• How should the depth measurement be logged and scored?

[smaria]

another point that needs refining: Are there any limits on the updates to the boat? E.g. We definitely won't allow remote control - but we don't mind teams updating higher level goals during the scan time! So, how can we limit this?

[smaria]

I see three possible methods of providing the depth information:

• GPS position with timestamp, in post processing for scoring the depth sounding is first corrected for tide time, then an average for each box is calculated and compared to the race committee reference.
• the teams provide the position already as x and y coordinate of the box and give a single value and timestamp for each box
• the team provides a fully processed dataset, giving a tide-compensated value for each box

The first option is in my opinion the nicest option (and it makes it very difficult to cheat), but it requires a significant amount of post-processing by the race committee

[takluyver]

Limiting updates: I think a good dividing line is that any changes while the attempt is in progress must be decided by automatic systems, not by human input (except for safety reasons or to bring the boat back and finish the challenge).

[smaria]

In this case, an 'attempt' is the time between starting and registering a recovery? (as opposed to: the entire challenge timeframe)

[takluyver]

Yep, that's what I was thinking.