Meshviewer-Collector

[genofire]

Hello,
why not enhance/fork the old good meshviewer-collector ?
https://github.com/genofire/meshviewer-collector
From:
https://multi.meshviewer.org

Sorry for this disclaimer, i just thing we should merge all the developer-power ...

[T-X]

Would it maybe make sense to have both the meshviewer-collector and gluon census-exporter to collect this data via the FFAPI? With some overwrite / customization options if some community provides invalid or outdated data/links in the FFAPI. I think it would make sense to have the FFAPI as the common, "central" authority for this.

https://api.freifunk.net/
https://github.com/freifunk/directory.api.freifunk.net

[herbetom]

That would be nice but unfortunaly doesn't seem realistic.

If i take a quick look at https://api.freifunk.net/data/ffSummarizedDir.json i see

4x meshviewer.json
36x nodes.json
232x nodelist.json

And maybe some other formats or differently named files.

The prevalence of nodelist.json is quite unfortunate because it doesn't contain any usefull information for us.

[T-X]

@herbetom thanks for the summary! Actually, we at Freifunk Lübeck are one of those only providing a nodelist.json... I wanted to add a meshviewer.json now, but looking a the API spec I'm a bit confused (and maybe that's also why many only provide a nodelist.json?).

For the four ones providing a meshviewer.json all use a different format:

• 1 uses url: ".../meshviewer.json", technicalType: "nodelist", no mapType (iserlohn)
• 1 uses url: ".../meshviewer.json", technicalType: "meshviewer", mapType: "list/status" + url: ".../nodelist.json", technicalType: "nodelist", mapType: "list/status" (fulda)
• 1 uses url: ".../meshviewer.json", technicalType: "meshviewer", mapType: "geographical" (euskirchen)
• 1 uses url: ".../meshviewer.json", technicalType: "nodelist", mapType: "list/status" (buchholz)

I guess the best way would probably be to open a ticket at https://github.com/freifunk/api.freifunk.net/ to ask for some clarification then.

---

I guess we could also check for a technicalType: "hopglass" or technicalType: "meshviewer" where their URL points to the rendered map. And fetch that URL and get the meshviewer.json or nodes.json inside of that. But ideally, the FFAPI would make it easier for us...

@herbetom I think there is also this schema validator, with an automatic mailer: https://www.ib-leier.net/rss/FreifunkApiResult.html. That has at least nudged us to fix our ffapi.json in the past ;-). But yeah, that won't help with every entry, that's why I wrote we would probably still need some overwrite / overlay / customization feature. Maybe that overlay could be its own repository, so that meshviewer could use it, too?