Ah, sarcasm. Usable when the fact that one's opinion about something is incorrect/incomplete and has been called out on it.
"Lol".
When accounting for hit ball "zones" and their corresponding RF or "Range Factor", a computer program is used.
If you check out the UZR primer posted on fangraphs.com, you'll notice:
For each zone, the computer keeps track of the following on a league-wide (for a particular year) basis:
The number of hits in that zone.
The average run value of a hit in that zone (using traditional lwts hit values).
The number of outs recorded in that zone for each fielding position.
At the same time, the computer keeps track of the total number of fielding errors for each fielding position, but not for each zone individually. Actually it compiles fielding errors in two separate categories: One, ROE errors, are fielding errors that result in an ROE. All other errors, such as on a hit, or a second error on an ROE, are called non-ROE errors.
For example, here is the 2002 league-wide data for zone 56 (the area between the third baseman and the SS):
Zone 56 Hits Outs Run Value per Hit
All Plays 1055 1419 .472
SS 294
3B 1125
For each player at each fielding position (e.g. Rey Sanchez at SS is one entity and Rey Sanchez at 2B is another entity), and for each zone, the computer also compiles the following information:
The number of hits in that zone while the player was on the field at that position.
The number of outs recorded by that player, at that position, in that zone.
ROE and non-ROE fielding errors are compiled separately for each player, but again, not by individual zones.
For example, the 2002 data in zone 56 for Mike Bordick, while playing SS, looks like this:
Zone 56 Hits Outs
Bordick 79 18
The data "a bunch of people taking notes at games" compile, is just used as a comparison for the data that the video-analysis program they use provide, which divides the field into 74 areas (only 68 used for UZR actual purposes).
That's the true "voice of reason". The people that created the statistic and compile the data.