Skip to content

Commit 17f11f1

Browse files
authored
Merge pull request #185094 from pamistel/pamistel_35anchor_limit
updated docs
2 parents d8215b4 + db00aef commit 17f11f1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/spatial-anchors/concepts/coarse-reloc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Coarse relocalization works by tagging anchors with various on-device sensor rea
2323

2424
## When to use coarse relocalization
2525

26-
If you're planning to handle more than 35 spatial anchors in a space larger than a tennis court, you'll probably benefit from coarse relocalization spatial indexing.
26+
If you're planning to handle anchors in a space larger than a tennis court, you'll probably benefit from coarse relocalization spatial indexing.
2727

2828
The fast lookup of anchors enabled by coarse relocalization is designed to simplify the development of applications backed by world-scale collections of, say, millions of geo-distributed anchors. The complexity of spatial indexing is all hidden, so you can focus on your application logic. All the difficult work is done behind the scenes by Azure Spatial Anchors.
2929

0 commit comments

Comments
 (0)