Can you find your address on the Location Address page to see if it was correctly geocoded? You can also check the individual shift record to see if it has the correct location (did you change the location AFTER creating shifts?).

Btw - though it doesn’t matter here - the important address type is “visit”, not “work”.

Yes, both are in the location address:

If I open one, it’s correctly geocoded (here is where I want the starting point for this resource):

However, after generate scheduling and capacity again, if I go to the Dispatch Console and I click view on map the same resource, this is what I see in the DC map:

Thanks!

Can you zoom in? I’m curious if it uses the location in Madrid.

Shouldn’t matter, but can you remove the 2 non-default locations? 

Yes, it uses the location in Madrid (because before I had Spain in my Person Address), the same with the other resource which has London by default (but i changed as well):

I deleted the other two locations:

And i generated again the schedules and capacity but it is still taking the Spain location as starting point: 

Can you find your address on the Location Address page to see if it was correctly geocoded? You can also check the individual shift record to see if it has the correct location (did you change the location AFTER creating shifts?).

Btw - though it doesn’t matter here - the important address type is “visit”, not “work”.

Yes, both are in the location address:

If I open one, it’s correctly geocoded (here is where I want the starting point for this resource):

However, after generate scheduling and capacity again, if I go to the Dispatch Console and I click view on map the same resource, this is what I see in the DC map:

 

Thanks!

Your screenshot with the different map positions and the default position - what entity is this from? It’s not from the Location Addresses page, right?

I was able to reproduce the issue. Can you run this database task…

...and we have filed a ticket for this.

Thank you very much Alexander, i will take it into account! 

It works now :)