Incorrect place point

Hi,

I know this has been done by another editor for another place location in the recent past. South East Water Ltd in Snodland appears in the right place on the WME with a parking lot road connecting to Rocfort Rd. However when you ask to be routed to it on Livemap (or in the app), the destination is on High Street, to the rear of the offices - which has no access to the site.

Help please - how do I fix this?

Regards,
Ian

If the primary location when searching is determined by the waze place (as opposed to a Google maps poi) then I’ve had success by moving the destination point of the waze place. This worked for me with a tube station

If place updates are working when you try, the update will be immediate in live map and the app, so you can test.

I think your problem is that the PLR connects to the car park but you are not searching for the car park you are searching for a separate place behind the car park.

When you look at it the nearest point on a road to SE Water is the High St to the north, I would suggest either extend the PLR up to the SE Water landmark or move the centre ref point of that landmark so that it closer to the PLR than any other road.

Even better may be to delete the car park landmark (it’s not a public car park), change SE Water landmark to a Point type landmark and move it so that it is closest to the PLR. Need to have a read up on landmarks as I’m not quite up to date.

Andy.

Ah. I should have clicked the link. :slight_smile:

I would suggest deleting the car park, and extending the parking road up to the offices, moving the navigation point of the place down to meet it.

Well guys I’ve made the changes suggested and changed the Area to a Point, only need to wait for waze to update the Livemap to see if the changes have made a difference

Hi,

As an aside to this, wit new residential roads, how long should it take for Waze to be able to find newly added roads/streets?

I have UR Here which mentions a few streets and one at least is not giving a result.

Des. . . :wink:

It should be searchable add soon as it’s included in the Livemap, I assume.

unless this has changed recently, then a road needs to be in google maps to be found in a waze search. google provides waze with the roads-gazeteer and the lat/lng co-ords of that road, waze just presents its map at those co-ords.

It has changed recently. Waze will now use a mix of it’s own data with results from Google.

good good :slight_smile:

Hi,

Not so good if google is way out of date! I thought that one of the key advantages of Waze was that, due to user input and its community (that’s us, guys and gals!), it could be more accurate and up-to-date than its competition (bing, google, tomtom et al).
What’s the point of Waze if it is bolting itself to out-of-date and/or inaccurate information!

Des. . . :wink:

The routing is all based on the maps we draw, so if there’s a new bypass or an altered junction, waze users get the benefit of Waze map editors’ work.

I suppose the argument now is that, if searching for a street name doesn’t result in any hits from the Waze database, we still get the benefits of being able to then fall back on the Google database where the result is more likely to be right than wrong. And in cases where we discover the Google result to be completely wrong, we now have the power to override it by editing the Waze map to add in whatever data was missing to cause the server to fall-back on Google in the first place.