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

KB47907: Mapping a schema attribute to a geographical role does not populate latitude and longitude data when placed in the Geo Attribute section of a map visualization in MicroStrategy Web


Community Admin

• Strategy


In MicroStrategy Web when placing a Data Import attribute into the Geo Attribute section of a map visualization, latitude and longitude data are automatically populated if the attribute is mapped to a geographical role.

SYMPTOM
In Strategy Web 9.4.x, 10.x, 2019, 2020 and 2021 when placing a Data Import attribute into the Geo Attribute section of a map visualization, latitude and longitude data are automatically populated if the attribute is mapped to a geographical role, like shown below.

ka04W00000148IUQAY_0EM44000000262r.png

However, latitude and longitude data are not populated after mapping a geographical role to a schema attribute via Strategy Developer, like shown below.

ka04W00000148IUQAY_0EM44000000262o.png

Note: Latitude and longitude data is needed in order to display markers for a map visualization.
STEPS TO REPRODUCE
In Strategy Tutorial:

  • Create a LU table in the data warehouse with State names.
  • In Strategy Developer, create an attribute mapped to the LU table.
  • In the attribute editor, select "State" in the Geographical Role section.
ka04W00000148IUQAY_0EM44000000262l.png
  • Update the schema.
  • Create a report using the attribute.
  • Create a Visual Insight dashboard from the report.
  • Select the map visualization.
  • Place the attribute in the Geo Attribute section.
  • Notice that latitude and longitude data are not populated.

 
CAUSE
This is a limitation of Strategy Developer 9.4.x. 10.x, 2019, 2020 and 2021. The geographical role in Strategy Developer does not work the same way as Data Import through Strategy Web. Through Strategy Developer, there is no current process to match the attribute element names to their respective latitude and longitude values.
 
ACTION
This issue was reviewed by our Technology team for feasibility and will not be scoped for a code fix in any upcoming Strategy release.
 
WORKAROUND
As a workaround, collect the latitude and longitude data from an 3rd party resource and add them to the warehouse. Create the respective attribute forms for the latitude and longitude data for the geographical attribute.
Or, use Data Import from Strategy Web, to link the geo attribute to the latitude and longitude data that automatically populates through this method.


Comment

0 comments

Details

Knowledge Article

Published:

April 7, 2017

Last Updated:

October 18, 2017