AlanOfTheBerg wrote:I'm not sure we have enough information to act on this yet. We don't know if house numbers should be added to only one side of a split street. Might there be a reason to add it to both? (can't think of any off-hand).

I assumed this would be a straight forward answer. If you get routed to the street closest to the house that can be driven (vs. the back yard when the house is on a long driveway and there is a street behind it), then we must map only the side of split roads that actually takes you to the driveway of the house in question.

If you put the house numbers only on one side of the split road, then half of the houses will be routed to the wrong side of the street with U-turns being forced leaving you on the wrong side.

AlanOfTheBerg wrote:Also, I'm not sure about the merging thing. If you take both sides and put them together and turned to two-way, do all house numbers remain?

I would expect if you have house numbers on each of the split roads then you need to get all the house numbers back to a single two-way road. I would think this is a monumental task for a long roads with hundreds of houses.

That makes me realize that anyone can delete a single segment with house numbers and when someone tries to add the road segment back, the house numbers are gone? This could be a very big problem for vandalism beyond just losing the street segment itself which is frankly pretty easy to replace.

This would be solved it the house numbers were somehow attached to a location and street name in the database and if a segment gets added to the map with that same name, then the house number automatically gets reattached to that segment to the closest location on that road. It would not be 100%, but would save probably 95% of the work after a major error.

Has anything in the interface or operation of House Numbers change for the recent editor updates? I don't recall off hand, but wanted to see if we need to update anything on our House Numbers article.

I'm not sure that I have read all the posts on this subject, but I'm here because this morning I tried to enter a hyphenated address on Oahu for the first time, and Waze would not take it. It drops the second half of the address whether I include a hyphen or not.

I discovered in 2007 that TomTom devices would not take the hyphenated addresses, and reported it to their customer service. Others had apparently beat me to it, because TomTom was well aware of the situation--and didn't care to fix it. I think it was only 2012 (?) when a version of their software came out that had hyphens on their keyboard. Meanwhile, they did accurately navigate to restaurants and other pre-loaded addresses with hyphens.

Unfortunately, the overwhelming majority of addresses in Hawaii have hyphens.

Stores (at least the responsible ones) advised potential TomTom buyers of the problem. I was in a Best Buy when a military guy consulted a sales person about what would be a good GPS to buy. I overheard the sales person (an honest fellow) cautioning the customer that the TomTom models would not handle any of the addresses near where he lived, or elsewhere on Oahu.

There are highways where the number after the hyphen makes all the difference. There could be a couple of miles, I understand, between one end an the other of a hyphenated street number.

I hope this will be treated with great seriousness. It also affects parts of New Jersey and I'm sure other areas that use a similar scheme.

I am a newbie here, if someone can suggest to me a way to raise the profile of this issue, I'd appreciate it.

Thanks

P.S. Google Maps, as an example, has no trouble with accepting hyphenated addresses.

Question for AoftheB, or anyone with the knowledge:

When I activated the House Numbers interface and checked my own neighborhood, it displays numbers on the houses, all of which are marked "forced." Besides being somewhat in the wrong spot (fixable), the numbers themselves omit the prefix part of the address. There are hyphenated numbering systems on some streets/highways: My house number, for example, is 46-111. But on my house there's only "111.")

I gather hyphenation is an issue, but should these numbers all be corrected to read 46111, etc.? I need to be clear on this before adding new ones or editing these. Thanks.

I don't think it's a problem with the existing import. After testing it out this morning, I saw that typing in my full numbered address, which is how a user would do it, got me to my house, with the hypen typed in and without.

I don't know this, but it would seem that the prefix acts like an area code.

I'm guessing that new addresses don't need to include the prefix, but I'll wait to get more official instruction before adding in any.

I did add in a few new addresses that have no prefixes, in response to URs, and it's SO COOL to be able to correct these things directly yourself!

kentsmith9 wrote:I am not sure the new addresses are being searched yet. Is it possible the address came from one of the other search providers?

That is possible. I know addresses that aren't on WME are still turning up in search, prolly from Bing or Google. I'll wait until the next update, and test again.

That sounds like a plan! Guess I'll wait until the next NA update to try that out. I'll just come back to this thread to report the results.

By the way, I'll be glad when in the next upgrade developers figure out a way to put the stop point somewhere other than right in front. Many destinations have driveways off another street. Until then, there's no real way to improve search results for these places from what the third-party services provide.

AlanOfTheBerg wrote: As noted just a few posts up, the search does not use internal Waze house numbers yet.

Is the delay to provide time to add to the database? The reason I ask is that I wanted to figure out how the system works with Hawaii's weirdly hyphenated house numbers before I start adding in the numbers in the newer subdivisions.

So I've been testing searches for known addresses with the prefix (Bing delivers search results). Without the prefix, as they're entered into WME, seems to deliver similar, though not exactly the same results. I assumed this meant the local database was working. But maybe not.

My guess would be I can start entering in the new house numbers, minus the prefix/hypen, as the imported ones are formatted.

In defense of Larry: The one thread in the house numbers forum on the issue is mine, and it has no responses:

viewtopic.php?f=655&t=53204

We have no guidance/resolution in the Hawaii forum, either.

Perhaps if there were other relevant threads they got lost in the forum reorganization?

I'm merely GUESSING that house numbers be added minus the prefix and hyphen, because the prefix is a reference to district and the city entry for the segment should take care of that. But it would be nice to get some more definitive guidance before adding in many new ones.

AlanOfTheBerg wrote:Searching the forum for "hawaii hypen" or "hawaii dash" or "address hyphen" or "address dash" would likely get you all the information you need to know about the situation without having to post the question again...

Sorry, but I've tried all those search terms, and there's just no definitive answer, only random suppositions and theories from people at my level. There's one proposal from a Champ for a live test that would assume Waze is using its own homegrown database (this was posted just after WME updated with the house numbers). But Waze is NOT yet searching its internal data.

So I realize that it's better to avoid posting the same question, but when there are no answers, there's no other option. I am on the verge of just assuming that because the Waze import includes ONLY the suffix, not the prefix or hyphen, that's the way it should be.