Differences

This shows you the differences between two versions of the page.

--- en:mirally:rally:puntos-de-control [2026/07/07 09:48] – Automatic push translation joan
+++ en:mirally:rally:puntos-de-control [2026/08/26 15:22] (current) – Automatic push translation joan
@@ Line 1: / Line 1: @@
 ====== Control points (CPs) ======
-As on the registrants’ page, look for the option to add an Excel file. If the Roadbook has been created using Roadbook Designer, upload the CP file found in the .ZIP folder generated when the Designer file was converted.
+Just as on the register page, look for the option to upload an Excel file. If the Roadbook has been created using Roadbook Designer, upload the CP file found in the .ZIP folder generated when the Designer file was converted.
-If not, download the ‘Download Example’ template, add the checkpoint data and upload the Excel document, setting the date to the day the stages are run.
+If not, download the ‘Download Example’ template, add the checkpoint data and upload the Excel document, specifying the date on which the stages are run.
 {{es:mirally:images:pcsexcel.png}}
@@ Line 9: / Line 9: @@
 \\
-==== Edit control points from MiRally ====
+==== Edit control points via MiRally ====
 {{es:mirally:images:pcslist.png?1000}}
@@ Line 16: / Line 16: @@
 <WRAP box noteyellow>
-  - Bearing: indicates the direction. If, within the control point’s radius, there is a change in direction compared to the first entry point, the bearing must be adjusted manually. If the control points have been created using Roadbook Designer, the bearing is already correct.
+  - Bearing: indicates the direction. If, within the PC’s radius, there is a change in direction from the first entry point, the bearing must be adjusted manually. If the PCs have been created using Roadbook Designer, the bearing is already correct.
 </WRAP>
@@ Line 25: / Line 25: @@
 . Valid: to deactivate a CP. \\
 . Type: \\
-  * Regularity: the rally route book takes precedence. Participants must set off and pass through the CP at their scheduled time.
+  * Regularity: the rally roadbook takes precedence. Participants must set off and pass through the CP at the specified time.
   * Passage: checkpoint.
   * Monte Carlo Start: when the participant arrives, they wait for the next minute and then set off. The programme calculates the penalties for that minute.
   * Monte Carlo CP: CP times are recalculated based on the participant’s start time.
   * Flying Start: the participant must pass through the start point without stopping. The system records the exact time of passage and CP times are recalculated based on the start time. The CPs must be Monte Carlo CPs.
-  * Stopped Start: the competitor must stop exactly at the start point (km 0) before the final start. The accuracy of this start is not very good and may vary by 1 or 2 seconds; therefore, it is not recommended if you can start at exactly zero seconds or 30 seconds. The CPs must be Monte Carlo CPs.
+  * Stopped Start: the participant must stop exactly at the start point (km 0) before the final start. The accuracy of this start is not very good and may vary by 1 or 2 seconds; therefore, it is not recommended if you can start at the exact zero-second mark or at 30 seconds. The CPs must be Monte Carlo CPs.
-  * C.H.: time control.
+  * C.H.: time checkpoint.
   * Earn Points: for competitions where points are awarded for reaching milestones.
   * Measure distance
-  * Arrival Time: time of arrival at the finish line. To impose penalties in the event of a delay. IMPORTANT: this type of CP marks the end of the rally; no further data will be processed thereafter.
+  * Time of Arrival: time of arrival at the finish line. To apply penalties in the event of a delay. IMPORTANT: this type of CP marks the end of the rally; no further data will be processed thereafter.
 </WRAP>
 </WRAP>
+==== ==== CP Validation
+To check that the CPs are correct and there are no errors, the system uses the DIST tool. \\
+This tool compares the distance between the event’s control points with the distance shown on Google Maps. \\
+To generate this DIST file, open the ‘More’ drop-down menu and click on ‘Download DIST’. An Excel file will then be downloaded, containing the following:
+\\
+{{es:mirally:images:dist.png?800|}}
+\\
+<WRAP box noteblue>
+  * “From Ref”: Start control point.
+  * “To Ref”: Finish control point.
+  * “Partial”: indicates the split time measured by the organiser between those points.
+  * “Line”: distance between the points in a straight line.
+  * “gDriving”: driving distance according to Google Maps.
+  * “gWalking”: walking distance according to Google Maps.
+  * “From / To”: the coordinates from point A to point B.
+</WRAP>
+To interpret this file, you need to go through it line by line. Look at the values in the different columns and check, in the brackets, the difference between that value and the value measured by the organiser. \\
+Small differences may be due to the route and the organiser’s measurement may be correct, but if the difference is considerably high over short distances, we must pay attention as there may be an error. \\
+In such situations, use our Web Roadbook tool, which can be accessed via the following link: https://rabbitrally.com/webroadbook  \\
+Here, you should paste the “From / To” details to view the route on Google.
+{{es:mirally:images:webroadbook.png?800|}}
+\\
+We can also check the PC on the map in the ‘Latest Positions’ screen. \\
+{{es:mirally:images:comprpcsup.png?600|}}
+\\
+This process detects an error in the ZR1’s PC at km 10,584
+{{es:mirally:images:dist2.png?800|}}
+\\
 <WRAP danger>
-Once the Rally has started, CPs must not be deleted, as this may affect the system’s calculations. To invalidate them, the ‘Valid’ tick box must be unticked.
+Once the Rally has started, PCs must not be deleted, as this may affect the system’s calculations. You must deselect the ‘Valid’ tick box to invalidate them.
 </WRAP>