MyOMaps
Like us on Facebook
  • Home
  • Overview
  • Results
  • User Guide
    • Main Screen
    • Main Menu
    • Race Screen
    • My Tracks
    • My Times
    • Race Results
    • Time Details
    • Creating a Map
  • Users
    • Mapper
    • Event Organiser
    • Orienteer - Training
    • Orienteer - Competitor
    • Hiker or Tourist
  • Technical
    • FAQ
    • Releases
    • Scoring
    • Maps and Courses >
      • OCAD - Maps and Courses
      • Set a Course with Google Earth
      • Set a Course with Google Maps
      • File Names - Setting Modes
    • GPS Accuracy
    • A-GPS Assisted GPS Issues
    • Course Setting for GPS
    • Carrying a SmartPhone
    • GPS Settings
    • Check Map and Control Locations
    • Use Map Transparency to check GeoReferencing
  • User Agreement
    • User Agreement & Privacy Policy
    • Event Terms & Conditions
  • Contact

Map and Course File Names - Setting Modes

Map Files 
The map file name (KMZ) is not required to be of any specific format except it cannot contain underscore characters (i.e. “_”).
 
Course Files 
The naming of the course file:
  • becomes the Event Name in MyOMaps and RouteGadget
  • can determine the course type (line, scatter…) and punching mode (auto, user…)
 
The MapRun App only displays events and folders that have names starting with “MR”.
 
Scatter:
A course file name containing:
  • PXAS is autopunch scatter
  • PXUS is user punch scatter
If PXAS or PXUS is followed by a number, this is the number of controls at need to be punched, otherwise ALL controls need to be punched.
 
For example if 20 controls are placed:
  • Taringa Long PXAS16.kml – requires 16 controls to be punched (using autopunch)
  • Taringa Medium PXAS12.kml – requires 12 controls
  • Taringa Short PXAS08.kml – requires 8 controls.
 
Details:
  • “Taringa Long” – Any name for the event except the filename cannot contain underscore characters (i.e. “_”).
  • “PXAS” – The punching format for this event is “Auto Punch” i.e. the App automatically punches the control when it comes in range of the control. The event is also a Scatter (as distinct from a Line Course event). All controls need to be punched for a valid run.
  • “PXUS” -  The punching format for this event is “User Punch” where the user needs to tap a button to punch. The event is also a Scatter (as distinct from a Line Course event). All controls need to be punched for a valid run.
  •  “PXASxx” or “PXUSxx” – Is an AutoPunch/UserPunch Scatter event with a specific (minimum) number of controls that need to be punched for a valid run.
  • Controls can only be punched once.
 
 
Score:
 
For a score event, the course file should contain:
“PXAS” or “PXUS” followed by “ScoreQxx” or “ScoreVxx” where xx is the time in minutes
 
The MapRun App is specifically tailored for Score Events. It only displays folders and events with names starting with “MR”. MapRun events can be used in MyOMaps too.
 
For example:
  • Taringa PXAS ScoreQ40.kml
  • MR Taringa PXAS ScoreQ40.kml (for a MapRun event)
 
Details:
  • “Taringa” – Any name for the event except the filename cannot contain underscore characters (i.e. “_”).
  • PXAS” – as described above for scatter events.
  • “ScoreQ40” – This is a score event with a 40min time limit, and “Q” designates “Queensland scoring” rules i.e.: The points for a control are the control number rounded down to the nearest multiple of 10 and the penalty for late completion is 30 points per minute (or part thereof).
  • An alternative scoring system is available ie ScoreV40 for a 40min time limit with “V” designating “Victorian scoring” rules: All controls are worth 20 points and there is a penalty for late completion of 20 point per minute (or part thereof).
 
PIN:
 
If the course file name includes “PZ” there is a PIN on this event. The map is still visible without the PIN, but not the course. If the PZ is followed by a time and dates of the format: “PZHHDDMMYYYY” there is a PIN on this event up to HH hours (00 to 23) on day DD of Month MM in Year YYYY.
 
The time is typically set as the time of the end of the start window, so that after that time, it is not necessary to remember (or know) a PIN.
 
PINs are automatically determined based on the filename. They are not stored by the server or the App. The PIN for an event can be displayed using a function on the MyOMaps Admin Page.
 
PINs restrict access to the course in both the App and RouteGadget.
 
Example:
 
Taringa PZ1921022017 PXAS ScoreQ40.kml
Is a Taringa event, with a PIN that expired at 7pm on 21 Feb 2017. It is a 40min score event using auto-punch to Queensland scoring rules. 

Powered by Create your own unique website with customizable templates.