Forum Discussion
"Validating" Addresses for map visual
- 2 years ago
Here's my conclusion to close the thread.
Turn out having the entire address in one string is a shaky soloution.
1. I Tried using google and bing map api to validate addresses. Turns out to be a bad soloutiong as the API utilizes the search engine to help find the right address, while the MAP visual in Power BI doesn't no such thing - at least not to the same extent. So the API might say you got a correct address. Leading you to think that no actions needs to be made, but in reality the Power BI map can't place it with a dot.2. The address might be correct, but the maps visualisation will place them incorrectly either ways. I found a thread from 2020 that had a problem of an address being shown correctly in desktop and incorrectly in Power BI Online. Here in 2023 i have the same problem. Correctly formatted address was placed in Norway in the Desktop Version, but was moved to ??France?? when uploaded to Power BI online. Having this type of inconsistency we've decided to go with lon/lat to do our map placements.
Here's my conclusion to close the thread.
Turn out having the entire address in one string is a shaky soloution.
1. I Tried using google and bing map api to validate addresses. Turns out to be a bad soloutiong as the API utilizes the search engine to help find the right address, while the MAP visual in Power BI doesn't no such thing - at least not to the same extent. So the API might say you got a correct address. Leading you to think that no actions needs to be made, but in reality the Power BI map can't place it with a dot.
2. The address might be correct, but the maps visualisation will place them incorrectly either ways. I found a thread from 2020 that had a problem of an address being shown correctly in desktop and incorrectly in Power BI Online. Here in 2023 i have the same problem. Correctly formatted address was placed in Norway in the Desktop Version, but was moved to ??France?? when uploaded to Power BI online. Having this type of inconsistency we've decided to go with lon/lat to do our map placements.