davipt wrote:CrackedLCD wrote:Well, fiddlesticks. It's giving me the same error no matter what I do.
Have you seen my post? select the segments that gives you errors, click on permalink, and go to waze.com/support, write ghost segments and post the permalink asking waze to remove those broken segments.
AlanOfTheBerg wrote:Mycrophage wrote:Is anyone, in any country knowing how does the Alt. Names works ?
Right now, it is of no use. But, for those who do have streets which go by multiple names, it is nice to have the data be totally correct.
I use it because often, highways or routes overlap. The primary name is used for the name most used, and alt name is where other names or routes are input. In my state of the US, all highways are named, and those usually have a route #, but not always.
Also, the primary name is used for shield creation, but alternate names can hold a local name if the route name is the most popular local name.
AlanOfTheBerg wrote:davipt wrote:So waze please tell me the nickname of the reporter!!!
rleejr79 wrote:skbun wrote:
It would really be nice if the behavior was that primary AND alt names should be scanned for something that generates a shield...
Users browsing this forum: Google Feedfetcher