Panel 1
First visible image
Google Maps
Enter a starting location and target destination, then build the route.
Panel 2
Second visible image
Google Maps
Panel 3
Third visible image
Google Maps
Inset map
Panel 1 location
Google Maps Platform usage and cost reminder
RoadPanel can make Google Maps Platform requests when you search for locations, build a route, move the slider, press Prev or Next, use the maneuver cards, view the inset map, or load a visible Street View image. Google Maps Platform uses pay-as-you-go pricing, and eligible SKUs may include monthly no-cost usage caps. Usage beyond those included amounts can be charged to your Google Cloud billing account. Monitor usage, quotas, and budget alerts in Google Cloud Console before sharing the site publicly.
Start fresh by refreshing the page
Refreshing the page starts a new RoadPanel page session. It clears the active route, selected panel, play timer, route slider position, and the in-memory pano/navigation timeline used by this page. RoadPanel does not save Street View images in localStorage, IndexedDB, service-worker cache, or files. Your browser may still manage its own normal temporary HTTP cache according to browser behavior and Google response headers.
Implementation notes
This app uses a custom 5-item Google Places suggestions dropdown that starts after 1 typed character for the starting location and target destination. It requests Street View Static API imagery only for the panels that are visible on screen. It does not add hidden image tags, service workers, local image storage, or image prefetch links. On every Next action, the old second image becomes Panel 1, the old third image becomes Panel 2, and only the new visible Panel 3 image is requested. On every Prev action, the old first image becomes Panel 2, the old second image becomes Panel 3, and only the new visible Panel 1 image is requested. The route position slider waits until release before changing the panels, so dragging the slider itself does not repeatedly request Street View images.
The total image count shown beside the remaining distance and time is a route-distance estimate only. It is calculated from the Directions route length divided by the visible panel spacing. It does not scan every Street View panorama, does not request hidden images, and should be treated as an approximate limit rather than an exact count.
Each visible image is aimed forward along the active route, while the final destination image keeps the same approach heading as the previous panel. After the first image, the app prefers connected Street View pano links when available, then scores candidates by route progress, heading alignment, and distance from the Directions route. This can reduce wrong-level choices on flyovers, overpasses, tunnels, skyways, and parallel roads, but Google Street View metadata available to this browser app does not provide guaranteed roadway elevation or lane-level matching, so complex roads may still need manual checking. Click any visible panel to enlarge it; this is a CSS layout change only and does not request hidden extra imagery. The image stays uncropped inside its container.