Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello there,
I have a point layer on Qlik Map which contains over 380000 points and this has triggered the "showing only limited data" warning on Qlik Map
Limiting the number of points is acceptable, but Qlik is automatically selecting which points to display. As a result, data is visible on the left side of the map, but gradually decreases toward the right and eventually displays as zero.
This result is highly misleading. Can I control how Qlik limits the Data? If I zoom out, the data can be limited, but the points should be evenly distributed across the map.
Best regards,
Lan
Hi @LanBiteam
Note that you can increase the number of points shown in the map layer properties:
Obviously that setting is there for a reason, so it won't necessarily cover your 380K points, you could give it a try though.
What might be a good idea is to have different levels of map granularity that the user can either pick or you can automatically choose. Take a look at the Map sheet in this demo app:
https://www.quickintelligence.co.uk/sense/prescribe.html
You can calculate average points in your load script by aggregating the data in a resident load. If you have latitude and longitude by PostCode, and there is also a Town in the data you can do the following in the load script:
Town:
LOAD
Town,
GeoMakePoint(avg(Latitude),avg(Longitude)) as [Town Point]
RESIDENT Data
GROUP BY Town;
Because that average is over all the data it will skew the position of the town point to the location in the town with the most rows of data.
You can then either have a drop down to select which granularity to use or have something like this for the dimension:
=if(GetPossibleCount(PostCode) < 100000, PostCode, Town)
The location dimension would be the same, having something like:
=if(GetPossibleCount(PostCode) < 100000, [PostCode Point], [Town Point])
Obviously, there could be more than one Town with the same name, so that would be a problem. You would be safer using a subset of the postcode to group by, depending on whether you are looking at a single country and what the countries postcode format is (in the UK you can group by the first half, before the space).
Hope that gives you some things to try.
Kind regards,
Steve
Hi @LanBiteam
Note that you can increase the number of points shown in the map layer properties:
Obviously that setting is there for a reason, so it won't necessarily cover your 380K points, you could give it a try though.
What might be a good idea is to have different levels of map granularity that the user can either pick or you can automatically choose. Take a look at the Map sheet in this demo app:
https://www.quickintelligence.co.uk/sense/prescribe.html
You can calculate average points in your load script by aggregating the data in a resident load. If you have latitude and longitude by PostCode, and there is also a Town in the data you can do the following in the load script:
Town:
LOAD
Town,
GeoMakePoint(avg(Latitude),avg(Longitude)) as [Town Point]
RESIDENT Data
GROUP BY Town;
Because that average is over all the data it will skew the position of the town point to the location in the town with the most rows of data.
You can then either have a drop down to select which granularity to use or have something like this for the dimension:
=if(GetPossibleCount(PostCode) < 100000, PostCode, Town)
The location dimension would be the same, having something like:
=if(GetPossibleCount(PostCode) < 100000, [PostCode Point], [Town Point])
Obviously, there could be more than one Town with the same name, so that would be a problem. You would be safer using a subset of the postcode to group by, depending on whether you are looking at a single country and what the countries postcode format is (in the UK you can group by the first half, before the space).
Hope that gives you some things to try.
Kind regards,
Steve
Thanks a lot Steve!
Yes we are also working on limiting the points by first grouping them to regions. This is one way to solve the problem 🙂
The point of average lat and lon is also interesting. Im going to try it out.