You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-video-indexer/matched-person.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,10 +95,10 @@ The following JSON response illustrates what Azure Video Indexer returns when tr
95
95
96
96
It's important to note the limitations of Mapped person, to avoid or mitigate the effects of miss matches between people or people who have no matches.
97
97
98
-
**Precondition** for the matching is that the person that showing in the Observed person was detected and can be found in the People insight.
98
+
**Precondition** for the matching is that the person that showing in the observed faces was detected and can be found in the People insight.
99
99
**Pose**: The tracks are optimized to handle observed people who most often appear on the front.
100
-
**Obstructions**: There may be miss matching between persons and observed people where there are obstruction (people or faces overlapping each other).
101
-
**Spatial allocation per frame**: There may be miss matching where different people appear in the same spatial position relatively to the frame in a short time.
100
+
**Obstructions**: There is no match between faces and observed people where there are obstruction (people or faces overlapping each other).
101
+
**Spatial allocation per frame**: There is no match where different people appear in the same spatial position relatively to the frame in a short time.
102
102
103
103
See the limitations of Observed people: [Trace observed people in a video](observed-people-tracing.md)
0 commit comments