Need to know how to get out of the corn maze from 3 years ago in the Greater Ipswich Area???? Waze can help!
http://i.imgur.com/Pxpi7Cbh.jpg?1
http://i.imgur.com/Pxpi7Cbh.jpg?1
You did hear, of course, about Apple's problems at Anchorage with routing people onto the taxiways?akpolarbee wrote: I'm more concerned with the airport across town where there ARE some roads that tie into the taxiway/runway system.
https://www.waze.com/editor/?zoom=6&lat ... TTTTTTTTTT
Which is one problem I have with the conversation system. It leaves the UR on the map for someone else to close. What we need is the option of just leaving it open to be followed and maybe someone else can fix (for real not just close it) OR an option that lets the original responding editor semi-close it, to remove it from the editor for others but leave it still in the system for him and the original reporting User to talk and figure out the fix. My biggest fear with this system as is, is that we will return to the bad old days of thousands of unresolved UR's sitting on the maps because everybody is afraid to close one that is still pending.shawndoc wrote:Vent: Just had a user close as 'solved' over 150 UR's that I had outstanding comments on in under 45 minutes. Who knows how many more that I didn't have comments on he closed as well...
Notice anything missing? The entire city should look like that section on the right hand side. The desolation continues south through Long Beach.
Until someone gets yelled at for closing a week or two old UR that someone thought the user would eventually get back to them. Or you send a message to the editor and wait until they get around to responding to you to tell you that they think they know the problem they are just waiting on the response from the user to make sure, and so it gets left open for another week. Meanwhile being a busy editor you move on and who knows when it'll get addressed again to be closed.Riamus wrote:With the current Wiki on conversations, you wouldn't just leave it open forever even if it has conversations. If the conversation is dead - nothing within a long time - then unless you can find a solution, you can close it... though I would still suggest talking to the editor having the conversation first just in case they have a reason to keep it open. I don't really see any more of an issue with that than with the old method. Only now, we can easily solve many problems that were unsolvable in the past.
When I started editing in early 2012 I was finding UR's dating back to 2009, city maps were nearly solid UR's. Las Vegas was a sea of UR's when I got CM status and visited there the first time. There were plenty of GPS tracks down the interstate through the city but very few off the freeway within the city. There were so many UR's I had to work zoomed in so they wouldn't bog my system down as it tried to plot them all. But I started just clearing the UR's(making fixes when I could easily see the needed fix), and basic directionality clean-up. Within a few weeks GPS tracks were popping up in the cleaned up areas and local editors started working on it as well. But it was a mess, so much that I think others had tried to work on it before me and just got discouraged. I spent the time, I did the same in my own state and throughout the mountain west.iainhouse wrote:When I first became a CM, we had some URs in out-of-the-way areas that were over a year old.
Re: Jolly editors