georss-tfs-incidents-client 0.4

A GeoRSS client library for the Tasmania Fire Service Incidents feed.

python-georss-tfs-incidents-client

This library provides convenient access to the Tasmania Fire Service Incidents Feed.

Installation

pip install georss-tfs-incidents-client

Usage

See below for an example of how this library can be used. After instantiating the feed class and supplying the required parameters, you can call update to retrieve the feed data. The return value will be a tuple of a status code and the actual data in the form of a list of specific feed entries.

Status Codes

• UPDATE_OK: Update went fine and data was retrieved. The library may still return empty data, for example because no entries fulfilled the filter criteria.
• UPDATE_OK_NO_DATA: Update went fine but no data was retrieved, for example because the server indicated that there was not update since the last request.
• UPDATE_ERROR: Something went wrong during the update

Supported Filters

Filter		Description
Radius	filter_radius	Radius in kilometers around the home coordinates in which events from the feed are included.
Categories	filter_categories	Array of category names. Only events with a category matching any of these are included.

Example

from georss_tfs_incidents_client import TfsIncidentsFeed
# Home Coordinates: Latitude: -41.5, Longitude: 148.0
# Filter radius: 50 km
feed = TfsIncidentsFeed((-41.5, 148.0), filter_radius=50)
status, entries = feed.update()

Feed Manager

The Feed Manager helps managing feed updates over time, by notifying the consumer of the feed about new feed entries, updates and removed entries compared to the last feed update.

• If the current feed update is the first one, then all feed entries will be reported as new. The feed manager will keep track of all feed entries' external IDs that it has successfully processed.
• If the current feed update is not the first one, then the feed manager will produce three sets:
  • Feed entries that were not in the previous feed update but are in the current feed update will be reported as new.
  • Feed entries that were in the previous feed update and are still in the current feed update will be reported as to be updated.
  • Feed entries that were in the previous feed update but are not in the current feed update will be reported to be removed.
• If the current update fails, then all feed entries processed in the previous feed update will be reported to be removed.

After a successful update from the feed, the feed manager will provide two different dates:

• last_update will be the timestamp of the last successful update from the feed. This date may be useful if the consumer of this library wants to treat intermittent errors from feed updates differently.
• last_timestamp will be the latest timestamp extracted from the feed data. This requires that the underlying feed data actually contains a suitable date. This date may be useful if the consumer of this library wants to process feed entries differently if they haven't actually been updated.