Azure spatial anchors - Coarse relocalization quality

Question

Hi!

I'm building an app and I want to utilize Coarse relocation feature to find anchors close to the user. I did some tests, and the system works great if, as a user, I scan the environment and find some unique visuals first.

Unfortunately, the system breaks when I try to find anchors without scanning the surroundings: as a request result I receive anchors very much mislocated, and I don't see a way to position them properly afterward: scanning the area after the anchors were already received doesn't make they update the positions.
I know that it should be used only after the area is scanned, but since I cannot enforce it on the user, I need a way to show the user that he cannot look for the anchors yet. Is there a way to do it?

Additionally, can I set some minimal requirements for area scanning that has to be met before Coarse relocation request returns some data? This way I can prevent the user from using the app in the wrong way.

Bests!

Answer 1

Hi @Karol R , to help you better can you confirm what sensors and platform are you using for Coarse relocalization in your scenario? As well as share with us the ASA SDK calls the app is making for the scenario - starting from creating anchors to querying them? Thanks!

Coarse relocalization | Sensors and platforms