Waze: outsmarting traffic together
https://www.waze.com/forum/
Yeah, them's was the good ol' days!youncs wrote:= 71.2 milesWaze cookie eater feet: 376,076
That's quite a challenge. I doubt, unless disaster strikes you, I'll be able to. I'm too concerned with the little things now. Sure, I will occasionally regrid a small eastern Oregon or Washington town, but the lucrative points-heavy areas are shrinking fast. And, as most anyone in the Top 50 will say, it's just not so much about the points.jasonh300 wrote:Alright Alan, time to catch me again!
I love the text in that ad. Update to 512KB of "user memory"!? What can't I do with that!youncs wrote:AlanOfTheBerg: Munching roads in the 'good ol days'
Or locking North Up.jasonh300 wrote:Guess you've never opened a new thread to inquire about points.youncs wrote:You are always responsive on the forum and possess a generally pleasant disposition.
Probably an phone issue. Insert phone in microwave. Set for 10s on High.daknife wrote:Speaking of which, Alan I seem to be 3 points short of where I estimate I should be. Fix it NOW!!!
I think you left out a few dozen hours and hours....harling wrote:Hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours and hours of dedicated map editing.SKYFLYGUY wrote:I wonder how does some one gets such points from???
And many of these were done on Cartouche, the previous map editor that allowed one edit & one save at a time: Change a segment's geometry, save (pause). Change a segment's name, save (pause). Change the next segment's name, save (pause). Add a new segment, save (pause). Add a junction to connect it to another road, save (pause). For me, those pauses could be up to ten seconds each when the system was working normally, thirty seconds when it was particularly busy, or a couple minutes when something was broken.
So if you wonder where the attention to detail comes from, now you know.
