pub fn encode_in(
lon: f64,
lat: f64,
step: u8,
lon_range: (f64, f64),
lat_range: (f64, f64),
) -> Option<Hash>Expand description
The same, over ranges the caller picks.
This exists for one caller. A GEOHASH reply is a standard geohash string,
and the standard runs latitude from -90 to 90 where we store it from
-85.05112878, so the reply is the stored point decoded and then encoded again
over the wider range. Everything else uses encode.