OCAD and OpenOrienteering Mapper represent the primary desktop choices for drawing sports cartography to strict specification. While OCAD provides specialized proprietary modules and print preparation for Windows, OpenOrienteering Mapper delivers an open-source cross-platform desktop alternative. At Gratic, we build a browser-based vector editor that removes desktop installations and per-seat licensing hurdles entirely, importing national vector datasets directly and exporting files compatible with OCAD for downstream cartographic production workflows.
How do OCAD and OpenOrienteering Mapper manage cartographic vector engines?
OCAD and OpenOrienteering Mapper both execute vector rendering through specialized rule-based engines built to display International Orienteering Federation standards. OCAD runs on Windows and relies on a structured desktop codebase, whereas OpenOrienteering Mapper runs natively across multiple operating systems. Both programs process vector point, line, and area symbols according to exact millimetre dimensions rather than arbitrary pixel scales.
Desktop vector engines calculate how line symbols, border tracks, and dashed contours interact on a physical sheet. According to OCAD, the software is now up to version 18 and has been translated into more than 20 languages. Its vector drawing engine has evolved over decades across desktop Windows releases to handle specialized orienteering linework, custom symbol tables, and print output preparation.
OpenOrienteering Mapper uses an open-source vector codebase that supports IOF specifications such as ISOM and ISSprOM. The application executes locally on Linux, macOS, and Windows without ongoing software fees, allowing cartographers to draw contours and point features directly from their local hardware.
At Gratic, we approach vector drawing through an engine running inside a standard browser tab. Rather than maintaining desktop binaries, our engine renders standard IOF symbols directly on a canvas measured in millimetres. The screen and exported output run from the same internal drawing list, ensuring linework fidelity without requiring desktop client software.
What are the technical trade-offs between local desktop suites and web editors?
Local desktop suites require manual file distribution, version alignment across club members, and local installation rights on individual operating systems. Web-based vector editors handle data ingestion by connecting directly to public surveys without local filesystem overhead. However, desktop engines operate completely offline, whereas browser-based tools rely on remote network connections to pull initial elevation tiles and external survey features.
- Ingest external vector and elevation layers
- Apply ISOM or ISSprOM standard symbol rules
- Coordinate concurrent edits across club mappers
Export files compatible with OCAD
Print exact millimetre sheets to scale
When a mapping team adopts a traditional desktop suite, file management often creates version fragmentation. Club members pass project files across email threads or shared drives, risking conflicting edits when two surveyors update adjacent terrain features. Furthermore, according to OCAD, OCAD is only offered as a subscription model since 2018, requiring clubs to budget recurring per-seat fees or transfer seat activations across machines.
OpenOrienteering Mapper avoids software fees by providing open-source binaries, but it still requires desktop installation. If a club provides a shared laptop with restricted administrative permissions, volunteers may struggle to install or update local binaries. The team must also manually download digital elevation models and national geodata files, converting file projections using separate GIS software before drawing begin.
| Technical dimension | Standalone proprietary desktop | Community open-source desktop |
|---|---|---|
| Operating system requirement | Native Windows execution environment | Multi-platform compilation for Windows, macOS, and Linux |
| Software acquisition model | Commercial subscription requiring recurring seats | Open-source release under community licensing |
| Raw survey preprocessing | Manual GIS conversion and contour generation | External GIS reprojection and file translation |
| Real-time multi-user editing | File serialization across local drives and external folders | File exchange dependent on manual revision tracking |
At Gratic, we designed the workflow to begin without a blank sheet or local software installation. Mappers drag a bounding box over their target area, and the editor imports elevation data tile by tile alongside national mapping service vector data. Two mappers can draw features concurrently on the same map from separate machines, eliminating file collisions and version disputes.
How does base data ingestion differ across terrain mapping pipelines?
Base data ingestion in desktop suites typically requires sourcing raw GIS files, reprojecting coordinates, and assigning symbol numbers by hand. In contrast, modern pipelines automate this transfer by querying public mapping endpoints and translating vector shapes directly into IOF symbols. The efficiency of a mapping project depends heavily on how rapidly surveyors convert external survey data into workable linework.
Traditional workflows with OCAD or OpenOrienteering Mapper often begin in external GIS programs. A cartographer downloads contour shapefiles, georeferenced aerial rasters, and lidar point clouds from state databases. These layers are imported locally, where the cartographer must manually assign imported vector layers to specific ISOM symbol definitions like form lines or index contours.
Gratic connects directly to open spatial sources to compress this preparation phase. When you define an area, our pipeline queries available public services—such as the land survey in Finland, PDOK in the Netherlands, IGN in France, or OpenStreetMap globally. It translates that open vector data into standard orienteering symbols while fetching underlying elevation tiles, so surveying begins from structured terrain features rather than manual tracing.
Once field work and drawing conclude, interoperability remains essential for event staging. While Gratic handles the full editing cycle from base layers to print-ready millimetre sheets, it also exports files compatible with OCAD. This ensures that sports cartographers, rogaining directors, and orienteering clubs can integrate their browser-drawn maps into established event workflows and course setting tools.
Frequently asked questions
Can Gratic replace OCAD for course planning software workflows?
Gratic exports files compatible with OCAD, allowing course designers to draw terrain maps online and then open the resulting vector files inside course planning tools like Condes or Purple Pen.
Which operating systems support Gratic compared to OpenOrienteering Mapper?
While OpenOrienteering Mapper provides distinct desktop installers for Windows, macOS, and Linux, Gratic runs entirely in a browser tab on any operating system without installing software or managing licences.
How does Gratic fetch base layers without manual GIS preprocessing?
Gratic pulls elevation data tile by tile and queries national mapping service vector data directly, automatically converting open spatial features into standard IOF orienteering symbols.
Is Gratic intended for general-purpose municipal GIS work?
Gratic is designed specifically for sports cartographers, orienteering clubs, and adventure racing organizers; it is not built for general-purpose municipal GIS departments or commercial navigation app development.
Sources
- OCAD — OCAD - software for Cartography and Orienteering Language Selection Page