Be sure to look at the notes here:
You might try one or more of the following:
-Converting the fields to measures (this may automatically make it a Geographic field, and if not, you can try again)
-Ensuring the longitude and latitude fields in the data source include at least one decimal place.
Aside from that, if you can provide an example TWBX where this is occurring, we can probably figure out the cause. You could mock up a small dataset with sample records for this purpose, just use some random Lat/Long values from your actual data.
I cannot convert my lat and long fields to measures as they are coming from SSAS data source. Also, I checked and the fields have decimal values.
I do not know much about SSAS data sources, so I'm not sure if there is some limitation related to this.
If you can post an example TWBX, I'll be happy to take a look -- otherwise, you may want to reach out to firstname.lastname@example.org to see if you're running into some expected behavior.
1 of 1 people found this helpful
I'm not sure if there's some way to specify them as Geographic fields in SSAS, but this KB discusses limitations when working with Cubes:
Also, I found this thread which mentions making a "fact" from the lat/long values:
I'm not sure if that helps or not.
Thank you Matthew, you're awesome!