House Numbers Update Schedule

[orbitc]

Everyone:

Please see below info from Waze regarding the update schedule for house numbers:

[b]The waze engine house numbers index contains all the house numbers you see in the editor’s house numbers layer. Some of the house numbers were added by users and some were imported. The index is updated during the tile build process.

When searching for a specific number, we prioritize the data as follows:

1. If there’s a residential place with that specific number, use the place location.
2. If there’s a waze house number added by a user (not imported), use house number location.
3. Use google location.
4. If there’s no house number location in google’s address, use imported location.[/b]

[MojaveCactusMonkey]

Does this apply to place point and areas with address added by a user taking priority over other sources?

[PesachZ]

@MojaveCactusMonkey

Does this apply to place point and areas with address added by a user taking priority over other sources?

Only residential places. Not public (business) places, even if they have addresses listed.

Sent using Tapatalk for Android 4.4.2

[TheLastTaterTot]

Thanks, Orbit! How does Waze deal with abbreviated and full common road name suffices? E.g., Blvd vs Boulevard. In the past, I’ve seen that Waze tend to favor Google’s search hit when the suffix is fully spelled out.

[tonestertm]

Important Note:

(2) includes imported numbers which have been confirmed (nudged) by an editor.

[bummerdude69]

Just to make sure I’m clear. If we nudge an imported HN (#4), it would then become an added/ edited HN (#2)?

[PesachZ]

@bummerdude69

Just to make sure I’m clear. If we nudge an imported HN (#4), it would then become an added/ edited HN (#2)?

Yes exactly

Sent using Tapatalk for Android 4.4.2

[citeman]

@orbitc

1. If there’s a residential place with that specific number, use the place location.
2. If there’s a waze house number added by a user (not imported), use house number location.

I heard a rumor that Waze was now checking these two databases for duplicates when saving a place and/or house number. Meaning, if there was a confirmed house number and residential place with the same address, Waze would error-out indicating ‘duplicate record’ and not let an editor save the new duplicate record. Anybody know if this is a bad rumor or fact?

Sent from my iPhone using Tapatalk

[PesachZ]

@citeman

@orbitc

1. If there’s a residential place with that specific number, use the place location.
2. If there’s a waze house number added by a user (not imported), use house number location.

I heard a rumor that Waze was now checking these two databases for duplicates when saving a place and/or house number. Meaning, if there was a confirmed house number and residential place with the same address, Waze would error-out indicating ‘duplicate record’ and not let an editor save the new duplicate record. Anybody know if this is a bad rumor or fact?

Sent from my iPhone using Tapatalk

I have seen this error in wme trying to save a residential place. Not sure it applies to place reporting from the app

Sent using Tapatalk for Android 4.4.2

[AlanOfTheBerg]

An UPDATE on House Numbers and searchability:

While the address database index is updated with each tile build, the Search server index is NOT updated daily with tile updates. This is why recently added/moved HNs in Waze are not showing changes/adds to House Numbers when searching in the app when we’d expect.

We are not sure if this is currently working as designed and/or if they are planning to make any kind of update to get the Search server to align daily with the House Number index.

[PesachZ]

@AlanOfTheBerg

An UPDATE on House Numbers and searchability:

While the address database index is updated with each tile build, the Search server index is NOT updated daily with tile updates. This is why recently added/moved HNs in Waze are not showing changes/adds to House Numbers when searching in the app when we’d expect.

We are not sure if this is currently working as designed and/or if they are planning to make any kind of update to get the Search server to align daily with the House Number index.

I was told to report instances where the search index is not updated within 24 hours after the HN is included in a tile build. Meaning if the HN is added at 23:00 UTC (after the tile cutoff) wait till the next tile build (about 33 hours later for this example), then wait an additonal 24 hours after the tiles are updated. If it is still not indexed, report it to HQ so they start to narrow down the source of the issue.

Sent using Tapatalk for Android 4.4.2

[subs5]

So do address get updated the next update or do you have to do one of the items listed on the wiki page about tile updates

Basically do we still need to bump the road to force the HN update on the next tile update or not?

I have received some conflicting information from some editors in PMs so looking for what is really occurring. Thanks, subs5

[citeman]

The last I heard, HN’s still require a bump to trigger the time update, but residential places do not. Remember, it is Waze, I don’t know if any of us editors can say for sure. [emoji6]

Sent from my iPhone using Tapatalk

[orbitc]

According to Waze, the HNs are indexed daily and updated with the next tile update. There maybe delays but it should not be more than 2 tile update cycle. If you experience otherwise please send a sample to me. I’ll be happy to let Waze know.

[PleaseDriveFast]

@PesachZ

@AlanOfTheBerg

An UPDATE on House Numbers and searchability:

While the address database index is updated with each tile build, the Search server index is NOT updated daily with tile updates. This is why recently added/moved HNs in Waze are not showing changes/adds to House Numbers when searching in the app when we’d expect.

We are not sure if this is currently working as designed and/or if they are planning to make any kind of update to get the Search server to align daily with the House Number index.

I was told to report instances where the search index is not updated within 24 hours after the HN is included in a tile build. Meaning if the HN is added at 23:00 UTC (after the tile cutoff) wait till the next tile build (about 33 hours later for this example), then wait an additonal 24 hours after the tiles are updated. If it is still not indexed, report it to HQ so they start to narrow down the source of the issue.

Sent using Tapatalk for Android 4.4.2

Is this related how Waze shows an address in the navigation directions? I have an address that’s been nudged (1 month ago), is shown as a house number in search results, but when you select navigation, the navigation instructions end with “Street Name” with no house number.

[bz2012]

I was told to report this problem here.

Still running across cases where Waze fails to find the correct location for an address despite private place maker, House number markers in the correct location.
https://www.waze.com/editor/?zoom=5&lat=30.405165000000007&lon=-90.146589&layers=2849&mapUpdateRequest=4575330

[bz2012]

Despite repeated attempts to fix this problem, including successfully moving the Google Maps point for the address, Waze continues to INTERMITTENTLY and UNPREDICTABLY return the wrong, old location for the address point (the one Google originally returned).

207 Milton Rd, Maurice, LA
Google maps returns the correct location for the above address line but the wrong location for
207 Milton Rd, Maurice, LA 70555

This strange, repeatable phenomena, may be related to the Waze problem.

https://www.waze.com/editor/?zoom=5&lat=30.102563000000018&lon=-92.122338&layers=928&mapUpdateRequest=4371965

[KC-Guardrail]

Did you clear the old search history? I know that in the app, if the search history isn’t cleared, Waze will continue to send the user back to the original point, regardless of the new point being in place.

[bz2012]

The searches I am trying are in WME, livemap, and Google Maps. Sorry I didn’t make that clear.

Occasionally I search in the App itself, but if I can’t get reliable searches in livemap, my experience says that the App itself will fail also.

[papok]

Hi, from the discussion here I understand that Waze doesn’t interpolate house numbers. In Argentina we where putting house numbers at the start and end of each block thinking (hoping) Waze will find the correct location for each house number. Obviously it never worked as expected.
Does anybody positively know that Waze does not interpolate house numbers (and will never do)?
Should we consider writing a script to automatically add 100 house numbers to each block, 50 on each sidewalk? Although not all the numbers are used, the difference from block to block is 100.

Please share your thoughts.

Papo.