Display various data (different categories) on a single map + use of slicer

[bloffet]

Dear all,

I'm building a report for the company X, which present on a map the company X workers(based on their home address) and locations of that company X (also based on their address).

The aim is to allow Company X management to quickly identify which worker could replace another one (if he's sick for example) on a given location, based on the proximity of the worker and that location.

For this I use three tables : Locations / Workers / Postcodes-cities. They are linked together by the postcode.

The way I I've built my report is to append my locations and workers tables, and display them on a map.

I use the legend (location or worker) to display the points in a different color (blue and yellow respectively). I then use my postcode-cities as a slicer . This works well, and you can see a sample below.

The question I have is the following though : I'd like not to use a postcode as a slicer, but rather the location.

The idea would be to see on the map which workers lives the closest from that location. On my map, I should then only see one blue point (=the selected location) and the closest workers (=yellow points).

I however does not know how to achieve this on a single map.

Would anyone of you have an idea ?

Thanks already for the help.

Benoît

[v-haibl-msft · Accepted solution]

@bloffet

To show the closet workers, we need to know the distance between each worker and location. To calculate the distance between two points here, we need to know the latitude and longitude of each worker and location. You can refer to this thread for the calculation method. But I don’t think we can achieve the final goal only on a single map. Once we select a location in the slicer, the workers in the map will be filtered out. So we may need two maps, one map will show the selected location and one will show the nearest workers.

There is another thread which use power query to do the similar thing.

Best Regards,

Herbert

[bloffet]

Thank you Herbert for your message.

That's indeed the only solution I'm afraid.

The related post are however very relevant and should help me build a more robust solution.