Amazon Quicksight is not recognizing geospatial data (GPS coordinates or Address, City and state) after troubleshooting steps

Thank you all for reviewing my question. Thus far , I have only gotten it to work by switching to legacy mode in quicksight. Im still cleaning my data etc so will update if any of the other solutions presented here work for me

When working with geospatial data in Amazon QuickSight, you need to explicitly assign geographic roles to your fields to enable map visualizations. The error "Only geospatial fields are allowed" indicates that QuickSight doesn't recognize your fields as having geographic roles.

Here's how to resolve this issue:

1. In the QuickSight dataset editor, select the field you want to use as geospatial data (like latitude, longitude, city, etc.)

2. Look for the "Field list" panel, select the field, and then find the "Geographic role" option in the field properties or dropdown menu.

3. Assign the appropriate geographic role to each field:

• For latitude/longitude: Set one field as "Latitude" and the other as "Longitude"
• For address fields: Set appropriate roles like "City," "State," "Country," or "Zip code"

4. After assigning geographic roles, save your dataset changes and refresh the SPICE import if necessary.

If you're not seeing the "Geographic role" option in the field properties, it could be due to:

• The data type might not be compatible (latitude/longitude should be decimal)
• You might need to update your QuickSight version or permissions
• There might be an issue with how the data is being imported from Athena

For map visualizations, QuickSight offers different types including points maps, filled maps, and the newer layer maps feature that supports custom shape layers using GeoJSON files.

If you continue experiencing issues after assigning geographic roles, you may need to contact AWS Support as there could be an account-specific configuration issue.
Sources
Create custom shape maps in Amazon QuickSight | AWS Business Intelligence Blog