Properly Configured Graphhopper Instance Can't Retrieve Tiles from Omni

Open Source Routing Engine
1

Following the tutorial at https://github.com/graphhopper/graphhopper/blob/0.9/docs/core/deploy.md#api-tokens I obtained an API token from omniscale. I attempted to add the omniscale api key for web+server to webapp/js/config/options.js as follows:

////////////////////////////////////////////////////////////////////////////////////////////////////////
// We know that you love 'free', we love it too :)! And so the entire GraphHopper routing engine is not
// only free but even Open Source! The GraphHopper Directions API is also free for development.
// Grab an API key and have fun with installing anything: https://graphhopper.com/#directions-api
// Misuse of API keys that you don't own is prohibited and you'll be blocked.
////////////////////////////////////////////////////////////////////////////////////////////////////////

// Easily replace this options.js with an additional file that you prodive as options_prod.js activate via:
// BROWSERIFYSWAP_ENV='production' npm run watch
// see also package.json and https://github.com/thlorenz/browserify-swap
exports.options = {
    environment: "development",
    routing: {host: '', api_key: ''},
    geocoding: {host: '', api_key: ''},
    omniscale: {api_key: '[API_KEY]'}
};

Then started graphhopper and it failed. I then tried to obtain and use a thunderforest API key:

////////////////////////////////////////////////////////////////////////////////////////////////////////
// We know that you love ‘free’, we love it too :)! And so the entire GraphHopper routing engine is not
// only free but even Open Source! The GraphHopper Directions API is also free for development.
// Grab an API key and have fun with installing anything: https://graphhopper.com/#directions-api
// Misuse of API keys that you don’t own is prohibited and you’ll be blocked.
////////////////////////////////////////////////////////////////////////////////////////////////////////

// Easily replace this options.js with an additional file that you prodive as options_prod.js activate via:
// BROWSERIFYSWAP_ENV=‘production’ npm run watch
// see also package.json and https://github.com/thlorenz/browserify-swap
exports.options = {
environment: “development”,
routing: {host: ‘’, api_key: ‘’},
geocoding: {host: ‘’, api_key: ‘’},
thunderforest: {api_key: ‘[API_KEY]’}
};


This also failed. In both cases I can see in the web developer tools that it is making a generic request to the omniscale server for the tiles:

`https://maps.omniscale.net/v1/mapsgraph-bf48cc0b/tile?service=WMS&request=GetMap&layers=osm&styles=&format=image%2Fjpeg&transparent=false&version=1.1.1&height=256&width=256&srs=EPSG%3A3857&bbox=-7912761.168081446,5213616.825275302,-7911538.175628883,5214839.817727864`

No API key is being appended as a param to this request. It uses the same request regardless of whether I use the thunderforest API. This suggests to me that the documentation is incorrect or missing something. But I have not been able to figure out what.
2

Hi,

if you change anything in javascript you have to rebuild the javascript files. See this tutorial.

Best,
Robin