| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
| |
Add a more helpful error message when a problem fetched over Open311 is
rejected for problems with the date.
|
| |
|
|
|
|
|
|
|
| |
If a body has a `fetch_all_reports` setting in the extra metadata then
all reports are fetched over Open311 and processed regardless of age.
This is useful for bodies where the API endpoint always returns all the
reports as it suppresses the error messages you would otherwise get
about reports with invalid dates.
|
| |
|
|
|
|
|
|
| |
FMS uses the Contact->email field for the Open311 service code,
and the Contact->category field is the user-friendly service name.
The wrong value was being compared previously, resulting in all
fetched problems being assigned to the 'Other' category.
|
| |
|
|
| |
Certain endpoints can be slow, so fetch fewer reports at a time.
|
| |
|
|
| |
Also adds script for fetching the last 24hrs of reports
|
| | |
|
| |
|
|
|
|
|
| |
When pulling reports in over Open311 it's sometimes useful to be able to
accept reports with Easting/Northing rather than latitude/longitude.
This adds an option to GetServiceRequests to convert them as they
come in.
|
|
|
This enables the display of existing reports from the back end on FMS
if the body is configured to do this.
Reports will not be created if they are missing an id, a lat or a long,
if the lat/long is outside the area covered by the body, if there is
already a report with a matching id, or if we can't parse out the
request time.
|
