Skip to main content

FAQ About Maps and Course Data

This page is a short collection of questions about maps and course data. If you want to review how to think about event areas or spot placement, also see Operations Guide - Preparation Before the Event.

What map formats are supported?​

NaviTabi supports the following map formats.

KMZ, raster map overlay​

  • The most common format for orienteering and rogaining
  • A ZIP archive containing tile images georeferenced with GroundOverlay in KML
  • The file size limit is 10MB. Larger files increase memory use and may make the app slower or more likely to crash during play, so keeping the file as small as possible is recommended
  • Do not use Japanese characters in filenames inside the KMZ
  • You can also create a KMZ directly from an image with the in-app calibration wizard (iOS / Android)

TMS, tile map service​

  • Tile delivery by a URL template in {z}/{x}/{y} format
  • You can define a zoom level range, default 10 to 18
  • Overzoom, enlarged display at high zoom levels, is also supported

KML, vector overlay​

  • Vector data such as polygons, line strings, and points can be shown as an overlay
  • Used as a supplemental layer over the main map, Organizer Plan feature
  • File size limit: 2 MB
  • Configuration is done from the course edit screen of the mobile app (iOS / Android). The web version supports neither display nor import
  • Detailed steps: Course and Spot Settings - Import a KML vector overlay

Default background maps​

If you do not configure a custom map, the following background maps are used automatically.

  • Events in Japan: GSI map
  • Events outside Japan: OpenStreetMap

How do I replace the base map with my own map?​

You can replace the map on an event basis by importing a KMZ map image into the app.

How to create a KMZ file​

  • Export it from orienteering mapping software such as OCAD. Output resolution 150 to 200 dpi and tile size 512 × 512 are recommended
  • You can also use Google Earth Pro on desktop to align a map image and create a KMZ file
  • In the app (iOS / Android), you can use the in-app calibration wizard to create a KMZ directly from an image

The map does not display correctly​

If a KMZ map does not display​

Check the file size

  • The KMZ file size limit is 10MB. If it exceeds the limit, or if a large file makes the app sluggish, lower the image resolution or adjust the tile size

Check the KMZ structure

  • A doc.kml file exists at the root
  • The KML contains a GroundOverlay element and a LatLonBox
  • Tile images are placed under the files/ directory
  • Filenames do not contain Japanese characters

Check georeferencing

  • Confirm that latitude and longitude ranges are set correctly
  • If calibration is off, redo the calibration

If a tile map does not display​

  • Check that the tile URL template uses the correct {z}/{x}/{y} format
  • Check that tiles exist in the specified zoom range
  • Check that the tile server is reachable

If a KML vector overlay does not display​

  • Check that the file size does not exceed 2 MB
  • Check that the Placemark in the KML contains a LineString or Polygon
  • Elements that specify <visibility>0</visibility> are not drawn

If the map is slow to display​

  • Try clearing the tile cache from the app settings and reloading it (How to clear the cache)
  • Check that the network environment is stable

I want to create an event that uses multiple maps​

The map you can set for the whole event is one. If the event spans multiple areas, consider one of the following.

Method 1: Combine them into one large map​

Create a single KMZ map that includes all areas. If the file stays within 10MB, this is the simplest option.

Method 2: Split the event by area​

Create separate events for each area and assign a different map to each one. Participants join them as separate events.

Map library

Created maps are saved in My Maps and can be reused across multiple events. From Map Management in the web admin screen, you can review and manage the saved map list.

If you are unsure whether multiple areas really should be combined into one event, also check the area criteria in Operations Guide - Preparation Before the Event.

I want to import or export course data​

NaviTabi supports multiple formats for importing and exporting course data.

IOF XML 3.0​

This is the international standard format in orienteering.

Import

  • Parses RaceCourseData and reads spot coordinates and course structure
  • Supports Score courses, Score (Free Start and Finish) courses, and Fixed Order courses
  • You can create a new event or add to an existing event

Export

  • Exports result data in ResultList format
  • Includes split time or lap data for each participant
  • Only Fixed Order courses are exported; Score courses are not included
  • The output file is sent as an email attachment

CSV​

Spot data can also be exchanged in a simple text format, Organizer Plan feature. To keep spots inside the app without going through files, use My Spots and Public Spots (photos are kept too).

Import

  • Four columns: name, description, latitude, longitude
  • Latitude must be within -90 to 90, longitude within -180 to 180
  • Photos need to be registered separately

Export

  • Exported with the same four-column structure, UTF-8 with BOM
  • Latitude and longitude are exported with eight decimal places

GPX​

  • Participant GPS tracks can be exported in GPX 1.1 format
  • Download is available from the web management screen

I want to create several variations of the same course (copy a course)​

Within the same event, you can copy a course and change only its points or type (the spots are shared with the original). See Event Hosting FAQ — Can I copy a course?. To reuse spots in a different event, use CSV export (export the spots, then import them into the other event) instead of copying.

Can I change the size of checkpoint circles?​

Yes. Open the option menu in the top-right corner of the course edit screen and choose Control Circle Size (the selection dialog shows it as "Control circle radius". You can choose from 50m (default) / 30m / 18m / 10m).