QREvents Manual

Version 1.0+

App is for organizing small orienteering events, quizzes and more.

Workflow is as follows (see image set below and short demo video at the bottom of this page):

1) Create new event by selecting scenario of your choise, edit event data, set event times.

2) Some basic controls for selected scenario are created while creating the event. Append controls as necessary. Control entry provides possibility first to scan control QR code. If no scan - enter manually. QR codes have to be prepared in advance using any available software or online code generators. More about controls see below.

3) Basic class for selected scenario is created while creating the event. Modify class as necessary. Course definition principles are described below.

4) Create teams. Team bib is important and must be unique for event. Teams must use bibs defined by organizers. 

5) When all data is entered (actually, controls are what is needed), app is ready to display event QR code, which is for use with Qrenteerings app (AppStore v. 4.0+, GooglePlay v. 2.0+) Basic data contains information about control points, extra data (may be skipped) contains data about controls geocoordinates, optional data (may be skipped, available with Qrenteerings from v.5.0+ on iPhone, v.3.0+ on Android) contains data about mass start of event, etc.

6) After team is finished, scan team splits from Qrenteerings screen. Corrections to splits, if necessary, may be entered manually.

7) See results. If team's splits conforms to class course definition, team scores; if not - team gets DQ.

1. Select existing or create new event


2. Create new event


3. Enter some simple event title, select event type, save, go back to first screen


4. Edit event


5. Set times, start type. Here you can delete entire event, if you like.


6. Set start time, finish time, late time. Start time is important, if event will be with mass start, usually, score/rogain event. 


7. Set controls on course


8. When new event is created, some controls are created. You can edit them, append new ones. More about controls see below.


9. Control editing form. You can scan controls QR code from prepared control post image.


10. Edit classes and course definitions for classes.


11. When new event is created, a class for selected event type is created. You can edit it, append new ones. 


12. Class editing form. Course definition principles are described below.


13. Edit teams.


14. Initially, there are no teams. Create new ones.


15. Team editing form. Enter unique bib number, enter team title, tap to select course, which team will take.


16. You can edit team data, tapping on team. In team editing form you can see team's splits, edit them.


17. Each team must read event's data from QR codes.


18. Mandatory controls' data.


19. Optional controls'GPS data...


20. ... and other optional data, as mass start time, etc.


21. When team finishes, they display teams control visits as QR image, which must be scanned into QREvents.


22. Team may sent splits image and it may be read from this image.


23. Event results are calculated by classes, using course definitions. Course definition principles are described below.


To be continued...



Controls are labels (flags on orienteering course), which are marked with QR code and, optionally, with this codes label and control ID. Every field in form must contain appropriate value as described below.

Field "Control" usually is number of control on course, quiz question number, etc. It may contain capital letters as well.

Field "QR code" must contain only capital letters and/or number digits. QR codes may be prepared on any QR code generator software as text codes. If this is done in anvance, you can use "Read control QR" to scan QR code field.

Field "Value" is point value of control as it is used in score orienteering, rogaining or quiz. For cross-county race we use value of 1 to count controls taken.

Field "Bon/Pen time" is for bonus or penalty time, which is subtracted/added to teams total time, if this control is taken. Number, accordingly, may be positive or negative.

Fields "Latitude" and "Longitude" is for GPS coordinates of control. Format is [-]nnn.dddd Coordinates MUST be entered with exactly 4 digits after decimal point. DO NOT USE "+" SIGN! If coordinates will not be used in event, these fields must be "0".

Field "NFC ID" is for future releases of Qrenteerings client and would be used as complementary code for control reading. User may scan QR code or read NFC tag when visiting control. It is already implemented in Android version.


Classes contains class name and course definition.

Class names usually denotes groups of event participants. Best practice is use of simple abbreviations, like, MO for "men open", etc.

If team is a member of class, teams result will be calculated for that class. Teams' control visits must conform to course definition for this class.

Course definition consists of basic definitions (BD), grouped in sets of BD.

BD is of form [{a,b}Oc1,c2,c3,...,cn],


a means "at least a controls"

b means "max b controls"

O is for order of controls to follow and is one of two: "<" - any order from following list of controls; ">" - in order of following list of controls.

c1, ..., cn - list of controls ID for this BD. Control itself may be BD as in "score/rogain" example course.

Three basic event types are offered, when creating new event - score/rogain, cross-county and quiz. Experienced users may create also more complicated course definitions on base of given. Results calculation is not yet guaranteed in such cases.


1. "score/rogain"


That means - must be taken exactly 3 "controls" in that order. First, start control S. Second, no or max of 3 controls in any order from list of controls with IDs 1, 2, 3. An, finally, finish control F.

2. "cross-county"


That is - must be taken exactly 5 controls in that order - S,3,2,1,F.

3. "quiz"


Quiz consists of 3 questions, each offers 3 choises. Questions may be answered in any order, at least one question must be answered, selecting exactly one answer for each question.

Short demo video.