EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB42355: Google Maps not loading map tiles when data and number formatting preferences are set to non-English language in MicroStrategy Web 9.x


Community Admin

• Strategy


This knowledge base article describes an issue with the Google Maps visualization, where no map tiles are loaded when using non English-US locale settings and explains a possible root cause of this behavior.

SYMPTOM:
 
Non-English users observe an issue with the Google Maps visualization, where no map tiles are loaded while other control elements, such as zoom control are displayed correctly. Only languages with number formatting other than the "." as decimal separator that are set either in Web Preferences or browser as preferred language are affected by this behaviour.
 
The following screenshot shows the Google Maps widget as user with Spanish language preferences. In Web Preferences, Spanish has been selected as Date and Number formatting language.
 
1. Web preferences:
 

ka04W000000OeBlQAK_0EM4400000026rN.png

 
 
2. Maps Widget on document:

ka04W000000OeBlQAK_0EM4400000026rP.png

 
The following screenshot shows the Google Maps widget as user with English language preferences. Web preferences are set to English (US):
 
1. Web preferences:
 

ka04W000000OeBlQAK_0EM4400000026re.png

 
2. Google Maps Widget on document:
 

ka04W000000OeBlQAK_0EM4400000026rg.png

  
CAUSE:
 
This issue only occurs when latitude and longitude values are stored as string / VarChar in the data warehouse and attribute forms are defined as text data type. In that case international date and number formatting is not applied to the latitude and longitude decimal values.
 
When sending the maps request sent to Google, the request includes regional specific parameters. Thus, Google expects the regional specific number formatting for latitude and longitude values. In the above example however, the Spanish user retrieves English formatted latitude values (e.g. 12.56578 instead of 12,56578) directly from the database. Google would expect latitude values with coma as decimal separator and thus fails to display the map.
 
ACTION:
There are two options to solve this issue:

  1. In your data warehouse, change the data type of the latitude and longitude column to a numeric type (e.g. float)
  2. Change the attribute form expression to an ApplySimple that converts the values retrieved into a numeric format.

 
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 13, 2017

Last Updated:

June 13, 2017