Open-Harbor/osrm-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Use a sane gps_precision multipler

Browse Source
This commit is contained in:
Patrick Niklaus 2016-01-07 16:30:54 +01:00
parent 88e6558da3
commit 2ce74c05e1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
plugins/match.hpp
View File

@ -51,8 +51,6 @@ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
template <class DataFacadeT> class MapMatchingPlugin : public BasePlugin template <class DataFacadeT> class MapMatchingPlugin : public BasePlugin
{ {
constexpr static const unsigned max_number_of_candidates = 10;
std::shared_ptr<SearchEngine<DataFacadeT>> search_engine_ptr; std::shared_ptr<SearchEngine<DataFacadeT>> search_engine_ptr;
using ClassifierT = BayesClassifier<LaplaceDistribution, LaplaceDistribution, double>; using ClassifierT = BayesClassifier<LaplaceDistribution, LaplaceDistribution, double>;
@ -101,7 +99,9 @@ template <class DataFacadeT> class MapMatchingPlugin : public BasePlugin
{ {
osrm::matching::CandidateLists candidates_lists; osrm::matching::CandidateLists candidates_lists;
double query_radius = 10 * gps_precision; // assuming the gps_precision is the standart-diviation of normal distribution that models
// GPS noise (in this model) this should give us the correct candidate with >0.95
double query_radius = 3 * gps_precision;
double last_distance = double last_distance =
coordinate_calculation::haversine_distance(input_coords[0], input_coords[1]); coordinate_calculation::haversine_distance(input_coords[0], input_coords[1]);