The retirement of dknight212 is taking it’s toll. UR’s are getting raised in London faster than they are being cleared. Perhaps country bumpkins with editing rights in the capital could help out?
Agreed. However, I am noticing that, although I respond to ~20 URs in London each day, I’m getting very few responses from reporters, so I end up closing the majority of them unsolved in 8-10 days time. Are other London editors getting the same level of response or (switching on paranoia mode
) is it just me?
Should we reduce the time allowed for reporters to respond? I find they either respond within 24 hours, delighted that we’re taking the time to elicit more information, or they don’t respond at all.
I could process more URs if I was closing those that had 1 response (mine) but that was more than 2 days ago, and the map would probably look a lot clearer.
In general, I find that replies from reporters are the exception rather than the rule. Sometimes however they are very helpful, so it’s always worth asking. Plus it’s good PR that we respond. Some of the effect of responding may be invisible - possibly some people making raising inappropriate UR’s may be deterred from doing so again when they realise they’re wasting real people’s time.
What I do notice is that a quick response is much more likely to generate a reply. I think we should be trying to respond to UR’s within 24 hours max. I don’t expect a reply to some of the 3-week-old UR’s I’ve been tackling this morning, I can’t remember the details of where I was driving 3 days ago, never mind 3 weeks.
As for reducing the time we allow for a reply before we close the UR, I agree that most responses come quickly, but the odd person may be away and unable to reply quickly. I don’t see that it does any harm to wait since I usually filter UR’s with a recent comment out of my display (using UR overview on WME or Livemap UR layer on livemap
Hi,
I’ll see if I can look at a few for you. But London is not exceptional in getting few replies from requests for info.
I know SE London and bits of North London, should I look at Se and let you guys work the other areas?
Des. . . ![]()
I suspect part of the problem is that people are reluctant to deal with UR’s in areas they don’t know. Which in most of London’s nooks and crannies means that everybody is leaving them for somebody else.
So by all means do any areas that you know first, but don’t stop there.
I have been trying to tackle those around SW to NW London especially those around Heathrow but I’m avoiding those on the motorways. Maybe country CM’s or those that don’t know London could tackle those first. I tend to keep a spreadsheet open to keep track of the date I responded but agree that very few OPs are responding.
Sent from my iPhone using Tapatalk
Many thanks for taking on Heathrow, that’s a particularly difficult area for those who don’t know it - and I’ve been there once this year - by bus :o
I haven’t been on properly for a for a few days, I was doing a daily sweep for new, and no updates in 8 days.
One thing I will add, certainly for London at least, given the numbers we can’t afford to be picky, so if you see a UR with someones name on that can be resolved/closed, close it. Too many to leave lying around. At least feel free with mine. ![]()
i will give as many as I can a go tonight.
Happy to pitch in, but I haven’t driven through central London or round the northern part of the M25 for a while so I’ve lost my editing rights. ![]()
There are a number with David’s name on many now over a month old, I’ve closed a couple that were obvious but generally have left alone. Are we OK to close all these now, they are all the red ones some starting to turn dark red :lol: .
Andy.
There are certainly some challenges, like this UR in Hebrew. :o
To my surprise, cut & paste into Google Translate worked perfectly. ![]()
I’m there a couple of times a month but mainly T5 which is easy, occasionally T1 and I try my best to avoid T4 :shock: .
What I have noticed is many of the UR will be about incorrect postcodes for car parks. My stock answer is if you check Heathrows website they will quote postcodes to get you close to the car parks but you then have to follow the road signs.
The other major problem is people not using a sensible search term and inadvertently selecting a destination that is “airside.” They are then directed to a completely inappropriate destination via a high security entrance! To avoid a whole load of work for us editors the easy way out is to politely point out that when close to the airport drivers need to use a bit of common sense and follow road signs.
Andy.
Hi,
You were right when it was mentioned the aerial imagery is way out of sync with the actual maps. Makes editing things a challenge, something to be raised with our Waze colleagues at this weekend me thinks.
I have closed a few, added comments to some more and will pop back later and look at more.
Des. . . ![]()
Yeah I saw that one, part of me wanted to respond with “que?” and from the translate and street view I wasn’t even sure if it was right or not.
I certainly wasn’t going to respond in hebrew lol. EDIT: I see you did though, now thats customer service.
What I have noticed is many of the UR will be about incorrect postcodes for car parks. My stock answer is if you check Heathrows website they will quote postcodes to get you close to the car parks but you then have to follow the road signs.
The other major problem is people not using a sensible search term and inadvertently selecting a destination that is “airside.” They are then directed to a completely inappropriate destination via a high security entrance!
I’m hoping the substitution of “places” for “landmarks” will help. If we name the places right and Waze picks it’s own places in preference to Google answers, we should be able to direct more people to the right points. I’m playing around in Gatwick, starting by creating a “Gatwick Airport” place which, if selected, should take people to the south terminal passenger drop-off. But I can’t begin to test until we get a livemap update…
Possibly we may even be able to create “point places” for some of the commonest incorrect postcodes :idea:
I’ve closed at least 20 old ones, updated a few new ones and resolved a few new ones too.
I’m playing around in Gatwick, starting by creating a “Gatwick Airport” place which, if selected, should take people to the south terminal passenger drop-off. But I can’t begin to test until we get a livemap update…
But Ian that’s the wrong terminal! On the few occasions I’ve flown from Gatwick it has been from the North Terminal and I’ve been late arriving so wouldn’t want want Waze to mess up at the last minute :lol: .
And the bigger the airport the worse the problem becomes, I was waiting at Heathrow last week for a pre-booked minicab who was stuck in traffic on the M25, he phoned me and asked me to go the the central terminals (T1/3), I thought it would be easy but took 25 minutes by train!
There are so many search combinations; is it airport followed by terminal number or other way around; is it airport followed by airline name, airport followed by some car park name… the list is endless. I wait with interest to see if Waze Places can handle it but I would be very surprised if it picks up many of the searches.
I’m afraid I haven’t been doing my duty in London recently. Work is crazy busy at the moment and likely to be so for another week or so. By the time I get a chance to do any editing, I’m too tired to work well. Plus I’ve been trying to catch up with the hundreds of 30+day old URs around the country.
I’ll try to contribute a bit more in London soon.
I think the answer is - Waze places and sensible users can handle it. ![]()
People who navigate to “the airport” with 5 minutes to spare without paying any attention to what terminal they should be going to, is their own fault.
Yeah fair enough, if you search for gatwick south and get taken to a service road just off the run way round the back of north terminal then thats semi understandable.
Please can someone look at this UR. It looks like a L4 locked round a bout need a rebuild.
Thanks,
David