diff options
| author | CoprDistGit <infra@openeuler.org> | 2023-05-17 05:17:58 +0000 |
|---|---|---|
| committer | CoprDistGit <infra@openeuler.org> | 2023-05-17 05:17:58 +0000 |
| commit | ec652907662b0cf1c91bba53bf3630863d0cdceb (patch) | |
| tree | 1c075d0fe8d736d4a308145c1f740f96211d6c5b | |
| parent | 7617faf35ec6311507444c33bd8ac70f8290d338 (diff) | |
automatic import of python-aio-geojson-flightairmap
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-aio-geojson-flightairmap.spec | 414 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 416 insertions, 0 deletions
@@ -0,0 +1 @@ +/aio_geojson_flightairmap-0.4.21.tar.gz diff --git a/python-aio-geojson-flightairmap.spec b/python-aio-geojson-flightairmap.spec new file mode 100644 index 0000000..4243191 --- /dev/null +++ b/python-aio-geojson-flightairmap.spec @@ -0,0 +1,414 @@ +%global _empty_manifest_terminate_build 0 +Name: python-aio-geojson-flightairmap +Version: 0.4.21 +Release: 1 +Summary: An async GeoJSON client library for planes using information from a Flight Air Map server. +License: Apache Software License +URL: https://github.com/kuchel77/python-aio-geojson-flightairmap +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/ad/0e/c6597ef2fac10b8a1056a5654cff6683027b0f8c7e11d50d3a58b0d7dcec/aio_geojson_flightairmap-0.4.21.tar.gz +BuildArch: noarch + +Requires: python3-aio-geojson-client +Requires: python3-aiohttp +Requires: python3-pytz + +%description +# python-aio-geojson-flightairmap + +[](https://travis-ci.org/kuchel77/python-aio-geojson-flightairmap) +[](https://coveralls.io/github/exxamalte/python-aio-geojson-flightairmap?branch=master) +[](https://pypi.python.org/pypi/aio-geojson-flightairmap) +[](https://pypi.python.org/pypi/aio-geojson-flightairmap) + +This library provides convenient async access to local [Flight Air Map](https://www.flightairmap.com/) geojson feed. + +This is an adaption of the [NSW RFS Incidents feed](https://github.com/exxamalte/python-aio-geojson-nsw-rfs-incidents) by Malte Franken. + +## Installation +`pip install aio-geojson-flightairmap` + +## Usage +See 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 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 +feed entries specific to the selected feed. + +Status Codes +* _OK_: 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 update + +**Parameters** + +| Parameter | Description | +|--------------------|-------------------------------------------| +| `home_coordinates` | Coordinates (tuple of latitude/longitude) | + +**Supported Filters** + +| Filter | | Description | +|------------|---------------------|-------------| +| Radius | `filter_radius` | Radius in kilometers around the home coordinates in which events from feed are included. | + +**Example** +```python +import asyncio +from aiohttp import ClientSession +from aio_geojson_flightairmap import FlightAirMapFeed +async def main() -> None: + async with ClientSession() as websession: + # Home Coordinates: Latitude: -33.0, Longitude: 150.0 + # Filter radius: 50 km + feed = FlightAirMapFeed(websession, + (-33.0, 150.0), + filter_radius=20000) + + status, entries = await feed.update() + print(status) + print(entries) + for e in entries: + print(e.publication_date) + print(e.coordinates) + print(e.flight_num) +asyncio.get_event_loop().run_until_complete(main()) +``` + +## Feed entry properties +Each feed entry is populated with the following properties: + +| Name | Description | Feed attribute | +|--------------------|-----------------------------------------------------------------------------------------------------|----------------| +| geometry | All geometry details of this entry. | `geometry` | +| coordinates | Best coordinates (latitude, longitude) of this entry. | `geometry` | +| external_id | The unique public identifier for this incident. | `guid` | +| title | Title of this entry. | `title` | +| attribution | Attribution of the feed. | n/a | +| distance_to_home | Distance in km of this entry to the home coordinates. | n/a | +| publication_date | The publication date of the incidents. | `pubDate` | + + +## 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 provides two +different dates: + +* `last_update` will be the timestamp of the last update from the feed + irrespective of whether it was successful or not. +* `last_update_successful` 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` (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. + + + + +%package -n python3-aio-geojson-flightairmap +Summary: An async GeoJSON client library for planes using information from a Flight Air Map server. +Provides: python-aio-geojson-flightairmap +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-aio-geojson-flightairmap +# python-aio-geojson-flightairmap + +[](https://travis-ci.org/kuchel77/python-aio-geojson-flightairmap) +[](https://coveralls.io/github/exxamalte/python-aio-geojson-flightairmap?branch=master) +[](https://pypi.python.org/pypi/aio-geojson-flightairmap) +[](https://pypi.python.org/pypi/aio-geojson-flightairmap) + +This library provides convenient async access to local [Flight Air Map](https://www.flightairmap.com/) geojson feed. + +This is an adaption of the [NSW RFS Incidents feed](https://github.com/exxamalte/python-aio-geojson-nsw-rfs-incidents) by Malte Franken. + +## Installation +`pip install aio-geojson-flightairmap` + +## Usage +See 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 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 +feed entries specific to the selected feed. + +Status Codes +* _OK_: 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 update + +**Parameters** + +| Parameter | Description | +|--------------------|-------------------------------------------| +| `home_coordinates` | Coordinates (tuple of latitude/longitude) | + +**Supported Filters** + +| Filter | | Description | +|------------|---------------------|-------------| +| Radius | `filter_radius` | Radius in kilometers around the home coordinates in which events from feed are included. | + +**Example** +```python +import asyncio +from aiohttp import ClientSession +from aio_geojson_flightairmap import FlightAirMapFeed +async def main() -> None: + async with ClientSession() as websession: + # Home Coordinates: Latitude: -33.0, Longitude: 150.0 + # Filter radius: 50 km + feed = FlightAirMapFeed(websession, + (-33.0, 150.0), + filter_radius=20000) + + status, entries = await feed.update() + print(status) + print(entries) + for e in entries: + print(e.publication_date) + print(e.coordinates) + print(e.flight_num) +asyncio.get_event_loop().run_until_complete(main()) +``` + +## Feed entry properties +Each feed entry is populated with the following properties: + +| Name | Description | Feed attribute | +|--------------------|-----------------------------------------------------------------------------------------------------|----------------| +| geometry | All geometry details of this entry. | `geometry` | +| coordinates | Best coordinates (latitude, longitude) of this entry. | `geometry` | +| external_id | The unique public identifier for this incident. | `guid` | +| title | Title of this entry. | `title` | +| attribution | Attribution of the feed. | n/a | +| distance_to_home | Distance in km of this entry to the home coordinates. | n/a | +| publication_date | The publication date of the incidents. | `pubDate` | + + +## 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 provides two +different dates: + +* `last_update` will be the timestamp of the last update from the feed + irrespective of whether it was successful or not. +* `last_update_successful` 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` (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. + + + + +%package help +Summary: Development documents and examples for aio-geojson-flightairmap +Provides: python3-aio-geojson-flightairmap-doc +%description help +# python-aio-geojson-flightairmap + +[](https://travis-ci.org/kuchel77/python-aio-geojson-flightairmap) +[](https://coveralls.io/github/exxamalte/python-aio-geojson-flightairmap?branch=master) +[](https://pypi.python.org/pypi/aio-geojson-flightairmap) +[](https://pypi.python.org/pypi/aio-geojson-flightairmap) + +This library provides convenient async access to local [Flight Air Map](https://www.flightairmap.com/) geojson feed. + +This is an adaption of the [NSW RFS Incidents feed](https://github.com/exxamalte/python-aio-geojson-nsw-rfs-incidents) by Malte Franken. + +## Installation +`pip install aio-geojson-flightairmap` + +## Usage +See 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 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 +feed entries specific to the selected feed. + +Status Codes +* _OK_: 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 update + +**Parameters** + +| Parameter | Description | +|--------------------|-------------------------------------------| +| `home_coordinates` | Coordinates (tuple of latitude/longitude) | + +**Supported Filters** + +| Filter | | Description | +|------------|---------------------|-------------| +| Radius | `filter_radius` | Radius in kilometers around the home coordinates in which events from feed are included. | + +**Example** +```python +import asyncio +from aiohttp import ClientSession +from aio_geojson_flightairmap import FlightAirMapFeed +async def main() -> None: + async with ClientSession() as websession: + # Home Coordinates: Latitude: -33.0, Longitude: 150.0 + # Filter radius: 50 km + feed = FlightAirMapFeed(websession, + (-33.0, 150.0), + filter_radius=20000) + + status, entries = await feed.update() + print(status) + print(entries) + for e in entries: + print(e.publication_date) + print(e.coordinates) + print(e.flight_num) +asyncio.get_event_loop().run_until_complete(main()) +``` + +## Feed entry properties +Each feed entry is populated with the following properties: + +| Name | Description | Feed attribute | +|--------------------|-----------------------------------------------------------------------------------------------------|----------------| +| geometry | All geometry details of this entry. | `geometry` | +| coordinates | Best coordinates (latitude, longitude) of this entry. | `geometry` | +| external_id | The unique public identifier for this incident. | `guid` | +| title | Title of this entry. | `title` | +| attribution | Attribution of the feed. | n/a | +| distance_to_home | Distance in km of this entry to the home coordinates. | n/a | +| publication_date | The publication date of the incidents. | `pubDate` | + + +## 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 provides two +different dates: + +* `last_update` will be the timestamp of the last update from the feed + irrespective of whether it was successful or not. +* `last_update_successful` 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` (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. + + + + +%prep +%autosetup -n aio-geojson-flightairmap-0.4.21 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-aio-geojson-flightairmap -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Wed May 17 2023 Python_Bot <Python_Bot@openeuler.org> - 0.4.21-1 +- Package Spec generated @@ -0,0 +1 @@ +f09f077ad2850b98fc2d2573d142a427 aio_geojson_flightairmap-0.4.21.tar.gz |