I wasn't sure that my question was read, so I post it in a separate topic.
I used the KML version of the bounding box feature in this site for a long time, until the old API stopped working all of a sudden.
The new KML files doesn't seem to be parsed as XML at all and the results for Atom are not as good as they were been (maybe it's due to the changes made to the searching criteria, which allows only precise coordinates searching and disallows bounding box, although the results for the last one get redirected).
I'll appreciate very much any help that you can provide, as this topic is highly crucial for some project I'm working on.
Thanks in advance,
Help get this topic noticed by sharing it on Twitter, Facebook, or email.
Sorry that I broke the old API you were using :(
Since we moved to Google Appengine we have to do our data requests in a different way, this stops us from doing arbitrary bounding box requests unfortunately.
The KML files should be working fine but I could have made a mistake. Can provide me a specific KML URL that isn't working for you and I'll look into it.
I'm still working on things, so anything you find that isn't working for you or that you find missing from what you need, let me know and I'll see what we can do.
Thanks for the quick response.
An example for KML file that seems to be broken - http://to.uri.st/search.kml?c=52.5,-0.25 .There are no additional information for the attractions, such as: summary, latlng e.t.c. and there are no tags.
I stumbled upon another problem - http://to.uri.st/search.js?c=52.5,-0.25 returns only one attraction, whereas the Atom and the KML versions of the search returning much more.
Hope that will help developing your service further.
The missing lat/lon from the KML was a mistake, and a pretty good one for malking the KML useless ;) This is now fixed. I've also added the tags as an ExtendedData element.
The JS view of the search results returned a single box of items while the other views fetch 9 boxes around the chosen point. This was as the JS view is used to feed the JS powered map. I think this is confusing, so I've changed it so all views consistently return 9 boxes of attractions unless you specify with a querystring parameter that you only want 1.