summaryrefslogtreecommitdiff
path: root/python-pygeoif.spec
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-04-11 16:28:06 +0000
committerCoprDistGit <infra@openeuler.org>2023-04-11 16:28:06 +0000
commitccb7ca4e1548cec75a468618492aa5dbae6099e8 (patch)
treec6aa124849cddc4519868f73e2ae8056c8984420 /python-pygeoif.spec
parent0ec3f910f8ffcf2cc778282545e531af6560df6e (diff)
automatic import of python-pygeoif
Diffstat (limited to 'python-pygeoif.spec')
-rw-r--r--python-pygeoif.spec127
1 files changed, 127 insertions, 0 deletions
diff --git a/python-pygeoif.spec b/python-pygeoif.spec
new file mode 100644
index 0000000..e3a1e30
--- /dev/null
+++ b/python-pygeoif.spec
@@ -0,0 +1,127 @@
+%global _empty_manifest_terminate_build 0
+Name: python-pygeoif
+Version: 1.0.0
+Release: 1
+Summary: A basic implementation of the __geo_interface__
+License: LGPL
+URL: https://github.com/cleder/pygeoif/
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/b9/cd/c9474df9ebcc0c5b006b3bba2e93addd41cc6ee40995176a2a4537d419e7/pygeoif-1.0.0.tar.gz
+BuildArch: noarch
+
+Requires: python3-typing-extensions
+
+%description
+PyGeoIf provides a `GeoJSON-like protocol <https://gist.github.com/2217756>`_ for geo-spatial (GIS) vector data.
+Other Python programs and packages that you may have heard of already
+implement this protocol:
+* `ArcPy <https://www.esri.com/about/newsroom/arcuser/geojson/>`_
+* `descartes <https://docs.descarteslabs.com/>`_
+* `PySAL <http://pysal.geodacenter.org/>`_
+* `Shapely <https://github.com/Toblerity/Shapely>`_
+* `pyshp <https://pypi.python.org/pypi/pyshp>`_
+So when you want to write your own geospatial library with support
+for this protocol you may use pygeoif as a starting point and build
+your functionality on top of it
+You may think of pygeoif as a 'shapely ultralight' which lets you
+construct geometries and perform **very** basic operations like
+reading and writing geometries from/to WKT, constructing line strings
+out of points, polygons from linear rings, multi polygons from
+polygons, etc. It was inspired by shapely and implements the
+geometries in a way that when you are familiar with shapely
+you feel right at home with pygeoif.
+It was written to provide clean and python only geometries for fastkml_
+
+%package -n python3-pygeoif
+Summary: A basic implementation of the __geo_interface__
+Provides: python-pygeoif
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-pygeoif
+PyGeoIf provides a `GeoJSON-like protocol <https://gist.github.com/2217756>`_ for geo-spatial (GIS) vector data.
+Other Python programs and packages that you may have heard of already
+implement this protocol:
+* `ArcPy <https://www.esri.com/about/newsroom/arcuser/geojson/>`_
+* `descartes <https://docs.descarteslabs.com/>`_
+* `PySAL <http://pysal.geodacenter.org/>`_
+* `Shapely <https://github.com/Toblerity/Shapely>`_
+* `pyshp <https://pypi.python.org/pypi/pyshp>`_
+So when you want to write your own geospatial library with support
+for this protocol you may use pygeoif as a starting point and build
+your functionality on top of it
+You may think of pygeoif as a 'shapely ultralight' which lets you
+construct geometries and perform **very** basic operations like
+reading and writing geometries from/to WKT, constructing line strings
+out of points, polygons from linear rings, multi polygons from
+polygons, etc. It was inspired by shapely and implements the
+geometries in a way that when you are familiar with shapely
+you feel right at home with pygeoif.
+It was written to provide clean and python only geometries for fastkml_
+
+%package help
+Summary: Development documents and examples for pygeoif
+Provides: python3-pygeoif-doc
+%description help
+PyGeoIf provides a `GeoJSON-like protocol <https://gist.github.com/2217756>`_ for geo-spatial (GIS) vector data.
+Other Python programs and packages that you may have heard of already
+implement this protocol:
+* `ArcPy <https://www.esri.com/about/newsroom/arcuser/geojson/>`_
+* `descartes <https://docs.descarteslabs.com/>`_
+* `PySAL <http://pysal.geodacenter.org/>`_
+* `Shapely <https://github.com/Toblerity/Shapely>`_
+* `pyshp <https://pypi.python.org/pypi/pyshp>`_
+So when you want to write your own geospatial library with support
+for this protocol you may use pygeoif as a starting point and build
+your functionality on top of it
+You may think of pygeoif as a 'shapely ultralight' which lets you
+construct geometries and perform **very** basic operations like
+reading and writing geometries from/to WKT, constructing line strings
+out of points, polygons from linear rings, multi polygons from
+polygons, etc. It was inspired by shapely and implements the
+geometries in a way that when you are familiar with shapely
+you feel right at home with pygeoif.
+It was written to provide clean and python only geometries for fastkml_
+
+%prep
+%autosetup -n pygeoif-1.0.0
+
+%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-pygeoif -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.0-1
+- Package Spec generated