6 Replies Latest reply: Jul 10, 2015 6:35 PM by Josh Good RSS

    Point Map Not Showing All Data Points - Example

      Hi, I'm using the following point map in QlikSense to chart forest fires from 2014 in Canada (this point is on Vancouver Island):

       

      qliksensemap.jpg

      Which is backed by the following data (lat, long, etc.):

       

      qliksensedatabehindmap.JPG

      What you can see above is that the "frp" column of data has been considered for the yellow items, thus leading to a total sum of 73.1 MW (this is how fires are rated in power). However, the red data does not affect the data point even though it has the same longitude, as in, its "frp" value of 51.7 is not included in the sum. Now, this may be due to the fact that the latitude is slightly different, however, I am stuck here as something extremely weird happens if I remove my location filter:

       

      qliksensemap2.jpg

       

      After removing the filter, notice how there's no map points at all where there was at least the one above previously on that island (on Vancouver Island)? How can that be possible? Removing filters should only expand the map points, not reduce the map points.

       

      So I'm stumped on two fronts:

       

      1. With no filters set, it appears not all map points are being shown, there should be many more points looking at the data.
      2. How far apart do latitudes and longitudes need to be for two map points to be shown vs both points being aggregated into a larger map point? I thought in the data above those three points were very close (yellow and red are in the same area) and would be aggregated into one map point. Is that not the case?

       

      The logic behind my Measure's expression is very simple:

       

      Sum(if(year(acq_date)=2014,if(confidence > 80,frp)))

       

      Essentially, sum the "frp" if we have over 80 confidence and if the date is 2014.

       

      Thank you for your insights!

       

      Message was edited by: Ryan Park Can't understand why this was not approved, please leave a message as to why if you disapprove a post, otherwise it's a mystery.

        • Re: Point Map Not Showing All Data Points - Example

          Bonus question: Why are my latitudes and longitudes being rounded so strangely vs the original data? For instance:

           

          longitude in data: 126.882

          longitude in QlikSense: 126.8820000000001

           

          I believe the extra digits are rather unnecessary, no?

          • Re: Point Map Not Showing All Data Points - Example
            Josh Good

            Hi Ryan,

             

            I believe what you are running into is a point limitation on the mapping object.  Currently the mapping object is limited to 1000 data points.  Note at the bottom of your image says that a limit data set is being displayed.

             

            -Josh

            Qlik

             

            PS  You post wasn't rejected it just entered our moderation queue.

              • Re: Point Map Not Showing All Data Points - Example

                Hi Josh,

                I resubmitted the post, it was rejected, I got an email saying so. I just edited it, added that statement about moderation and resubmitted it. Now it's accepted, strange.

                 

                Anyway, as a new user, that limitation is not clear. I felt it was limiting data due to my Measure's expression, which is a filter of sorts. So I would suggest QlikSense comes with a better warning like, "output limited as over 1,000 map points", or something else that makes it clear why there are limited points being shown.

                 

                 

                Ultimately, this limitations is unfortunate. People will expect certain points to be on the map, but they won't see them and then they'll think the map is erroneous. As I did. I understand that having the limitation is probably due to the fact too many points is hard to visualize on a map, but it should be up to the user to decide how to filter points to clear up the clutter.

                 

                 

                Oh well, we're demoing all of the BI products out there, so hopefully this isn't a weakness of QlikSense that the others can do, because I like most things about QlikSense...

                 

                Thanks for your answer, marking it as such.

                 

                EDIT: PS: Any word on why QlikSense is rounding my longitude and latitude as it is? It's adding 10 trailing zeros followed by an integer in many cases...