Matthew will probably beat me up for saying this, but if this data was held on someone else's site, in plain and reasonably structured view, and there was no API, we'd *scrape it*.
/me runs Tom On 10 August 2010 09:01, Matthew Somerville <[email protected]> wrote: > On Mon, Aug 09, 2010 at 08:08:43PM +0100, Tom Steinberg wrote: > > Best of all, it doesn't involve the need to understand or install our > > codebase. > > You need the site to be able to be given a location and return the > nearest unknown/not fixed problem is. Given the site doesn't currently > do that, that involves adding code to the site. Pretty simple bit of > code, but nevertheless. > > I would suggest it only look for "old, state unknown" reports - > unsurprisingly, people can be quite possessive of their reports, and so > limiting it only to those reports that haven't had any updates for a > while would hopefully prevent any ill feeling that might arise. > > ATB, > Matthew > > > The idea is this: a mobile app that tells people where the nearest > > problem is on FixMyStreet that is of status 'unknown' or 'not fixed', > > helps them navigate there, and then gets them to give an update - > > "fixed" or "still not fixed". > > _______________________________________________ > Mailing list [email protected] > Archive, settings, or unsubscribe: > https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public >
_______________________________________________ Mailing list [email protected] Archive, settings, or unsubscribe: https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
