There is no existing standard for this, but the XEP-0060 can be expanded to accomplish this.
In the developed system, I allowed to subscribe to the radius of the + point within the node. This is done using subscription options , for example:
<iq type='set'
from='francisco@denmark.lit/barracks'
to='pubsub.shakespeare.lit'
id='sub1'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<subscribe node='princely_musings' jid='francisco@denmark.lit'/>
<options>
<x xmlns='jabber:x:data' type='submit'>
<field var='FORM_TYPE' type='hidden'>
<value>http://jabber.org/protocol/pubsub#subscribe_options</value>
</field>
<field var='location#latitude'><value>52.231</value></field>
<field var='location#longitude'><value>-1.49</value></field>
<field var='location#radius'><value>10</value></field>
</x>
</options>
</pubsub>
</iq>
Then I set up the pubsub service to filter notifications according to the scope in the subscription options. Things really get complicated when objects move around a location, and you need to emulate a rollback when an item previously published to a client goes beyond its subscription area.
, - , ( ), , , ejabberd. , , , .