Loading Profile...
Can I look up a cluster?
The cluster id http://to.uri.st/cluster/51.606;-3.977 given in the API leads nowhere. I would like to dig into clusters, and even group by category, but I cannot because I don't know what the cluster.
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi enigmatic,
The API provides two objects you can get access to, a list of places within a bounding box (both attractions and clusters) and then attractions themselves.
So given the URL http://to.uri.st/places.xml?lat=51.13... I see that I have a number of attractions and a number of clusters. The clusters are purely URLs of more lists of places but at a narrower zoom level. Following the URL given in a cluster gives me another list of the attractions (and possibly clusters) within that clusters area.
I hope this makes sense.
-
Inappropriate?Unfortunately it isn't working properly:
From the URL you posted, there is this cluster:
cluster url="/places.xml?loc=51.177,-0.854,1" lat="51.177" lng="-0.854" size="2"
However going to http://to.uri.st/places.xml?loc=51.17... doesn't expand the cluster, but instead gives a list of clusters and places nowhere near 51.177,-0.854 Such as:
cluster url="/places.xml?loc=8.299,46.289,2" lat="8.299" lng="46.289" size="24"
cluster url="/places.xml?loc=13.412,99.803,2" lat="13.412" lng="99.803" size="18" -
Inappropriate?You're right, there are two ways of getting a bounding box of places. The first is using a URL like http://to.uri.st/places.xml?lat=51.13... which explicitly defines the box.
The other is with a URL like http://to.uri.st/places.xml?loc=51.17... which defines a center point and a zoom level.
The latter is the way the that the clusters are defined in the XML responses. So the solution is to use the second format from the outset rather than the former but with a suitable zoom level for the data you want (with a zoom level of 1 being the whole world with each increase halving the size of the area).
The index XML file should probably be used to reflect this.
-
Inappropriate?How high of a zoom level would I need to get just the 2 places out of the cluster?
Can you adjust the /places.xml logic to give the appropriate zoom level with the cluster's url? Otherwise it's going to take a lot of guesswork to dig down until I get 24 places out of cluster url="/places.xml?loc=8.299,46.289,2" lat="8.299" lng="46.289" size="24"
I’m confused
EMPLOYEE
