google_maps 3.9.5

An unofficial Google Maps Platform client library for the Rust programming language.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

//! The **Geolocation API** returns a location and accuracy radius based on
//! information about cell towers and WiFi nodes that the mobile client can
//! detect.
//!
//! # [Introduction](https://developers.google.com/maps/documentation/geolocation/intro#introduction)
//!
//! This document describes the protocol used to send this data to the server
//! and to return a response to the client.
//!
//! ## [Before you begin](https://developers.google.com/maps/documentation/geolocation/intro#before-you-begin)
//!
//! Before you start developing with the Geolocation API, review the
//! [authentication
//! requirements](https://developers.google.com/maps/documentation/geolocation/get-api-key)
//! (you need an API key) and the [API usage and
//! billing](https://developers.google.com/maps/documentation/geolocation/usage-and-billing)
//! information (you need to enable billing on your project).
//!
//! [Frequently asked questions](https://developers.google.com/maps/documentation/geolocation/intro#troubleshooting)
//!
//! * Why am I getting a very large `accuracy` radius in my Geolocation response?
//!
//! If your Geolocation response shows a very high value in the `accuracy`
//! field, the service may be geolocating based on the request IP, instead of
//! WiFi points or cell towers. This can happen if no cell towers or access
//! points are valid or recognized.
//!
//! To confirm that this is the issue, set `considerIp` to `false` in your
//! request. If the response is a `404`, you've confirmed that your
//! `wifiAccessPoints` and `cellTowers` objects could not be geolocated.

pub mod request;
pub mod response;