Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Google Maps Extension with Heatmap support.
QlikTech takes no responsibility for any code and QlikTech Support Agreement does not cover issues with this extension.
Please review Googles license agreement before you put this into production.
Big thanks to pablolabbe for contributing to the project.
Download
mindspank/GoogleMaps-Heatmap-QV11 · GitHub
Introduction
A new addition to the Google Maps family. This extensions will take your data points and produce a heatmap on top of a Google Map.
A good tool easily spot areas with higher intensity of data points. There is no selection support for this extension has there is no markers available at the moment.
You can either use the extension 'as is' or use it as a base to further customize it to fit your needs.
2013-12-14
Finally tracked down the errors when you tried to pass in faulty data.
Less DOM-calls.
2013-06-04
Added a check that QV passes valid data points to Google. If you are passing an invalid data point it will log it to the console in your browser.
Also enabled weighted data points. Now the weight if your data point in the heatmap will correspond to your expression value. If you want equal weight between the points, e.g the original heatmap where the number of data points determined your heat level, set a arbitrary value of =1
If you build something awesome please share it with the community!
Live long and prosper.
Shouldn't matter. I have not tested QV with IE11 so can't really say.
But the technical reasoning behind it is that the heatmap layer from Google Maps are using canvas which got supported natively by IE9.
When you switch over to webview inside of QV - we utilize the IE api to render the page inside of QV so sadly we are also dependent on keeping IE semi up to date.
Gotcha, I am going with 10 to be safe. Thanks very much, I'm excited to
get this working.
Best Regards,
Aron F Elston
PwC | Manager
Office: 2673301536 | Mobile: 9176931822
Email: aron.f.elston@us.pwc.com
PricewaterhouseCoopers LLP
Two Commerce Square, Suite 1700, 2001 Market Street, Philadelphia,
Pennsylvania 19103-7042
http://www.pwc.com/us
Print less, think more.
Hi Alex,
I installed IE10 and now webview doesn't work in Qlikview. Any idea why
this would happen or what I should do?
Best Regards,
Aron F Elston
PwC | Manager
Office: 2673301536 | Mobile: 9176931822
Email: aron.f.elston@us.pwc.com
PricewaterhouseCoopers LLP
Two Commerce Square, Suite 1700, 2001 Market Street, Philadelphia,
Pennsylvania 19103-7042
http://www.pwc.com/us
Print less, think more.
Gah, sorry my mistake.
I'm guessing you are running QV11.2 SR4 or below... which of course does not work with IE10...
Either downgrade to IE9 and it will work with QV11.20 SR4 and below and the heat map.
Or upgrade to QV11.20 SR5 and it will work with IE10 and the heat map.
Or craft a voodoo doll out of the IE team and silently curse them under your every breath.
Building Voodoo doll now.
I'm downgrading ot IE9 for now, maybe I'll
upgrade later. Thanks!
Best Regards,
Aron F Elston
PwC | Manager
Office: 2673301536 | Mobile: 9176931822
Email: aron.f.elston@us.pwc.com
PricewaterhouseCoopers LLP
Two Commerce Square, Suite 1700, 2001 Market Street, Philadelphia,
Pennsylvania 19103-7042
http://www.pwc.com/us
Print less, think more.
Hi Alexander,
I'm using IE8 and had the same issue.
Is there any alternative?
Tks
Fabio
Ye, upgrade your version of internet explorer.
Hi Alex,
first of all thanks for taking the time to develop this extension. Efficient visualization of geographical information is still not satisfyingly available and your solution fills a gap for heatmaps!
I noticed by alert()ing the value of
this.Data.Rows.length
in the script file that apparently no matter how many points are selected in QV only 20'000 will be provided to your extension. This is a bit inconvenient for my use case as I would like to visualize about 500'000. And I know that Google Heatmaps is indeed able to handle this many points without much ado.
Is this limitation to 20'000 records fix or can I configure it?
Kind regards
Raffael
That limitation is set in the definition.xml file that you will find in the extension folder.
If you open the file you should find a tag called PageHeight which controls the height, amount of rows, of each data page.
Now, I have not really tested the extension with a data set that large so you might run into performance implications.
A way around that problem would be to page the data into smaller chunks to avoid long running loops which tend to halt in IE.
First of all - thank you very much for your really fast answer!
Indeed it works - I can increase the data set limit the way you suggested.
The bad news though is that QV consistently crashes as soon as I increase the limit to something larger than about 50'000. In case you have a suggestion how to approach this setback - it's highly appreciated.
Kind regards
Raffael