I just tried the same route again and this time it calculated OK. Does this suggest that the problem I was having before was due to load on the server?
And/or the complexity issue I mentioned above.
I have only really tried at peak times. It seems that if I try and get a route a mile or two after my journey begins I have more luck.
Ok, can you try off peak. If that doesn’t work then please PM me the exact start and end postcodes/addresses and I’ll see if there are issues at either end.
As requested by David, I’ve uploaded some further test results obtained in early December… Data was logged between midday on the 7th until early morning on the 10th.
On the 7th and 8th routing results were pretty much OK, as expected for a weekend. On the 9th the usual pattern emerged, with routing failing completely during the morning and evening rush hours. Logging was stopped on the 10th before any rush-hour effects could creep into the data for that day.
Raw data for this test: http://chizzum.com/lmr/test5.zip
[i]Notes on the CSV file layout…
The first 4 columns contain data common to all routes returned in the request:
Columns 1&2 - Date/time of request
Column 3 - Elapsed time (ms) between submitting request and receiving response
Column 4 - 0 if any routes were returned, 1 if no routes were returned
Each returned route then adds 5 columns as follows:
Column 5 - 0 if route reached the exact expected endpoint, 1 if it did not (no matter how close it got)
Columns 6&7 - actual endpoint coordinates
Column 8 - route distance
Column 9 - route time[/i]
A shade over 8 hours into the start of a new logging session, and so far everything is proceeding as usual. Unfortunately. One of these days I’ll check the results and see the routing server hasn’t fallen over at the start of the morning rush hour, but that day isn’t today… Oh well, it’ll all get fixed “soon”, right.
Did any of your test routes have any magical interventions along yellow brick roads?
It’s the same test route as originally requested by Waze. Haven’t cross-referenced the yellow brick segment list against the raw route data yet, will have a look at that when I get a chance…
So I tried numerous off peak routes from E14 to TW14 and vice versa over the Christmas period, and almost 100% of the time I failed to get a route. Repeatedly trying again after a few miles would eventually get a route. Basically I can’t get EVER get a route from door to door, and only ever get any sort of route well after the journey begins. I can PM you the exact postcodes if you still want them.
There is a chance it might be an issue with the origin and destination rather than the standard routing issues, particularly as you can’t get routes off-peak. So yes please, let’s see the postcodes. If for privacy reasons you don’t want to share them in a public forum by all means private message me or one of the other country admins.
TW14 9NR > E14 5AP avoiding Motorways, and vice versa.
Interesting, I couldn’t get any routes before 1930 even when trying a midnight time on livemap. However, I can now get two (1942), admittedly one is via the M4 but the other is via the A40 (and I’ve checked for any errant motorway sections). I can’t see much other than minor errors in the map at the first location. It is on a u-turn enabled cul-de-sac but I’m not aware of that failing navigation when at an origin point.
Do you have any idea where the cut-off point is for you normally on getting a route? IE once you start driving at what point does it start giving you a route?
I’ll pick this up tomorrow unless anyone else wants to chime in this evening.
Going to E14 from TW14 I manage to get a route some where near Osterley Station on the A4. Going to TW14 from E14 I usually get a route just before reaching Northumberland Avenue / Trafalgar Square.
At 8:05 am this morning TW14 -> E14 wouldn’t find a route, but Osterley Park (About 5 miles closer to E14) -> E14 found a route immediately.
Interestingly, TW14 -> Osterley Park found a route right away too - so it would seem that splitting the journey into 2 parts would work fine.
That’s helpful, I’ll do some route tracing this morning to see if I can find an exact point at which the problem switches on and off.
I now have a full weeks-worth of data logged for this test route, and whilst a full summary/data upload will have to wait until I’ve got more free time than I had over breakfast this morning, the TL:DR version is both simple and unsurprising - the routing server performance appears to be no better now than during any of the previous test runs…
Maybe the routing server will be next… 
We can but hope. We’re still none the wiser as to what exactly is the problem. My money is still on some algorithm issue rather than pure server power.
Hi,
When all else fails, throw some more pretty graphics at it, or another processor or two! 
Des. . .
It’ll be an instagram interface so you can post your screenshots of the routing failing …