Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I have a dataset with two competing bank branches mapped on latitude and longitude. I want to determine which branches are the furthest from a competitor branch.
So far I have figured out how to calculate the distance between two coordinates. Now I want to create a top 50 list of branches that are furthest away from any other branch.
My mind is fried trying to find a way. Can anyone help?
Solved! Go to Solution.
To be able to do such things in a reasonable time you have to pre-calculate the distances between any pair of branches and store this into a physical table in the model. Best would be to calculate this in Power Query or in an outside source system (like, say, SQL). Depending on the amount of data, it may not be feasible to do it in DAX as a calculated table. Once you have such a table, it's then dead easy to find what you want.
@danialsj
If you can get the long and lat into tables, then you may able to calculate the distance and compare.
Solved: Calculating Distance Between Latitude / Longitude - Microsoft Power BI Community
Use Power Query to Calculate Distance – Girls With Power Tools
Paul Zheng _ Community Support Team
If this post helps, please Accept it as the solution to help the other members find it more quickly.
@danialsj
If you can get the long and lat into tables, then you may able to calculate the distance and compare.
Solved: Calculating Distance Between Latitude / Longitude - Microsoft Power BI Community
Use Power Query to Calculate Distance – Girls With Power Tools
Paul Zheng _ Community Support Team
If this post helps, please Accept it as the solution to help the other members find it more quickly.
To be able to do such things in a reasonable time you have to pre-calculate the distances between any pair of branches and store this into a physical table in the model. Best would be to calculate this in Power Query or in an outside source system (like, say, SQL). Depending on the amount of data, it may not be feasible to do it in DAX as a calculated table. Once you have such a table, it's then dead easy to find what you want.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 49 | |
| 44 | |
| 42 | |
| 19 | |
| 18 |
| User | Count |
|---|---|
| 74 | |
| 71 | |
| 34 | |
| 33 | |
| 31 |