Hi @Atul Vasudev ,
Thank you for the question. If I understood this correctly, you are wanting the raw point cloud values (x, y, z) somehow via an API to query an existing Azure Spatial Anchor storage account.
If so, that is not is used in the API calls since it is more of an offset in the point cloud that is matched depending on the device once matched via the API. In the API set, the underlying class does not expose an x,y,z value and no value is accessible via a query:
https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.spatialanchors.cloudspatialanchor?view=spatialanchors-dotnet
This shows the location matching design with how the scan works:
https://learn.microsoft.com/en-us/azure/spatial-anchors/how-tos/create-locate-anchors-unity#locate-a-cloud-spatial-anchor
Thanks,
Nathan Manis - MSFT
Here are a couple other threads that may be of interest too in forums:
https://learn.microsoft.com/en-us/answers/questions/673434/comparison-of-points-clouds-in-azure-spatial-ancho.html
https://learn.microsoft.com/en-us/answers/questions/690659/import-data-manually-into-azure-spatial-anchors-to.html