file through GitHub. The servers.json file is simply a template view of
servers.yml which can be found at
Does that answer your question?
As for question #2, I agree that status.open311.org should be
using servers.json instead. I'll see if I can coordiante with Ben Sheldon
on that. I don't actually have experience working with that codebase, but
if anybody else is interested in helping to make that update please let me
know or submit a pull request -
On Sat, Sep 3, 2016 at 3:43 PM, Milo van der Linden - Code Fellow Eindhoven
<<email obscured>> wrote:
> Open311 Lists <http://lists.open311.org>
> [image: Photo of Milo van der Linden - Code Fellow Eindhoven]
> *City/Server Status*
> by *Milo van der Linden - Code Fellow Eindhoven*
> in *Open311 Discuss* <http://lists.open311.org/groups/discuss>
> Hello all,
> Since I am writing the open311-android app to be able to target any kind
> of open311 server, I have been through various locations on the web to come
> up with a good overview. I have been working through:
> * http://*wiki.open311.org*/GeoReport_v2/Servers/
> * http://*status.open311.org*/ <http://status.open311.org/>
> * https://*github.com*/codeforamerica/open311status
> * https://*github.com*/codeforamerica/open311_java
> and have forked and rewritten https://*github.com*/
> <https://github.com/codeforamerica/open311_java> to https://*github.com*/
> where I am now maintaining the list
> That is parsed by my java lib and used by the android app.
> I wrote a junit test that will try to parse the discovery file for all the
> endpoints. And this is generating some trouble ;-) as can be seen here:
> I have 2 questions:
> Question1) I would prefer to simply download http://*wiki.open311.org*/
> <http://wiki.open311.org/GeoReport_v2/servers.json> every now and then.
> What is the best way for me to get changes through on that page?
> Question2) status.open311.org uses endpoints.json which is not compatible
> with the servers.json file from the wiki. Wouldn't it be better to replace
> endpoints.json with servers.json and update it every now and then? We might
> even be able to set up github hooks to do that automatically.
> ⮪ Reply <email@example.com?subject=Re%3A%20City/Server%20Status>
> 🖂 New topic <firstname.lastname@example.org> View topic…
> • Switch to a daily digest