8 releases (4 breaking)

0.4.0 Jun 25, 2022
0.3.1 Oct 20, 2020
0.3.0 Jul 27, 2020
0.2.0 Apr 10, 2020
0.0.1 Jan 20, 2015

#231 in Geospatial

Download history 26/week @ 2023-11-20 34/week @ 2023-11-27 15/week @ 2023-12-04 23/week @ 2023-12-11 24/week @ 2023-12-18 36/week @ 2023-12-25 87/week @ 2024-01-01 75/week @ 2024-01-08 64/week @ 2024-01-15 44/week @ 2024-01-22 88/week @ 2024-01-29 106/week @ 2024-02-05 40/week @ 2024-02-12 70/week @ 2024-02-19 113/week @ 2024-02-26 127/week @ 2024-03-04

368 downloads per month
Used in 2 crates

MIT/Apache

64KB
1K SLoC

geocoding

Rust utilities to enrich addresses, cities, countries, and landmarks with geographic coordinates through third-party geocoding web services. Project is in a very early stage.

API Documentation

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


lib.rs:

This crate provides forward– and reverse-geocoding functionality for Rust. Over time, a variety of providers will be added. Each provider may implement one or both of the Forward and Reverse traits, which provide forward– and reverse-geocoding methods.

Note that for the reverse method, the return type is simply Option<String>, as this is the lowest common denominator reverse-geocoding result. Individual providers may implement additional methods, which return more finely-structured and/or extensive data, and enable more specific query tuning. Coordinate data are specified using the Point struct, which has several convenient From implementations to allow for easy construction using primitive types.

A note on Coordinate Order

While individual providers may specify coordinates in either [Longitude, Latitude] or [Latitude, Longitude] order, Geocoding always requires Point data in [Longitude, Latitude] (x, y) order, and returns data in that order.

Usage of rustls

If you like to use rustls instead of OpenSSL you can enable the rustls-tls feature in your Cargo.toml:

[dependencies]
geocoding = { version = "*", default-features = false, features = ["rustls-tls"] }

Dependencies

~8–23MB
~336K SLoC