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
34

//! The Roads API **Nearest Roads** service returns individual road segments for
//! a given set of GPS coordinates. This services takes up to 100 GPS points and
//! returns the closest road segment for each point. The points passed do not
//! need to be part of a continuous path.
//!
//! **If you are working with sequential GPS points, use Nearest Roads.**
//!
//! # [Required parameters](https://developers.google.com/maps/documentation/roads/nearest#required-parameters)
//!
//! * `points` - The path to be snapped. The path parameter accepts a list of
//!   latitude/longitude pairs.
//!
//! Note: The snapping algorithm works best for points that are not too far
//! apart. If you observe odd snapping behavior, try creating paths that have
//! points closer together. To ensure the best snap-to-road quality, you should
//! aim to provide paths on which consecutive pairs of points are within 300m of
//! each other. This will also help in handling any isolated, long jumps between
//! consecutive points caused by GPS signal loss, or noise.

pub mod request;
pub mod response;

// -----------------------------------------------------------------------------

pub use crate::roads::nearest_roads::{
    request::Request,
    response::Response
};

#[deprecated(note = "use `crate::roads::nearest_roads::Request` instead", since = "3.8.0")]
pub use crate::roads::nearest_roads::request::Request as NearestRoadsRequest;

#[deprecated(note = "use `crate::roads::nearest_roads::Response` instead", since = "3.8.0")]
pub use crate::roads::nearest_roads::response::Response as NearestRoadsResponse;