Prepare by mastering two separable skill sets: capturing a seamless 360 panorama (projection, nodal point, nadir, metadata) and publishing it correctly (tour connectivity, orientation, privacy blurring). Work through each stage with deliberate practice scenarios, and treat official program pages as the authority for current administrative requirements.
Why a 360 panorama is not just a very wide photo
A Street View panorama is an equirectangular image designed to be viewed from inside the sphere, so every direction — including straight up and down — carries compositional weight, unlike a flat photo with fixed frame edges.
A normal photograph presents a rectangle; the viewer's eye sits outside the frame. An equirectangular 360 image instead maps the whole sphere onto a grid where the horizon stays straight but vertical lines curve and everything near the top and bottom stretches dramatically. Understanding that projection is the foundation for this exam's technical topics, because stitch errors, tripod shadows, and metadata problems all show up in specific places on that map.
Study the consequences rather than the definition. When you review any 360 image, mentally walk the full circle at eye level, then check the ceiling and floor as separate shots, because a viewer will look there. This changes what counts as a flaw: a crooked horizon, a duplicated person caught mid-step in two frames, or a floating tripod can each ruin an otherwise sharp capture. Build the habit of describing what a defect looks like in the viewer before worrying about how to fix it in software.
Stopping parallax and seam errors at the nodal point
Multi-shot stitching rotates a camera through overlapping frames, and those frames must pivot around the lens's nodal point. Rotate around any other axis and nearby objects slide against the background, tearing the image at every seam.
The nodal point is the optical center of the lens. When the camera rotates around it, foreground and background objects keep their relative positions across overlapping frames, so the stitching software can blend them cleanly. Rotate around the tripod's center post instead — the common mistake — and a nearby door frame or chair shifts sideways between frames. The stitcher then averages the disagreement, producing ghosting, bent lines, or a visible seam exactly where the viewer's eye is likely to rest.
One-shot 360 cameras reduce this problem because their multiple lenses are fixed relative to each other, but they introduce their own stitch lines at fixed angles, usually where two fisheye hemispheres meet. Either way, the study habit is the same: after stitching, scan a complete horizontal band at eye level and deliberately trace straight architectural lines — door frames, tiles, table edges — through every seam. If a line kinks or doubles, note whether it happens near a close foreground object, because that points to parallax rather than exposure or alignment.
The nadir problem: placing the tripod where it can be hidden
The nadir is the point directly below the camera. Because no 360 rig covers that spot perfectly, the photographer must plan placement and patching before shooting, not after.
The zenith (straight up) is usually easy because ceilings are uniform, but the nadir shows the tripod, monopod, your feet, or an obvious patch blob. Good technique treats the nadir as a composition decision: stand beside the rig during exposure, choose floor areas with repetitive texture that patches cleanly, or use a self-timer and step away. A poorly patched nadir is highly visible because the viewer naturally looks down when entering a panorama, which is why it deserves its own line in any review checklist.
Worked scenario: imagine shooting a small cafe with a one-shot 360 camera on a short monopod, placed right next to a glass pastry display for convenience. In the viewer, the camera's fixed stitch line slices straight through the display case, the glass both reflects and shows parallax, and the monopod's reflection appears in the floor patch. The mistake was treating placement as an afterthought. The better decision is to relocate the rig to the open center of the room, two or more meters from glass and chrome, re-shoot, and then patch the nadir from clean tile. Why it matters: seam and reflection defects near eye level and floor level are the defects a reviewer or viewer notices first, and they cannot be fixed convincingly in publishing software.
Metadata: why a good image can still fail to register as a Photo Sphere
Street View recognizes a panorama partly through embedded metadata — XMP Photo Sphere fields, orientation, and location data. A visually perfect file without correct metadata may not display or position as intended.
The XMP Photo Sphere standard describes projection type, field of view, and the initial compass heading of the image center, while EXIF can carry GPS coordinates and timestamps. Publishing tools rely on these fields to know an image is a 360 panorama, to orient its starting view, and to place it geographically. Two visually identical files can behave completely differently on Maps: one snaps into place with the storefront facing the street, the other floats unplaced or starts facing a wall.
The practical study point is distinguishing image defects from data defects, because their fixes live in different places. A torn seam is fixed by re-shooting or re-stitching; a panorama that starts facing the wrong direction is fixed by correcting the heading; a panorama stuck in local storage instead of Maps is often a missing or stripped metadata problem — for example, after an editor re-saves the file and drops the XMP block. When practicing, deliberately break one field at a time in a test file and observe what changes, so you learn to diagnose from the symptom rather than guessing.
Choosing a capture approach: matching the method to the location
There is no single correct capture method. A one-shot 360 camera, a DSLR or mirrorless rig shot around the nodal point, and a phone Photo Sphere each trade speed, control, and stitching risk differently across locations.
The decision that matters for exam-style reasoning is matching method to constraints. A one-shot 360 camera captures instantly and handles moving subjects best, but carries fixed stitch lines and a smaller sensor. A panoramic DSLR rig offers maximum resolution and control over the nodal point, at the cost of setup time, exposure blending across frames, and visible seams whenever people or vehicles move between shots. A phone Photo Sphere is fastest to start with but demands a steady, slow sweep and struggles with movement and low light.
Scenario reasoning example: photographing an empty museum hall, a DSLR rig wins because nothing moves and resolution rewards you. Photographing a busy street corner at midday, the same rig produces ghost crowds and traffic doubling at every seam, while a one-shot camera freezes the scene in one instant. Photographing a quick indoor walk-through for practice, the phone works if you pivot slowly around your body. Being able to justify the trade-off in a paper scenario — speed versus resolution versus motion handling — is a transferable skill, whichever specific equipment you personally own.
| Capture approach | Strengths | Watch-outs | Best-suited situations |
|---|---|---|---|
| One-shot 360 camera | Single instant capture; simple workflow; compact | Fixed lens stitch lines; smaller sensor; needs monopod nadir plan | Busy interiors, streets, any scene with movement |
| DSLR/mirrorless panorama rig | Highest resolution; manual exposure and nodal-point control | Slow setup; ghosting when subjects move between frames; complex stitching | Static scenes: empty rooms, landscapes, architecture |
| Phone Photo Sphere | No extra gear; fast to attempt; built-in guidance | Sweep errors and alignment artifacts; weak in low light; lower resolution | Practice sessions, casual documentation, quick checks |
Publishing decisions: connectivity, orientation, and privacy
Publishing is a separate skill from shooting: panoramas must be correctly oriented, optionally connected into a navigable tour, and screened for privacy — faces and license plates — before becoming publicly visible.
On Maps, a single panorama is a dot; a connected series of panoramas linked through doorways and pathways becomes a walkable tour, shown as a line a viewer can travel. Connectivity is a deliberate editorial act: each panorama should overlap meaningfully with its neighbors so transitions feel natural, and the starting heading of the first panorama should greet the viewer sensibly — usually facing the entrance or the street. Unconnected uploads may still publish, but they deny the viewer the walk-through experience a business or venue usually wants.
Worked scenario: you shot five panoramas inside a small hotel — lobby, corridor, two rooms, breakfast area — and upload them all at once. The mistake: uploading them as five independent public panoramas, all geotagged to the same entrance coordinates, with no connections drawn and no pass over the images for guests' faces. The better decision: before publishing, place each panorama at its true position, connect lobby to corridor to rooms in the order a visitor walks, verify the blue line on the map, set each starting heading, and use the blur tools on every identifiable face and license plate. Why it matters: connectivity and privacy are publishing-stage judgments the camera cannot make for you, and they determine whether the imagery actually functions as a tour.
A practice sequence and self-check rubric you can run this week
Rehearse the full pipeline on a small, repeatable home project: capture a two-room walk-through, publish it privately or to your own contributions, and grade it against a written rubric until your observations are consistent.
The exercise: photograph a two-room virtual walk in your home or workplace — three or four panoramas connected through a doorway. Deliberately produce one imperfect first attempt: rotate handheld around your body instead of around a stable point, or shoot close to a corner. Then improve it and compare. Expected observations from the imperfect attempt include kinked door frames at seams, a cluttered or doubled nadir, and a tour line that jumps unnaturally between rooms; the improved version should show straight lines through seams, a clean patched floor, and smooth blue-line navigation.
Grade each attempt against this rubric, scoring each item 0–2 (absent, partial, solid): straight architectural lines at every seam; nadir free of rig, feet, and patch artifacts; uniform exposure around the sphere; heading and position correct on the map; tour connects logically through the doorway; no identifiable faces or plates left unreviewed. A realistic preparation sequence over a couple of weeks: (1) study projection and the nodal point, (2) shoot and grade the two-room exercise, (3) break and repair metadata on a test file, (4) rehearse the publishing scenario — connect, orient, blur — on paper and then live. Readiness check: you can name the defect type from the symptom alone — seam, nadir, metadata, connectivity, or privacy — and state its fix within the correct stage. Treat a rubric score as a learning milestone, not a prediction of any exam outcome. One short note on administration: current program requirements and any eligibility specifics belong to Google's Street View program pages, which you should consult directly.
- Self-check: trace one straight line (door frame, tile edge) through every horizontal seam before judging a panorama finished.
- Self-check: view the nadir and zenith as dedicated inspection passes, not part of the horizontal sweep.
- Self-check: confirm XMP Photo Sphere metadata and heading survive any editing software you use.
- Self-check: walk your own published tour as a stranger would — does the blue line flow and does each panorama open facing something sensible?
- Self-check: complete a privacy pass for faces and license plates on every panorama before it goes public.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.