This will use to compare the place based on google place id.
So no need to compare the place string which may not be equal
always.
Ex. Madras not equel to Chennai
from geo_id import GeoIds
geo_ids=GeoIds('India')
geo_ids.get_id_data()
return:
{
"country_id": "ChIJkbeSa_BfYzARphNChaFPjNc",
"country": "India"
}
geo_ids=GeoIds('Adyar')
geo_ids.get_id_data()
return:
{
"locality_id":"ChIJgRbEFe1nUjoRg54kepbOaWU",
"state":"Tamil Nadu",
"city":"Chennai",
"state_id":"ChIJM5YYsYLFADsR8GEzRsx1lFU",
"locality":"Adyar",
"city_id":"ChIJYTN9T-plUjoRM9RjaAunYW4",
"country_id":"ChIJkbeSa_BfYzARphNChaFPjNc",
"country":"India"
}
So no need to compare the place string which may not be equal
always.
Ex. Madras not equel to Chennai
from geo_id import GeoIds
geo_ids=GeoIds('India')
geo_ids.get_id_data()
return:
{
"country_id": "ChIJkbeSa_BfYzARphNChaFPjNc",
"country": "India"
}
geo_ids=GeoIds('Adyar')
geo_ids.get_id_data()
return:
{
"locality_id":"ChIJgRbEFe1nUjoRg54kepbOaWU",
"state":"Tamil Nadu",
"city":"Chennai",
"state_id":"ChIJM5YYsYLFADsR8GEzRsx1lFU",
"locality":"Adyar",
"city_id":"ChIJYTN9T-plUjoRM9RjaAunYW4",
"country_id":"ChIJkbeSa_BfYzARphNChaFPjNc",
"country":"India"
}
Metadata
Release files for google-place-id 0.1.2
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 | |
|---|---|---|---|---|
| google_place_id-0.1.2.tar.gz | 2.9 kB | Without provenance | Details |
Release files / google_place_id-0.1.2.tar.gz
| Download URL | google_place_id-0.1.2.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
960042a72bd3fa38a3878cd4836456fa098ab78d365dfc88b145ccf85f4e7fee
|
|
BLAKE2b-256 checksum How to use checksums |
dffbc1b0d92b549265256a692c73e4db07d99c68c7233f8aede30f189c460701
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for google-place-id 0.1.2
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.