kkarkid wrote:Personally I like 1 NPA NXX-XXXX over 1-NPA-NXX-XXXX.
What is the requirement for the +, and do we need it? Example +1 NPA NXX-XXXX

The + (plus) symbol is to access the proper long distance circuits if needed, it is ignored if not needed.
http://www.area-codes.org.uk/plus.php

Personally I like 1 NPA NXX-XXXX over 1-NPA-NXX-XXXX.
What is the requirement for the +, and do we need it? Example +1 NPA NXX-XXXX

doctorkb wrote:Two notes:
1. the "plus" sign. It indicates that the next number is the country code. North American phone systems have been lazy -- we use our country code ("1") as the indicator that we're going to dial long distance within the country. You'll see +55 for Brazil, for example -- in North America, you need to dial "011 55 ..." for that number.

That said, if we're including the '1', we MUST include the '+'.

2. for format -- the only time I've seen a hyphen between the country code and the NPA is when it's a toll-free number (1-800-xxx-xxxx). I think this is a throwback to the days of 7-digit (or fewer) dialing.

That said, I'm in favour of: "+1 NPA-Nxx-xxxx" or "+1 (NPA)Nxx-xxxx" -- or, alternatively, the way it should be is we enter "+1NPANxxxxxx" into the editor and Waze displays it appropriately in the client. (I'm sure that's coming soon).

Having previously, years ago, worked for Telus as a telephone operator, I highly agree with this post. My personal favourite is (and this is how I do it in my personal cell phone book) to use +1 (780) 555-1212. The + means if I'm travelling, it will work. Having the 1 means it will always work no matter where in the province I am. The () nicely separates the area code from the rest of the number and just looks professional.

However, for the program's sake, when I'm entering numbers I'm using no spaces, hyphens or brackets. I know from my programming side that it can create a pain since most people don't format the same way as myself. Taking a plain number and formatting is far easier than taking a formatted number, stripping and reformatting.

restless_in_nb wrote:Funny, on a map raid in Texas I was adding 1 to the front of numbers for this exact reason, to ensure mobiles dialed properly (I use 1- for every number in my cell now just to make calling easier).

However, i was told to stop. I guess there is some debate about this but if I have a vote I would vote +1 to adding +1 to numbers

The advantage to NOT having the +1 in the number is that the dialer is usually notified that it is a long distance call being made. Some people might appreciate knowing that the number they're about to dial is long distance.

I fully agree with accuracy and readability. I actually had never seen how it was displayed on the app side, though. I had been entering numbers how I would enter them on a web page form. I had assumed there would be some sort of formatting logic on the app or database side and I was trying not to have the number rejected by said logic.

If the consensus is to format +1-780-555-1212, then great. I can do that. It's just a minor habit I've gotten into from a decade of web programming work.

I just went through all the places I could find between Drayton Valley, AB and Leduc/Nisku, AB. I updated all the phone numbers to +1-NPA-NXX-XXXX and added in a bunch of missing address information. Now, to get a rank 4 to go through and approve a number of apparently locked places that are awaiting moderation...

Caveat: I've never dialed a phone number long distance or otherwise from Waze

I think the best thing would be for Waze to make it as easy as possible for users/editors by applying some kind of template to format/validate whatever phone number is typed in. I thought that was already happening but I guess I was wrong. Most place submissions by Wazers don't have a phone number.

One step further, Waze could possibly even suggest the phone number to submit by doing a Google search which often presents this information since Google already knows about most places anyways.

For myself, if I'm updating a place with an absent telephone number, I usually cut/paste from their website or from the Google search. Most of the time it's like (416) 555-1234. If I have to do more I might spend less time searching and adding numbers.

I can and just did but the task of piecemeal updating all existing places will not get done comprehensively without Waze support. I just think that Waze could help out here but I don't expect this to bubble to the top of feature/todo list anytime soon.

Perhaps an enterprising savvy script writer could make a place telephone number fixer robot.

Funny, on a map raid in Texas I was adding 1 to the front of numbers for this exact reason, to ensure mobiles dialed properly (I use 1- for every number in my cell now just to make calling easier).

However, i was told to stop. I guess there is some debate about this but if I have a vote I would vote +1 to adding +1 to numbers