% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/models.R
\name{cepis_geo}
\alias{cepis_geo}
\title{The coordinate of a CEP, when the database has one}
\description{
The \code{geo} field of a \link{cepis_address}, a plain list of class \code{cepis_geo}.
The point is the \strong{median} of the coordinates of that CEP's addresses,
not the mean: one badly geocoded address 40 km away shifts a mean and does
not move a median.
}
\section{Fields}{

\describe{
\item{\code{lat}, \code{lon}}{decimal degrees, WGS 84.}
\item{\code{raio_m}}{the radius, in metres, containing 90\% of that CEP's
addresses.}
\item{\code{precisao}}{\code{"logradouro"} or \code{"localidade"} — see below.}
\item{\code{is_precise}}{\code{TRUE} when \code{precisao} is \code{"logradouro"}. Derived,
not sent by the API.}
}
}

\section{Always check precisao before measuring distance}{

There are two kinds of point, and the difference between them is tens of
kilometres:\tabular{lll}{
   \code{precisao} \tab typical \code{raio_m} \tab what the point is \cr
   \code{logradouro} \tab 110-140 m \tab the stretch of street: good for maps and for distance \cr
   \code{localidade} \tab 7-40 km \tab the municipality centroid, because the CEP \emph{is} the whole city \cr
}


\code{raio_m} exists precisely so that error cannot pass unnoticed.
}