Qlik Community

New to Qlik Sense

Discussion board where members can get started with Qlik Sense.

Announcements
Qlik® Product Spotlight: Discover what’s possible. Get more from our products.
See for yourself. Register today.
igdrazil
Contributor III

Map Visualisation, custom Mapbox Link

Hi Community,

I (still) have the problem that i can't use my own mapbox map link. I got 2 of them:

1. https://a.tiles.mapbox.com/v4/chebig.noj8p17j/page.html?access_token=pk.eyJ1IjoiY2hlYmlnIiwiYSI6ImNp...

This one opened up in the browser works well, but pasted in Qlik Sense (of course i use the ${z}/${x}/${y} properties in Qlik), it gives me

no map neither an error message.

When i replace 2/3.3/-22.9 with "${z}/${x}/${y}.png" at the end i get the same. I also tried v3 instead of v4, then i get error 401 unauthorized.

2. https://a.tiles.mapbox.com/v4/chebig.noj8p17j/${z}/${x}/${y}.png

This one (is the one that Mapbox links normally look like for Qlik) isn't working at all, neither in the Browser as link nor in Qlik as Slippy Map URL. In Qlik Sense I get the 401 unauthorized error again, in a Browser I get practically the same but spelled a bit different {"message":"Not Authorized - No Token"}. I also tried v3 instead of v4, but the only Difference is the shorter error version in the Browser {"message":"Unauthorized"}.

To notice:

-Browser = Chrome (newest one), also tried IE9+

-Qlik Sense 2.1.1

-Mapbox free account

-Map Created with TileMill, exported as .mbtiles, uploaded to mapbox.com and created a new Project out of it there (no complications at all in the process)

I hope that anyone can help me with this, because i think that there is only a little thing i'm missing, but i'm clueless at the moment

Very Thankful in advance!

Regards

Chris

1 Solution

Accepted Solutions
igdrazil
Contributor III

Re: Map Visualisation, custom Mapbox Link

Problem Solved!

put the access token at the end of the link and delete the "page.html" part

1 Reply
igdrazil
Contributor III

Re: Map Visualisation, custom Mapbox Link

Problem Solved!

put the access token at the end of the link and delete the "page.html" part

Community Browser