Qlik Sense SaaS - Map Background Image not displaying

[paulcollins]

Hi - we are evaluating Qlik as an embeddable analytics solution. Trying to configure the Map chart to display a background image from a URL, as a background to some point data - but despite trying all sorts of different configurations, it doesn't  seem to work. A summary of what we have configured in the Map chart object:

- A point layer that is using latitude and longitude from our dataset as location, lat and long is in the range of (51.51xxxxx, -0.08xxxxx) to (51.52xxxxx, -0.09xxxxx) [I've anonymised these values for the purpose of the question]

- Map settings / base map is set to 'None', and projection is set to 'User defined (degrees)' (also tried Mercator, but doesn't seem to make any difference). Note that choosing the default map instead of 'None" renders the data in exactly the right positions on the map, so we know our lats and longs are correct.

- A background layer who's format is "Image", the URL is correct (opening in the URL in another tab works fine and I believe that the background image is fetched by the browser, not by the server). The image position Top Left Corner and Bottom Right Corner are using latitude and longitude values (Top Left is (51.51xxxxx, -0.08xxxxx), Bottom Right is (51.52xxxxx, -0.09xxxxx)) so the image co-ordinates and our data co-ordinates are using the same model.

I've also tried swapping the image URL to the one that is used in a related tutorial (https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Resources/Images/ui_map-image-back... but this also does not make any difference.

Is there anything obvious I'm missing?

Also as an aside, could you clarify if background images (once this is working) are automatically scaled and rotated based on the Top Left / Bottom Right positioning values?

Many thanks

Paul

[Alvaro_Palacios]

Hi Paul,

Did you add the image URL to the Content Security Policy in the Management Console? For example, I'm using the OpenStreeMap tile as map background so I had to add the corresponding directives for that origin (see screen dump below)

I hope that resolves the issue.