I've done a bit more investigation on this, which can causes workflow issues with Pano2VR:
Pano2VR lets you select a Google Place for a panorama, but it lets you select a "proper" place, and a linear feature such as roads, trails and town names. The latter causes a problem, and will result in the Google API returning an error to the effect that the place can not be found. Pano2VR returns this message, and stalls the metadata uploaded, you then have to manually acknowledge the error, and click the Project button for each pano that causes the problem.
My workaround is to ensure that I do not select any Google linear features such as roads and town names. But I dot enter a Pano Title (in User Data). These Panos will now upload without error, and will display in the Google Maps "Your Contribution" as "Unknown place", though when you display the Pano full size, the title will appear. Connections also appear.
If you do add Google Map linear feature place names, it would be useful if Pano2VR (a) continued automatically after reporting the "place not found" error (or gave the option). (b) Highlighted which images have a proper place, and which ones have a named linear feature. The tour still uploads OK, the image display, and are connected.