<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/11/2014 11:09 AM, Finn Herzfeld
wrote:<br>
</div>
<blockquote cite="mid:53981CBF.9040601@seattlemesh.net" type="cite">Ahh
yes! I sorta-kinda got it to work. The configuration you specified
was giving errors when I tried to synchronize, so I ended up using
this one:<br>
<br>
<tt>{</tt><tt><br>
</tt><tt> "map": {</tt><tt><br>
</tt><tt> "name": "OwnerName",</tt><tt><br>
</tt><tt> "description": "Details"</tt><tt><br>
</tt><tt> },</tt><tt><br>
</tt><tt> "url": <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="http://meshwith.me/nyc.geo.json">"http://meshwith.me/nyc.geo.json"</a></tt><tt><br>
</tt><tt>}</tt><br>
<br>
</blockquote>
<br>
Great! Sorry for the little mistake, I don't always remember
everything correctly :-)<br>
But you managed to get it right!<br>
<br>
<blockquote cite="mid:53981CBF.9040601@seattlemesh.net" type="cite">
I put the proper GeoJSON up there obviously, and as you saw I
filed a bug with NodeAtlas about their GeoJSON not actually being
GeoJSON. I would like to get some sort of hook system so that they
can tell us when they have a new node and have it either run the
synchronize command, or just have the new node data sent to us.</blockquote>
<br>
You can set up the celery-beat schedule to run the synchronizer
periodically, it will automatically detect changes (added nodes,
changed nodes, deleted nodes) and apply them, more info here:<br>
<a class="moz-txt-link-freetext" href="http://nodeshot.readthedocs.org/en/latest/topics/interoperability.html#required-settings">http://nodeshot.readthedocs.org/en/latest/topics/interoperability.html#required-settings</a><br>
(look for CELERYBEAT_SCHEDULE section)<br>
<br>
Federico<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</body>
</html>