I am not able to filter out the values to plot on a “Points on Map” visual.
I am working on a client use case dashboard which draws data from Athena view. After selecting all the countries from the filter, it should show data points in the US as well as the UK and other country regions. However, it is only skewing the data in US, and no points are seen in UK.
Upon selecting the countries individually, it works fine.
I do recall coming across another community post with the same problem, where they suggested to add a hierarchy in the dataset as well. I did that too: in my dataset we have postal_code and city_name fields which I am trying to map on the visual.
The postal_code has values such as ‘US-10118’,‘GB-KW17’. We have added calculated fields on splitting these values to country_part(US) and postal_part(10118). The hierarchy is added on the same. Still this issue persists as we are not able to plot the points all at once.
How do I get all the data points to show up for selecting all the countries? And is this issue coming up due to some overlapping? Please help us find the solution.
Attaching screenshots for reference.
Hi @Shriniket_Wagh, good to see you back in the community!
The problem is likely related to how QuickSight geocodes your postal codes, quicksight’s geocoding can struggle to handle postal codes across countries when they’re all selected at once. Without a proper geospatial hierarchy, it may default to resolving postal codes against the US. When you select countries individually, QuickSight has enough context to geocode correctly, but with “all” selected, it loses that distinction.
I would suggest checking the following:
-
Geospatial hierarchy setup: make sure your hierarchy is set up in the correct order: Country → State/Region → City → Postal Code (top to bottom). The country_part field (US, GB) must be labeled as the Country geospatial data type, and postal_part must be labeled as Zip Code/Postal Code.
-
Use full country names or ISO codes: your country_part values are “US” and “GB”. QuickSight should recognize ISO 2-letter codes, but try using full names (“United States”, “United Kingdom”) to see if that resolves the geocoding ambiguity.
-
Add the country field to the Geospatial field well: in your Points on Map visual, make sure the full geospatial hierarchy (including the country level) is added to the Geospatial field well, not just the postal code. This gives QuickSight the context it needs to plot across multiple countries simultaneously.
-
Check for data volume limits: points on Map visuals have row limits. If your US data has significantly more rows than UK data, the UK points may be getting cut off. Check if there’s a “data points displayed” warning on the visual.
-
Verify the postal_part values: UK postal codes like “KW17” are partial postcodes. QuickSight may not be able to geocode partial UK postcodes reliably. Try using full UK postcodes if available in your source data.
I’ve also attached the links to documentation specific to geospatial data and 2 related community post that might be helpful for your case.
Hope this helps narrow it down!
Hi @WLS-Cesar , thanks for the detailed information!
I have set up the hierarchy mentioned and I am able to see the data plotted correctly, however still there is the “select all” issue. I had connected with AWS Support over this and they mentioned that there is a 10K limit on the number of data points which can be plotted on the map. And half of that if a field is added in the “Color” group. Reference: Point Map and multiple values - #7 by gillepa
If this is legit, then there isn’t much we can do, is there? Do you happen to know any official AWS doc reference for this, because I am unable to find it.
Hi @Shriniket_Wagh,
Yes, that 10,000 limit is real. Unfortunately, I don’t believe there’s official AWS documentation page that explicitly states this number for Points on Map visuals. The visual display limits table lists limits for bar charts, line charts, heat maps, etc., but geospatial maps are notably absent from it. Other community threads also ran into the same issue:
As for workarounds, since the limit can’t be increased, I think your best bet is to use a parameter-driven approach. Show an aggregated view (city-level) when “Select All” countries is active, and only drill down to postal-code detail when a single country is selected. You could implement this with conditional visuals or a calculated field that switches the granularity based on the filter selection.
Hope this helps!
Hi @Shriniket_Wagh,
Hope everything has been well, just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
Thank you.
Hi @WLS-Cesar , thanks for checking in.
Sorry, I was held up with some priority deliverables, hence couldn’t get a chance to revert.
Thank you so much for the guidance!
For now, me and our team agreed to go forward with the parameterized approach for selecting one country at a time.
We have also removed the field from “Color” so it appears uniform with a single color and looks better, as per my client’s requests.
I’ll speak with my team about your specific solution regarding aggregated view (city - level), if we decide to make any updates.
Thanks, again, and wish you a good day. 
