Add support for any remote API or datasource to Koop. Dive into the docs below or check out a working sample here.


Every provider must have a file called index.js. Its purpose is to tell Koop how to load and use the provider. The keys and values are enumerated in the example below.


Every provider must have a Model. This is where almost all of the business logic of the provider will occur. Its primary job is to fetch data from a remote source like an API or database and return GeoJSON to Koop for further processing.

Function: getData

Models are required to implement a function called getData. It should fetch data from the remote API, translate the data into GeoJSON (if necessary) and call the callback function with the GeoJSON as the second parameter. If there is an error in fetching or processing data from the remote API it should call the callback function with an error as the first parameter and stop processing.

Cached vs Pass-Through

Providers typically fall into two categories: cached and pass-through.


Pass-through providers do not store any data, they act as a proxy/translator between the client and the remote API.

Koop-Provider-Yelp is a good example. The Yelp API supports filters and geographic queries, but it only returns 20 results at a time and there is no way to download the entire Yelp dataset.

It makes sense to use a pass-through strategy if at least one of the following is true:

The request below fetches data from yelp and translates it into Geoservices JSON


GeoJSON can be retrieved as well



Cached providers periodically request entire datasets from the remote API.

Koop-Provider-Craigslist is a good example. The Craigslist API returns the entire set of postings for a given city and type in one call (e.g. Atlanta apartments). The data also does not change that frequently. Therefore the Craigslist provider uses the Koop cache with a TTL of 1 hour, guaranteeing that data will never be more than an hour out of date.

It makes sense to use a cache strategy if at least one of the following is true:


Providers can do more than simply implement getData and hand GeoJSON back to Koop’s core. In fact, they can extend the API space in an arbitrary fashion by adding routes that map to controller functions. Those controller functions call functions on the model to fetch or process data from the remote API.

Enable/Disable parameters

Recall the getData function takes in a req that has a set of params:

By default the host parameter is disabled and the id parameter is enabled. So requests like the following would work:


To enable the host parameter, edit the index.js file and set hosts to true. Then requests like the following will work:


Sometimes, your provider may need no parameters at all. To disable the id parameter, edit index.js and set disableIdParam to true. Then requests like the following will work:



This file is simply an array of routes that should be handled in the namespace of the provider e.g.

In the example above, the provider namespace is agol, and arcgis and e5255b1f69944bcd9cf701025b68f411_0 are parameters. Anything that matches /agol/*/datasets/* will be be handled by the model.

Each route has:



The purpose of the Controller file is to handle additional routes that are specified in route.js. It is a class that is instantiated with access to the model. Most processing should happen in the model, while the controller acts as a traffic director.

As of Koop 3.0, you do not need to create a controller. If you want to add additional functionality to Koop that is not supported by an output plugin, you can add additional functions to the controller.



In addition to implementing getData, the model exists to interact with the remote API and to serve the controller. Any function the controller would need to call to handle a request should be implemented as a public function on the model.