I’m using a Filled Map visual with a column named state_code_clean that contains valid, trimmed, uppercase U.S. state codes. Despite this, QuickSight isn’t recognizing it as a geospatial field. Below are the distinct values (includes a Null value) from that column. I’ve tried multiple fixes without success.
| PA |
| FL |
| AZ |
| LA |
| MT |
| GU |
| NM |
| AK |
| NC |
| OR |
| VT |
| MS |
| AR |
| IL |
| MO |
| HI |
| IN |
| WY |
| UT |
| MI |
| KS |
| MD |
| VI |
| GA |
| DC |
| MN |
| WI |
| NE |
| OH |
| CT |
| NV |
| PR |
| OK |
| AL |
| DE |
| ND |
| CA |
| CO |
| WV |
| KY |
| WA |
| ME |
| RI |
| SD |
| TN |
| VA |
| NH |
| IA |
| SC |
Hi @Nikhil_1912
You may find it useful to review the related Quick community post where a similar filled map visual type issue has already been discussed.
Ensure that the column representing country information is set as a Geographic data type (Country or Region). You can confirm this in the dataset field settings.
Thanks @Xclipse - I’m using a Filled Map in QuickSight with a column state_code_clean that contains valid, trimmed, uppercase U.S. state/territory codes. QuickSight isn’t recognizing it as a Geospatial → State/Province → Code (2-letter) field.
Distinct values observed:
AK, AL, AR, AZ, CA, CO, CT, DC, DE, FL, GA, GU, HI, IA, ID, IL, IN, KS, KY, LA, MA, MD, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NJ, NM, NV, NY, OH, OK, OR, PA, PR, RI, SC, SD, TN, TX, UT, VA, VI, VT, WA, WI, WV, WY, ON
I’ve confirmed there are no leading/trailing spaces, the field is uppercase, and it’s set as a dimension. I also tried:
Refreshing the dataset and the analysis (SPICE and direct query),
Setting the role in Edit dataset → Prepare data (geospatial + State/Province → Code),
Adding a country_code = 'US' field and assigning Country/Region → Code,
Switching the visual to a table and back to a map.
Despite this, the field still won’t drop into LOCATION or isn’t recognized as geospatial.
Could you advise on any additional requirements (e.g., territory handling, mixed-country data like ON for Ontario) or known issues? If needed, I can provide the dataset name and a sample extract.
Hi @Nikhil_1912
Quick fails to recognize state_code_clean as a geospatial State/Province Code due to mixed codes like US territories (GU, PR, VI) and Canada’s ON (Ontario). This combination creates geocoding conflicts without a proper country hierarchy.
I tried with the sample data and following images for your reference.
Thanks @Xclipse, I was able to change the datatype in the legacy experience and it finally worked.
