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 ✔️

Repository:

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)

Repository:

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 ✔️

Repository:

Flygon

Repository:

RealDeviceMap

• PR 513 (opens in a new tab)

Repository: