diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-aio-georss-client.spec | 328 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 330 insertions, 0 deletions
@@ -0,0 +1 @@ +/aio_georss_client-0.11.tar.gz diff --git a/python-aio-georss-client.spec b/python-aio-georss-client.spec new file mode 100644 index 0000000..657ff11 --- /dev/null +++ b/python-aio-georss-client.spec @@ -0,0 +1,328 @@ +%global _empty_manifest_terminate_build 0 +Name: python-aio-georss-client +Version: 0.11 +Release: 1 +Summary: An async GeoRSS client library. +License: Apache-2.0 +URL: https://github.com/exxamalte/python-aio-georss-client +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5a/1b/8bcdd36315771b57fec09dba735b0211e18d865a8e60bd2402578fb8bd51/aio_georss_client-0.11.tar.gz +BuildArch: noarch + +Requires: python3-aiohttp +Requires: python3-haversine +Requires: python3-xmltodict +Requires: python3-dateparser + +%description +# python-aio-georss-client + +[](https://github.com/exxamalte/python-aio-georss-client/actions?workflow=CI) +[](https://codecov.io/gh/exxamalte/python-aio-georss-client) +[](https://pypi.python.org/pypi/aio-georss-client) +[](https://pypi.python.org/pypi/aio-georss-client) +[](https://codeclimate.com/github/exxamalte/python-aio-georss-client/maintainability) + +This library provides convenient async access to [GeoRSS](http://www.georss.org/) Feeds. + +## Installation +`pip install aio-georss-client` + +## Known Implementations + +| Library | Source | Topic | +|----------|---------|--------| +| [aio_georss_gdacs](https://github.com/exxamalte/python-aio-georss-gdacs) | Global Disaster Alert and Coordination System (GDACS) | Natural Disasters | + +## Usage +Each implementation extracts relevant information from the GeoJSON feed. Not +all feeds contain the same level of information, or present their information +in different ways. + +After instantiating a particular class 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 + +## Geometry Features +This library supports 3 different types of geometries: +* Point +* Polygon +* Bounding Box + +By default each feed entry is using all available geometries from the external +feed. If required however, you can exclude geometries by overriding +FeedEntry#features and only return the geometries you want to support in your +specific implementation. + + +## 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-georss-client +Summary: An async GeoRSS client library. +Provides: python-aio-georss-client +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-aio-georss-client +# python-aio-georss-client + +[](https://github.com/exxamalte/python-aio-georss-client/actions?workflow=CI) +[](https://codecov.io/gh/exxamalte/python-aio-georss-client) +[](https://pypi.python.org/pypi/aio-georss-client) +[](https://pypi.python.org/pypi/aio-georss-client) +[](https://codeclimate.com/github/exxamalte/python-aio-georss-client/maintainability) + +This library provides convenient async access to [GeoRSS](http://www.georss.org/) Feeds. + +## Installation +`pip install aio-georss-client` + +## Known Implementations + +| Library | Source | Topic | +|----------|---------|--------| +| [aio_georss_gdacs](https://github.com/exxamalte/python-aio-georss-gdacs) | Global Disaster Alert and Coordination System (GDACS) | Natural Disasters | + +## Usage +Each implementation extracts relevant information from the GeoJSON feed. Not +all feeds contain the same level of information, or present their information +in different ways. + +After instantiating a particular class 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 + +## Geometry Features +This library supports 3 different types of geometries: +* Point +* Polygon +* Bounding Box + +By default each feed entry is using all available geometries from the external +feed. If required however, you can exclude geometries by overriding +FeedEntry#features and only return the geometries you want to support in your +specific implementation. + + +## 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-georss-client +Provides: python3-aio-georss-client-doc +%description help +# python-aio-georss-client + +[](https://github.com/exxamalte/python-aio-georss-client/actions?workflow=CI) +[](https://codecov.io/gh/exxamalte/python-aio-georss-client) +[](https://pypi.python.org/pypi/aio-georss-client) +[](https://pypi.python.org/pypi/aio-georss-client) +[](https://codeclimate.com/github/exxamalte/python-aio-georss-client/maintainability) + +This library provides convenient async access to [GeoRSS](http://www.georss.org/) Feeds. + +## Installation +`pip install aio-georss-client` + +## Known Implementations + +| Library | Source | Topic | +|----------|---------|--------| +| [aio_georss_gdacs](https://github.com/exxamalte/python-aio-georss-gdacs) | Global Disaster Alert and Coordination System (GDACS) | Natural Disasters | + +## Usage +Each implementation extracts relevant information from the GeoJSON feed. Not +all feeds contain the same level of information, or present their information +in different ways. + +After instantiating a particular class 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 + +## Geometry Features +This library supports 3 different types of geometries: +* Point +* Polygon +* Bounding Box + +By default each feed entry is using all available geometries from the external +feed. If required however, you can exclude geometries by overriding +FeedEntry#features and only return the geometries you want to support in your +specific implementation. + + +## 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-georss-client-0.11 + +%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-georss-client -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.11-1 +- Package Spec generated @@ -0,0 +1 @@ +96b4b2b36d6a9fcd9347a6b61c1ae6f5 aio_georss_client-0.11.tar.gz |