Posted by
Peter Effeney on
URL: http://maprun.308.s1.nabble.com/Courses-in-IOF-XML-Format-tp19.html
Can I use a course that I have set in OCAD, or PurplePen, or Condes (or other Orienteering course setting systems)?
You can convert IOF XML to KML using a tool at
O-utils.
I’m actually trying to discourage people setting their courses based on an Orienteering Map - that is using OCAD, PurplePen etc … because:
- See
http://maprunners.weebly.com/accurate-control-latlng.html- Older versions to the App allowed direct importing of the IOF XML file - but I no longer support that
- I have had too many cases where people blindly export a course in IOF XML and not check their controls on a satellite image to see where they actually are… and then are disappointed by controls not punching reliably
- Moving a control on an Orienteering Map by just 1mm, moves the point on the ground by 10metres (at 1:10,000). This is enough to upset GPS-based punching (with a 15m tolerance).
- Zooming in further on an Orienteering Map to try to be more accurate with control placement, only goes so far… as no more detail is revealed as you zoom in (unlike on a satellite image).
- For sprint maps with dense features, IOF Mapping rules require that symbols be separated by certain distances, therefore mappers may be required to deliberately place features at Lat/Lng’s that they know are not accurate.
- So if you are wanting to use a course that has been set based on an Orienteering Map, export it, convert it to KML, and check and fine-tune control locations in Google Earth (or similar). Otherwise use high-definition imagery as a background layer in OCAD to give more details of location, or use Lidar layers to help with teh accuracy of control locations.
- Alternatively, you could increase the punching tolerance in MapRunF to allow for less precise control locations.
- My guidance is that if you can see the feature you are using as the control location in Google Satellite imagery and can drop a pin directly on that feature, the control will be within 3m of its real Lat/Lng (Satellite images aren’t perfectly aligned either). With a 15m standard punching tolerance in MapRunF, this will give reliable results.