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.
PS You post wasn't rejected it just entered our moderation queue.
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...