updates, OWM is back

README.md

@@ -2,6 +2,19 @@ https://hopglass.berlin.freifunk.net
 
 ...runs an instance of HopGlass
 https://github.com/plumpudding/hopglass
-as our primary map.
+that gets its data from the openwifimap backend.
+The OWM data is converted to ffmap/hopglass format using
+a simple converter (found in owm2ffmap/).
+The OWM backend is running on the same server, so owm2ffmap
+just parses its data directory.
+There's old code that could fetch the OWM data from remote as
+well.
 
-The OWM-script (see freifunk-berlin/packages) on the node uploads the data via util.berlin.freifunk.net to store them in a local folder.
+In case you wonder, node info ends up in OWM since the
+OWM script (see freifunk-berlin/packages) on the node
+uploads the data via api.openwifimap.net or
+util.berlin.freifunk.net about every hour.
+
+See
+https://wiki.freifunk.net/Berlin:Server#hopglass.berlin.freifunk.net
+for server details and further links.

www/config.json

@@ -28,6 +28,11 @@
     }
   ],
   "nodeInfos": [
+    {
+      "name" : "OpenWifiMap",
+      "href" : "https://util.berlin.freifunk.net/knoteninfo?knoten={NODE_ID}&typ=owm",
+      "caption" : "{NODE_ID} auf openwifimap.net"
+    },
     {
       "name" : "monitor.berlin.freifunk.net",
       "href" : "https://util.berlin.freifunk.net/knoteninfo?knoten={NODE_ID}&typ=monitor",