Package: aio-geojson-tas-tfs-incidents
python-aio-geojson-tas-tfs-incidentsThis library is a fork ofpython-aio-geojson-nsw-rfs-incidentsfor convenient async access to theTas Alert Feed.Installationpip install aio-geojson-tas-tfs-incidentsUsageSee below for examples of how this library can be used. After instantiating a
particular class - feed or feed manager - and supply the required parameters,
you can callupdateto 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
feed entries specific to the selected feed.Status CodesOK: Update went fine and data was retrieved. The library may still
return empty data, for example because no entries fulfilled the filter
criteria.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.ERROR: Something went wrong during the updateParametersParameterDescriptionhome_coordinatesCoordinates (tuple of latitude/longitude)Supported FiltersFilterDescriptionRadiusfilter_radiusRadius in kilometers around the home coordinates in which events from feed are included.Categoriesfilter_categoriesArray of category names. Only events with a category matching any of these is included.ExampleimportasynciofromaiohttpimportClientSessionfromaio_geojson_tas_tfs_incidentsimportTasFireServiceIncidentsFeedasyncdefmain()->None:asyncwithClientSession()aswebsession:# Home Coordinates: Latitude: -42.0, Longitude: 147.0# Filter radius: 50 km# Filter categories: 'Advice'feed=TasFireServiceIncidentsFeed(websession,(-42,147.0),filter_radius=50,filter_feedtypes=['warning'],filter_alertlevels=['watch_and_act','advice'])status,entries=awaitfeed.update()print(status)print(entries)asyncio.get_event_loop().run_until_complete(main())Feed entry propertiesEach feed entry is populated with the following properties:NameDescriptionFeed attributegeometriesAll geometry details of this entry.geometriescoordinatesBest coordinates (latitude, longitude) of this entry.geometriesexternal_idThe unique public identifier for this incident.idtitleTitle of this entry.titleattributionAttribution of the feed.n/adistance_to_homeDistance in km of this entry to the home coordinates.n/afeedTypeThe type of messages ('incident', 'warning').feedTypealertLevelThe alert level of the incident ("emergency_warning", "watch_and_act", "advice", "not_applicable"). Only available for feedType 'warning'.categorycreatedThe creation date of the incident.createdchangedThe last changed date of the incident.changedbodyHtmlThe description of the incident including HTML tags.bodyHtmldescriptionThe description of the incident without HTML tags.n/alocationLocation description of the incident.locationstatusStatus of the incident.statustypeType of the incident (e.g. Bush Fire, Grass Fire, Hazard Reduction).type['name']burntAreaBurnt area in ha.burntAreaFeed ManagerThe 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 provides two
different dates:last_updatewill be the timestamp of the last update from the feed
irrespective of whether it was successful or not.last_update_successfulwill 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(optional, depends on the feed data) 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.