Spatial Entity Resolution between Restaurant Locations and Transportation Destinations in Southeast Asia

Solving this problem can improve precision by removing duplicates, and can enrich detail by (for example) merging a phone Location matters in many businesses and services today, number from one record with the hours of operation particularly for transportation and delivery, scenarios from another, once these records are known to refer in which it is important to find the correct pickup to the same thing. This problem is referred to as entity and drop-off locations very quickly. User experience resolution (see (Talburt, 2011)), and it occurs with can be negatively affected if the location information various datasets, including those representing people, is inaccurate or insufficient. Inaccuracies products, works of literature, etc. can originate from imprecise GPS data, manual error happening in the process of data entry, or the lack of For Grab, one entity resolution problem that arises effective data quality control. Insufficiencies can also for spatial data is the alignment of transportation destinations take many forms, including lack of coverage, and lack and restaurants. Currently Grab maintains of detail -- for example, we may know the latitude two tables separately for transportation and food delivery, and longitude of a restaurant location in a mall, but because each use case requires some specific this might not include information about where passengers features, i.e., food delivery needs information about should be dropped off, or where a delivery the estimated delivery time, cuisine types, and opening courier should park to collect food for delivery. Or hours which are absent in the POI table. However, the location of a business may be known, but not its it is highly likely that some entities from both tables contact details or opening hours.