At http://www.water-fountains.org/ and any further use of this showcase framework (e.g. [public] toilets for handicapped, childrens playgrounds, park benches, ...) it can be helpful to be able to easily explore the surroundings of the object of interest.
It is not possible to query the Streetview Service semantically for visible items such as a fountain (nor to discover a fountain based on the approximate geographical coordinates), therefore this new property allows for a crowd data gathering of the best streetview URL for the item at hand. Also if more open services than the google service appear, this can also be used for such a service. – The preceding unsigned comment was added by Ralfhauser (talk • contribs) at 06:42, April 27, 2018 (UTC).
"StreetView" is strongly linked to a Google service. The generic term would be "Street-Level Imagery".
> 'streetPanorama360navigatorUrl' is fine too - how would I rename the proposal ?
Must this property link specifically to a 360 panorama navigator on the web, or would a URL to any image-like content be ok?
> I image-like content should rather be handled as image (P18) in Wikimedia
- Support I like the idea of having the opportunity to link from a wikidata POI to a 360° Panorama View. Instead or additional to Street View one could eventually also use Mapillary. Marco Sieber (talk)
- Support This feature would make Wikidata more useful to users looking to find out more about the spatial context of landmarks. Matthew (talk) 07:26, 17 May 2018 (UTC)
- Oppose For the stated use-cases, coordinates suffice. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:52, 20 May 2018 (UTC)
Ralf: Our experience shows that just with coordinates, streetview may point into a direction where the item of interest isn't visible at all