Python Client for Street View Publish API (Alpha)
Street View Publish API: The Street View Publish API allows your application to publish 360 photos to Google Maps, along with image metadata that specifies the position, orientation, and connectivity of each photo. With this API, any app can offer an interface for positioning, connecting, and uploading user-generated Street View images.
Quick Start
In order to use this library, you first need to go through the following steps:
Installation
Install this library in a virtualenv using pip. virtualenv is a tool to create isolated Python environments. The basic problem it addresses is one of dependencies and versions, and indirectly permissions.
With virtualenv, it’s possible to install this library without needing system install permissions, and without clashing with the installed system dependencies.
Mac/Linux
pip install virtualenv
virtualenv <your-env>
source <your-env>/bin/activate
<your-env>/bin/pip install gapic-google-maps-streetview_publish-v1
Windows
pip install virtualenv
virtualenv <your-env>
<your-env>\Scripts\activate
<your-env>\Scripts\pip.exe install gapic-google-maps-streetview_publish-v1
Preview
StreetViewPublishServiceClient
from google.streetview import publish_v1
client = publish_v1.StreetViewPublishServiceClient()
# TODO: Initialize `photo`:
photo = {}
response = client.create_photo(photo)
Next Steps
Read the Client Library Documentation for Street View Publish API API to see other available methods on the client.
Read the Street View Publish API Product documentation to learn more about the product and see How-to Guides.
View this repository’s main README to see the full list of Cloud APIs that we cover.
Metadata
Release files for gapic-google-maps-streetview-publish-v1 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gapic-google-maps-streetview_publish-v1-1.0.1.tar.gz | 32.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gapic_google_maps_streetview_publish_v1-1.0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 68.6 kB
Release files / gapic-google-maps-streetview_publish-v1-1.0.1.tar.gz
| Download URL | gapic-google-maps-streetview_publish-v1-1.0.1.tar.gz |
|---|---|
| Size | 32.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd524a5835ec7335fe8074c180215d35c101fa5c3b710ad35becbde1ec310b16
|
|
BLAKE2b-256 checksum How to use checksums |
f16a418373ca38e08d3dcd1f0993f29f20595260b1c2aa3e480b1e8c8f1f0ddc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.14+
|
Release files / gapic_google_maps_streetview_publish_v1-1.0.1-py2.py3-none-any.whl
| Download URL | gapic_google_maps_streetview_publish_v1-1.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 36.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
16c4682b0ec3d322b1fe85e34647ab5a48b422822b2cf995ae631bdcc42dcf31
|
|
BLAKE2b-256 checksum How to use checksums |
178c0e66dbb297b64fdfaf22a1654c42aa3eed830bab477806002c86e0aeac96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.14+
|
Security for gapic-google-maps-streetview-publish-v1 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.