External Integrations

ReactMap

• Remove the need to have an areas.json file by loading your managed geofences straight from Kōji
• You must set two config values to use Kōji with ReactMap

1. First set your Kōji Bearer Token:

   • api.kojiOptions.bearerToken
   • Your Kōji Bearer token

2. Then set ReactMap to call the Kōji API

   • map.general.geoJsonFileName
   • Example: http://{koji_ip}/api/v1/geofence/feature-collection/{project_name}
   💡

   You can use unique project names for Multi-Domain setups!

Supported Features

• Polygons ✅
• MultiPolygons ✅

PoracleJS

• Remove the need to have a geofence.json file by loading your managed geofences straight from Kōji
• You must set two config values to use Kōji with Poracle

1. First set your Kōji Bearer Token:

   • config.geofence.kojiOptions.bearerToken
   • Your Kōji Bearer token

2. Then set Poracle to call the Kōji API upon startup

   • config.geofence.path
   • Example: http://{koji_ip}/api/v1/geofence/poracle/{project_name}

Supported Features

• Polygons ✅
• MultiPolygons ½ (PoracleWeb and !area show does not support MultiPolygons)

Golbat

• Remove the need to have a geofence.json file by loading your managed geofences straight from Kōji
• You must set two config values to use Kōji with Golbat

1. First set your Kōji Bearer Token:

   • koji.bearer_token
   • Your Kōji Bearer token

2. Then set Golbat to call the Kōji API upon startup

   • koji.url
   • Example: http://{koji_ip}/api/v1/geofence/feature-collection/{project_name}

Supported Features

• Polygons ✅
• MultiPolygons ✅

Dragonite

• You must set two config values to use Kōji with Dragonite

1. First set your Kōji Bearer Token:

   • koji.bearer_token
   • Your Kōji Bearer token

2. Then set the Kōji url

   • koji.url
   • Example: http://{koji_ip}

Supported Features

• Polygons ✅
• MultiPolygons ½ (Works, but is downconverted to a Polygon, may produce unexpected results)
• Auto quest, Pokemon, and fort route calculations, both in the admin panel and used server side

Flygon

• Syncs all geofences from Kōji to Flygon in the given project at startup
• You must set two config values to use Kōji with Flygon

1. First set your Kōji Bearer Token:

   • koji.bearer_token
   • Your Kōji Bearer token

2. Then set the Kōji url

   • koji.url
   • Example: http://{koji_ip}

3. Then set the Kōji project name that you want Flygon to use when calling the API

   • koji.project_name
   • Example: project_name

4. Lastly, since Flygon loads all of the areas at startup and overwrites them in the database at startup, there's a config option to enable or disable this behavior.

   • koji.load_at_startup
   • true or false

Supported Features

• Polygons ✅
• MultiPolygons ½ (Works, but is downconverted to a Polygon, may produce unexpected results)

Flygon Admin

• Enable buttons in the dashboard panel to make calls to Kōji to calculate clustered and bootstrapped routes.
• You must set two config values to use Kōji with Flygon Admin

1. First set your Kōji Bearer Token:

   • koji.bearer_token
   • Your Kōji Bearer token

2. Then set the Kōji api_endpoint

   • koji.api_endpoint
   • Example: http://{koji_ip}

Supported Features

• Bootstrap 70m Circles
• Bootstrap 9x9 S2 Cells
• Pokemon 70m clustered routes
• Quest 78m clustered routes
• Gym 9x9 clustered routes

RealDeviceMap

• PR 513 (opens in a new tab)

rdmGruber

• Remove the need to have a geofence.json file by loading your managed geofences straight from Kōji
• You must set two config values to use Kōji with rdmGruber

1. First set your Kōji Bearer Token:

   • config.kojiOptions.bearerToken
   • Your Kōji Bearer token

2. Then set rdmGruber to call the Kōji API upon startup

   • config.kojiOptions.url
   • Example: http://{koji_ip}/api/v1/geofence/poracle/{rdmGruber_project_name}

Supported Features

• Polygons ✅
• MultiPolygons ❌