Stephen Pendleton wrote: > I can't seem to get this to work. For example I send: > > <iq to="butler.buddycloud.com" type="get" xml:lang="en" id="location1"> > <locationquery xmlns="urn:xmpp:locationquery:0"> > <timestamp>2009-04-05T08:09:56Z</timestamp> > <publish>true</publish> > <reference> > <id>262:07:51520:34124757</id> > <type>cell</type> > <signalstrength>88</signalstrength> > </reference> > </locationquery> > <locationquery xmlns="urn:xmpp:locationquery:0"> > <timestamp>2009-04-05T08:09:56Z</timestamp> > <reference> > <id>262:07:51520:34104756</id> > <type>cell</type> > <signalstrength>88</signalstrength> > </reference> > </locationquery> > <locationquery xmlns="urn:xmpp:locationquery:0"> > <timestamp>2009-04-05T08:09:56Z</timestamp> > <reference> > <id>262:07:51520:34084753</id> > <type>cell</type> > <signalstrength>88</signalstrength> > </reference> > </locationquery> > </iq> > At the moment our server don't like multiple <locationquery> elements in an <iq>. There is no particularly good reason for this and I will fix it.
> and I get back the placename OK. I then send the nearby places query and get > an error back: > > <iq to="butler.buddycloud.com" type="get" id="nearbyplaces1"> > <command xmlns="http://jabber.org/protocol/commands"; > node="location"> > <x xmlns="jabber:x:data" type="form"> > <field type="hidden" var="FORM_TYPE"> > > <value>buddycloud:location:places_near</value> > </field> > </x> > </command> > </iq> > > and get back: > <iq from="butler.buddycloud.com" to="spendle...@movsoftware.com/spark" > id="nearbyplaces1" type="error" xml:lang="en-GB"> > <command xmlns="http://jabber.org/protocol/commands"; > node="location"> > <x xmlns="jabber:x:data" type="form"> > <field type="hidden" var="FORM_TYPE"> > > <value>buddycloud:location:places_near</value> > </field> > </x> > </command> > <error code="500" type="wait"><internal-server-error > xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text > xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq> > > > Something wrong was probably not right there (!) Possibly to do with the above. > Also, I dont understand the <publish>true</publish> stanza. In the case > where I am sending cellids what is it publishing to my PEP node? Not my > lat/lon right, because you do not have lat/lon mappings from cellids to > lat/long coordinates and I dont have a placename published with that > lat/lon. > It will publish as much info as can be derived from your references. We do have a rudimentary cell to lat/lon database, and if a match is found it wil use this to derive your coordinates. If not it will default to the center of your country (derived from MCC) associated with a huuuuge error. From lat/lon it will try to obtain region, city and area names (with a little help from geonames.org). Note that the publish will most likely fail, since your host server will propably let our server publish to your PEP node on your behalf. Some configuration might be needed for this to work I believe. > Also, if I remove or set the <publish> to <publish>false</publish> I get > back: > > iq from="butler.buddycloud.com" to="spendle...@movsoftware.com/spark" > id="location31" type="result"><geoloc > xmlns="http://jabber.org/protocol/geoloc"; > xml:lang="en"><accuracy>1000000</accuracy></geoloc></iq> > > Not sure what this means. > This is probably related to your error above. Some how no results could be found (even so it suggest an error for your location had it been found. Er... right) > Thanks > Your're welcome _______________________________________________ JDev mailing list Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: jdev-unsubscr...@jabber.org _______________________________________________
