Wait a few moments. While the page may look like it's finished loading, its probably trying to download from the Lonely Planet api. Be patient!
Well, one of the current problems with Day Trippin' is the sheer number of requests it makes to the Lonely Planet api. Sometimes (often) we hit their request limit and it rather logically blocks us. We'll fix this soon!
We wrote it in 24 hours! But I can explain some stuff (in the cold hard light of now having a few hours sleep)!
This has a few contributing factors. First, due to limitations in anonymous access to the api we can't always get enough results to make a decent list of interesting places near our random point. Second, we rank results according to 4 categories (in descending priority): the Lonely Planet "Point of Interest" type, A unique reference to a keyword, subsequent references to the keyword and finally the distance from our original point. The POI-type is degraded as more results that match are found on a per type basis to try to make sure you still get a few results that you didn't explicitly ask for as a bit of a surprise and the distance from the original point is a logarithmic function so if a result that you were interested in is a long way away from the others it may not be included.
Please refer to Random Number Generators (our troll also knows about the numbers 6 and 4.......trolls don't count well)
Some of this has the same api problem as with preferences but it is mainly due to the random destination being defined as the crow files, while the google path is generated along roads.
Obviously, similar to the previous question. Whats happened here is the random point we've selected has returned no results, so the code has expanded to try to find something a bit further out. It's found two things about the same distance out, so it's decided you should visit both of them. There is a limit to how far it will expand proportional to your specified distance, but at 150km that could push out to 200km, then you have to drive between them.....
