# Mote Park - incorrect routing destination
**URL:** https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394
**Category:** United Kingdom
**Created:** [April 9, 2015, 9:38am UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394 "2015-04-09T09:38:25Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Challenger3802](https://www.waze.com/discuss/u/Challenger3802)
#### Post date: [April 9, 2015, 9:38am UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394/1 "2015-04-09T09:38:25Z")
Hi,
I’ve got problems with Mote Park in Maidstone. Currently Livemap is directing users to [this segment](https://www.waze.com/editor/?env=row&lon=0.53576&lat=51.26572&layers=933&zoom=4&segments=189800005) which is the entrance to the Leisure Centre (not the [Park Entrance](https://www.waze.com/editor/?env=row&lon=0.53576&lat=51.26572&layers=933&zoom=4&segments=251645345) as it should do!)
I’ve edited the place marker to navigate users to the parking area, but my edits have made no difference to the routing on the app or Livemap. Can anyone suggest another trick to force waze to route users to the correct address, off of Mote Avenue?
P.S. It has nothing to do with Google Maps which directs users to the Willington St entrance of the park.
Regards,
Ian
---
### Author:  [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [April 9, 2015, 12:43pm UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394/2 "2015-04-09T12:43:33Z")
I’ve got a similar problem with a park near me - if you select the Waze location result in the app then it’ll navigate you to the car park as expected, whereas if you select the Google location result it’ll try navigating you via the internal road network of Pinewood Studios…
Returning to your example, if I start typing in “Mote Park” as a navigation search within the app, I get a single obvious-looking result in the list, for “Mote Park, Mote Avenue, Maidstone, United Kingdom”. Selecting this as my destination, as most users would reasonably be expected to do when it’s the only result which exactly matches the search term, uses the Google location for the park. As this is closer to the access road for the swimming pool than to any other road segment defined in Waze, that’s where Waze tries to navigate to. Not good.
If however I go back to the search screen in the app, type in “Mote Park” again, but now tap the return key as well, the app now takes me to the “Around You” screen, which this time lists two “Mote Park” entries… The first is for “Mote Park, Mote Avenue, Maidstone, England” and the second is for “Mote Park, Mote Avenue, Maidstone, Kent”. Note the subtle differences in the addresses here, and also between the addresses shown here and back on the main search screen. Selecting the first “England” one again uses the Google location (i.e. this is the same location as the one listed as “United Kingdom” on the main search screen), however selecting the second “Kent” one uses the Waze Place location you’ve edited to be correct.
What’s rather concerning about the “Around You” screen, is that at the bottom there’s the list of tabs to filter the results by search provider. Tapping the Google tab, as expected, removes the correct location and leaves only the incorrect one. However tapping the Waze tab ALSO removes the correct location leaving the Google location still present inamongst a bunch of other results - the top result on this list is now “Mote Park, Saltash”… It’s only on the tab selected by default when entering this screen (the one that looks like a WME PUR marker) where the correct location is provided.
Logically I have two problems with this. Firstly, if a Waze Place location is available then it should always be prioritised over any other results where a combined result list is presented to the user - not only are places the only type of location data we can directly control from within the Waze ecosystem, but we ought to be able to assume that the location point for a Waze place is set up to be the optimum destination point for a Waze route, which isn’t generally true for any of the locations returned from other providers even if we’re able to influence them to any degree.
Secondly, why the hell does the Waze results tab fail to include the Waze Place search result present on the “thing that looks like a PUR” tab, yet continues to include the Google result? The Google tab doesn’t still contain results from other sources, so there’s an expectation that the Waze tab would behave in a similarly consistent manner and filter out other sources too.
Meanwhile over in LiveMap, the problem here seems to be that it isn’t using Waze Places at all in its location search…
---
### Author:  [@Timbones](https://www.waze.com/discuss/u/Timbones)
#### Post date: [April 10, 2015, 12:50pm UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394/3 "2015-04-10T12:50:46Z")
HQ says that the Waze and Google results are supposed to be merged automatically, but this sometimes fails. They say there’s a way to manually link a Waze place to a Google result in the editor, but only HQ can do this. They may provide a mechanism for us to request such fixes in the future.
---
### Author:  [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [April 10, 2015, 10:33pm UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394/4 "2015-04-10T22:33:55Z")
Are HQ using “merge” to describe a process whereby the Google result is replaced by a Waze Place result if the place name/address/etc of both results match up, or are they using it to mean a genuine merging of the data held both by Google and Waze to create a single composite result taking data from both sources? The former I’d be very happy with, the latter less so as it would negate some of the benefits of adding place data ourselves.
---
### Author:  [@Timbones](https://www.waze.com/discuss/u/Timbones)
#### Post date: [April 10, 2015, 11:49pm UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394/5 "2015-04-10T23:49:34Z")
I don’t know. Information on the matter is rather sparse…
---
### Author:  [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [April 11, 2015, 8:18am UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394/6 "2015-04-11T08:18:50Z")
If they aren’t a bit more forthcoming between now and July, perhaps something to add to the meeting agenda then? Looking around the UK maps, it’s fairly obvious that we’re all doing a lot of good work in putting places on the map, yet we’re still being faced with having to deal with URs which wouldn’t exist if the app didn’t remain so focussed on using Google location results.
---
### Author:  [@chinf](https://www.waze.com/discuss/u/chinf)
#### Post date: [August 29, 2015, 4:25pm UTC](https://www.waze.com/discuss/t/mote-park-incorrect-routing-destination/241394/7 "2015-08-29T16:25:32Z")
I’m wondering what the current state of play is with this - was there any news from that meeting, or otherwise?