Hi,
Inspired by the excellent graphic “all roads lead to Rome” posted elsewhere in this forum, I was experimenting with similar calculations for my own country. It’s my first time out using geographical calculations. Somewhere along the line I typed:
and got the message $Failed[ComputationTimeout]. I tried using SetOptions[WolframAlpha, TimeConstraint -> 120] without success.
My only other thought is that TravelDirections uses Alpha calls, and I am running up against my limit (I have a personal license with 3000 calls per month I think). Is that the case, or is there some other fix?
This is not (I believe) a calculation that involves alpha calls: TravelDirections is a part of the Wolfram Language itself, though it requires cloud access to function.
However, I notice that the first example in the Documentation Center for TravelDirections,
I am experiencing that problem quite regularly, e.g. in the context of AnatomicalStructure. My interpretation is that this timeout were due to my slow internet connection. I then have to try several times before I eventually get all the data. It would be interesting to know if this is the real reason.
"AnatomicalStructure" is an Interpreter type and I imagine that that might have issues under a slow internet connection. However the issue with TravelDirections and so on above is a bug rather than an issue with connection speed. I have been informed by the developers that the issue is resolved and will be fixed in version 10.4 or perhaps via a paclet update. I am not sure that I understand the circumstances where certain issues can be pushed via a paclet update. So, for the time being assume that TravelDirections, TravelDistance, and TravelTime are broken.
the 10.3.1 update! It worked fine in 10.3.0 (the version I used for this post ). OR it could be a problem on Wolfram’s side of course. I already deleted 10.3.0 so I can’t test that one. (Mac OSX btw).
Interesting that there will be a 10.4, not an 11 They always did .1 or .2 updates, so I was already surprised with the .3 update! Well, maybe this is a new kind of updating!
In the end, I don’t care! The major.minor.patch updates are bigger than the major update of Matlab
In the end, the numbers doesn’t really matter of course, the only big difference is a new logo or not
Thanks to everyone for the replies. Three days later I just tried again, without any luck. If it’s a Wolfram-side issue then it’s a persistent one. I haven’t done the 10.3.1 update yet, by the way.I’ll do it today and see what happens.
UPDATE: 10.3.1 now installed and the problem persists.
I’m having this problem too. TravelDirections worked for me two weeks ago. Now it doesn’t. I tried updating to 10.3.1 but issue persists.
I just sent a “feedback” message about the issue to Wolfram and will post any interesting response.
Note my comments earlier. I have discussed the issue with the developers, they are aware of it, and the problem will be fixed in a next release (whatever it is officially named).
Not your problem but…unfortunately for me, Wolfram fixing it “in the next release” is not good enough. I rely on the function in code I just wrote for a charity fundraiser happening next week (my scout troop will collect Christmas trees from 500+ homes in one day).
I’m further frustrated and disappointed because I purchased the last upgrade because of the new geographic information functions. Now I have to write my own TravelDirections function, just as I had to write my own version of FindGeoLocation for street addresses. To be fair, the Mathematica Documentation states only that FindGeoLocation[“address”] “attempts to find the geo location associated with the street address given”
They always did .1 or .2 updates, so I was already surprised with the .3 update! Well, maybe this is a new kind of updating!