[Python-modules-commits] [pygeoif] 01/03: import pygeoif_0.6.orig.tar.gz
Sandro Tosi
morph at moszumanska.debian.org
Sat Dec 26 03:00:04 UTC 2015
This is an automated email from the git hooks/post-receive script.
morph pushed a commit to branch master
in repository pygeoif.
commit 83e59100cdc5d278b2e9e28da4648e701f8d537e
Author: Sandro Tosi <morph at debian.org>
Date: Sat Dec 26 02:24:54 2015 +0000
import pygeoif_0.6.orig.tar.gz
---
MANIFEST.in | 6 +
PKG-INFO | 449 ++++++++++++
README.rst | 364 ++++++++++
docs/CONTRIBUTORS.txt | 7 +
docs/HISTORY.txt | 58 ++
docs/LICENSE.GPL | 504 +++++++++++++
docs/LICENSE.txt | 19 +
pygeoif.egg-info/PKG-INFO | 449 ++++++++++++
pygeoif.egg-info/SOURCES.txt | 16 +
pygeoif.egg-info/dependency_links.txt | 1 +
pygeoif.egg-info/entry_points.txt | 3 +
pygeoif.egg-info/not-zip-safe | 1 +
pygeoif.egg-info/top_level.txt | 1 +
pygeoif/__init__.py | 23 +
pygeoif/geometry.py | 1249 +++++++++++++++++++++++++++++++++
pygeoif/test_main.py | 762 ++++++++++++++++++++
setup.cfg | 5 +
setup.py | 63 ++
18 files changed, 3980 insertions(+)
diff --git a/MANIFEST.in b/MANIFEST.in
new file mode 100644
index 0000000..19a38f6
--- /dev/null
+++ b/MANIFEST.in
@@ -0,0 +1,6 @@
+include *.rst
+recursive-include docs *.txt
+recursive-exclude *.pyc *.pyo
+include docs/LICENSE.GPL
+exclude pygeoif/.*
+
diff --git a/PKG-INFO b/PKG-INFO
new file mode 100644
index 0000000..0143dbb
--- /dev/null
+++ b/PKG-INFO
@@ -0,0 +1,449 @@
+Metadata-Version: 1.1
+Name: pygeoif
+Version: 0.6
+Summary: A basic implementation of the __geo_interface__
+Home-page: https://github.com/cleder/pygeoif/
+Author: Christian Ledermann
+Author-email: christian.ledermann at gmail.com
+License: LGPL
+Description: Introduction
+ ============
+
+ PyGeoIf provides a GeoJSON-like protocol for geo-spatial (GIS) vector data.
+
+ see https://gist.github.com/2217756
+
+ Other Python programs and packages that you may have heard of already
+ implement this protocol:
+
+ * ArcPy http://help.arcgis.com/en/arcgisdesktop/
+ * descartes https://bitbucket.org/sgillies/descartes/
+ * geojson http://pypi.python.org/pypi/geojson/
+ * 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_
+
+ .. _fastkml: http://pypi.python.org/pypi/fastkml/
+
+ PyGeoIf is continually tested with *Travis CI*
+
+ .. image:: https://api.travis-ci.org/cleder/pygeoif.png
+ :target: https://travis-ci.org/cleder/pygeoif
+
+ .. image:: https://coveralls.io/repos/cleder/pygeoif/badge.png?branch=master
+ :target: https://coveralls.io/r/cleder/pygeoif?branch=master
+
+
+
+
+ Example
+ ========
+
+
+ >>> from pygeoif import geometry
+ >>> p = geometry.Point(1,1)
+ >>> p.__geo_interface__
+ {'type': 'Point', 'coordinates': (1.0, 1.0)}
+ >>> print p
+ POINT (1.0 1.0)
+ >>> p1 = geometry.Point(0,0)
+ >>> l = geometry.LineString([p,p1])
+ >>> l.bounds
+ (0.0, 0.0, 1.0, 1.0)
+ >>> dir(l)
+ ['__class__', '__delattr__', '__dict__', '__doc__', '__format__',
+ '__geo_interface__', '__getattribute__', '__hash__', '__init__',
+ '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__',
+ '__setattr__', '__sizeof__', '__str__', '__subclasshook__',
+ '__weakref__', '_coordinates', '_geoms', '_type', 'bounds', 'coords',
+ 'geom_type', 'geoms', 'to_wkt']
+ >>> print l
+ LINESTRING (1.0 1.0, 0.0 0.0)
+
+
+ You find more examples in the
+ `test_main.py <https://github.com/cleder/pygeoif/blob/master/pygeoif/test_main.py>`_
+ file which cover every aspect of pygeoif or in fastkml_.
+
+ Classes
+ ========
+
+ All classes implement the attribute:
+
+ * __geo_interface__: as dicussed above
+
+ All geometry classes implement the attributes:
+
+ * geom_type: Returns a string specifying the Geometry Type of the object
+ * bounds: Returns a (minx, miny, maxx, maxy) tuple (float values) that bounds the object.
+ * wkt: Returns the 'Well Known Text' representation of the object
+
+
+ and the method:
+
+ * to_wkt which also prints the object
+
+ GeoObject
+ ----------
+ Base class for Geometry, Feature, and FeatureCollection
+
+ Geometry
+ --------
+ Base class for geometry objects.
+ Inherits from Geoobject.
+
+
+ Point
+ -----
+ A zero dimensional geometry
+
+ A point has zero length and zero area.
+
+ Attributes
+ ~~~~~~~~~~~
+ x, y, z : float
+ Coordinate values
+
+ Example
+ ~~~~~~~~
+
+ >>> p = Point(1.0, -1.0)
+ >>> print p
+ POINT (1.0000000000000000 -1.0000000000000000)
+ >>> p.y
+ -1.0
+ >>> p.x
+ 1.0
+
+
+
+ LineString
+ -----------
+
+ A one-dimensional figure comprising one or more line segments
+
+ A LineString has non-zero length and zero area. It may approximate a curve
+ and need not be straight. Unlike a LinearRing, a LineString is not closed.
+
+ Attributes
+ ~~~~~~~~~~~
+ geoms : sequence
+ A sequence of Points
+
+
+
+ LinearRing
+ -----------
+
+ A closed one-dimensional geometry comprising one or more line segments
+
+ A LinearRing that crosses itself or touches itself at a single point is
+ invalid and operations on it may fail.
+
+ A Linear Ring is self closing
+
+
+
+ Polygon
+ --------
+
+ A two-dimensional figure bounded by a linear ring
+
+ A polygon has a non-zero area. It may have one or more negative-space
+ "holes" which are also bounded by linear rings. If any rings cross each
+ other, the geometry is invalid and operations on it may fail.
+
+ Attributes
+ ~~~~~~~~~~~
+
+ exterior : LinearRing
+ The ring which bounds the positive space of the polygon.
+ interiors : sequence
+ A sequence of rings which bound all existing holes.
+
+
+ MultiPoint
+ ----------
+ A collection of one or more points
+
+ Attributes
+ ~~~~~~~~~~~
+
+ geoms : sequence
+ A sequence of Points
+
+ MultiLineString
+ ----------------
+ A collection of one or more line strings
+
+ A MultiLineString has non-zero length and zero area.
+
+ Attributes
+ ~~~~~~~~~~~
+
+ geoms : sequence
+ A sequence of LineStrings
+
+ MultiPolygon
+ -------------
+
+ A collection of one or more polygons
+
+ Attributes
+ ~~~~~~~~~~~~~
+ geoms : sequence
+ A sequence of `Polygon` instances
+
+
+ GeometryCollection
+ -------------------
+ A heterogenous collection of geometries (Points, LineStrings, LinearRings
+ and Polygons)
+
+ Attributes
+ ~~~~~~~~~~~
+ geoms : sequence
+ A sequence of geometry instances
+
+ Please note:
+ GEOMETRYCOLLECTION isn't supported by the Shapefile format.
+ And this sub-class isn't generally supported by ordinary GIS sw (viewers and so on).
+ So it's very rarely used in the real GIS professional world.
+
+ Example
+ ~~~~~~~~
+
+ >>> from pygeoif import geometry
+ >>> p = geometry.Point(1.0, -1.0)
+ >>> p2 = geometry.Point(1.0, -1.0)
+ >>> geoms = [p, p2]
+ >>> c = geometry.GeometryCollection(geoms)
+ >>> c.__geo_interface__
+ {'type': 'GeometryCollection', 'geometries': [{'type': 'Point', 'coordinates': (1.0, -1.0)},/
+ {'type': 'Point', 'coordinates': (1.0, -1.0)}]}
+ >>> [geom for geom in geoms]
+ [Point(1.0, -1.0), Point(1.0, -1.0)]
+
+ Feature
+ -------
+ Aggregates a geometry instance with associated user-defined properties.
+
+ Attributes
+ ~~~~~~~~~~~
+ geometry : object
+ A geometry instance
+ properties : dict
+ A dictionary linking field keys with values associated with with geometry instance
+
+ Example
+ ~~~~~~~~
+
+ >>> p = Point(1.0, -1.0)
+ >>> props = {'Name': 'Sample Point', 'Other': 'Other Data'}
+ >>> a = Feature(p, props)
+ >>> a.properties
+ {'Name': 'Sample Point', 'Other': 'Other Data'}
+ >>> a.properties['Name']
+ 'Sample Point'
+
+ FeatureCollection
+ -----------------
+ A heterogenous collection of Features
+
+ Attributes
+ ~~~~~~~~~~~
+ features: sequence
+ A sequence of feature instances
+
+ Example
+ ~~~~~~~~
+
+ >>> from pygeoif import geometry
+ >>> p = geometry.Point(1.0, -1.0)
+ >>> props = {'Name': 'Sample Point', 'Other': 'Other Data'}
+ >>> a = geometry.Feature(p, props)
+ >>> p2 = geometry.Point(1.0, -1.0)
+ >>> props2 = {'Name': 'Sample Point2', 'Other': 'Other Data2'}
+ >>> b = geometry.Feature(p2, props2)
+ >>> features = [a, b]
+ >>> c = geometry.FeatureCollection(features)
+ >>> c.__geo_interface__
+ {'type': 'FeatureCollection', 'features': [{'geometry': {'type': 'Point', 'coordinates': (1.0, -1.0)},/
+ 'type': 'Feature', 'properties': {'Other': 'Other Data', 'Name': 'Sample Point'}},/
+ {'geometry': {'type': 'Point', 'coordinates': (1.0, -1.0)}, 'type': 'Feature',/
+ 'properties': {'Other': 'Other Data2', 'Name': 'Sample Point2'}}]}
+ >>> [feature for feature in c]
+ [<Feature Instance Point geometry 2 properties>, <Feature Instance Point geometry 2 properties>]
+
+ Functions
+ =========
+
+ as_shape
+ --------
+
+ Create a pygeoif feature from an object that provides the __geo_interface__
+
+
+ >>> from shapely.geometry import Point
+ >>> from pygeoif import geometry
+ >>> geometry.as_shape(Point(0,0))
+ <pygeoif.geometry.Point object at 0x...>
+
+
+ from_wkt
+ ---------
+
+ Create a geometry from its WKT representation
+
+
+ >>> p = geometry.from_wkt('POINT (0 1)')
+ >>> print p
+ POINT (0.0 1.0)
+
+
+ signed_area
+ ------------
+
+ Return the signed area enclosed by a ring using the linear time
+ algorithm at http://www.cgafaq.info/wiki/Polygon_Area. A value >= 0
+ indicates a counter-clockwise oriented ring.
+
+ orient
+ -------
+
+ Returns a copy of the polygon with exterior in counter-clockwise and
+ interiors in clockwise orientation for sign=1.0 and the other way round
+ for sign=-1.0
+
+
+ mapping
+ -------
+
+ Returns the __geo_interface__ dictionary
+
+
+ Development
+ ===========
+
+ Installation
+ ------------
+
+ You can install PyGeoIf from pypi using pip::
+
+ pip install pygeoif
+
+ Testing
+ -------
+
+ In order to provide a Travis-CI like testing of the PyGeoIf package during
+ development, you can use tox (``pip install tox``) to evaluate the tests on
+ all supported Python interpreters which you have installed on your system.
+
+ You can run the tests with ``tox --skip-missin-interpreters`` and are looking
+ for output similar to the following::
+
+ ______________________________________________________ summary ______________________________________________________
+ SKIPPED: py26: InterpreterNotFound: python2.6
+ py27: commands succeeded
+ SKIPPED: py32: InterpreterNotFound: python3.2
+ SKIPPED: py33: InterpreterNotFound: python3.3
+ py34: commands succeeded
+ SKIPPED: pypy: InterpreterNotFound: pypy
+ SKIPPED: pypy3: InterpreterNotFound: pypy3
+ congratulations :)
+
+ You are primarily looking for the ``congratulations :)`` line at the bottom,
+ signifying that the code is working as expected on all configurations
+ available.
+
+ Changelog
+ =========
+
+ 0.6 (2015/08/04)
+ -----------------
+
+ - Add id to feature [jzmiller1]
+
+ 0.5 (2015/07/13)
+ -----------------
+
+ - Add __iter__ method to FeatureCollection and GeometryCollection [jzmiller1].
+ - add pypy and pypy3 and python 3.4 to travis.
+ - Add tox configuration for performing local testing [Ian Lee].
+ - Add Travis continuous deployment.
+
+ 0.4 (2013/10/25)
+ -----------------
+
+ - after a year in production promote it to `Development Status :: 5 - Production/Stable`
+ - MultiPolygons return tuples as the __geo_interface__
+
+ 0.3.1 (2012/11/15)
+ ------------------
+
+ - specify minor python versions tested with Travis CI
+ - fix for signed area
+
+
+ 0.3 (2012/11/14)
+ -------------------
+
+ - add GeometryCollection
+ - len(Multi*) and len(GeometryCollection) returns the number of contained Geometries
+ - add orient function to get clockwise or counterclockwise oriented poygons
+ - add signed_area function
+ - add _set_orientation method to lineStrings, Polygons and MultiPolygons
+
+
+ 0.2.1 (2012/08/02)
+ -------------------
+
+ - as_shape also accepts an object that is neither a dictionary nor has a __geo_interface__ but can be converted into a __geo_interface__ compliant dictionary
+
+
+ 0.2 (2012/08/01)
+ -----------------
+
+ - change license to LGPL
+ - add wkt as a property
+ - as_shape also accepts a __geo_interface__ compliant dictionary
+ - test with python3
+
+
+ 0.1 (2012/07/27)
+ -----------------
+
+ - initial release
+
+Keywords: GIS Spatial WKT
+Platform: UNKNOWN
+Classifier: Topic :: Scientific/Engineering :: GIS
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 2
+Classifier: Programming Language :: Python :: 2.6
+Classifier: Programming Language :: Python :: 2.7
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.2
+Classifier: Programming Language :: Python :: 3.3
+Classifier: Programming Language :: Python :: 3.4
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL)
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Operating System :: OS Independent
diff --git a/README.rst b/README.rst
new file mode 100644
index 0000000..f04413f
--- /dev/null
+++ b/README.rst
@@ -0,0 +1,364 @@
+Introduction
+============
+
+PyGeoIf provides a GeoJSON-like protocol for geo-spatial (GIS) vector data.
+
+see https://gist.github.com/2217756
+
+Other Python programs and packages that you may have heard of already
+implement this protocol:
+
+* ArcPy http://help.arcgis.com/en/arcgisdesktop/
+* descartes https://bitbucket.org/sgillies/descartes/
+* geojson http://pypi.python.org/pypi/geojson/
+* 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_
+
+.. _fastkml: http://pypi.python.org/pypi/fastkml/
+
+PyGeoIf is continually tested with *Travis CI*
+
+.. image:: https://api.travis-ci.org/cleder/pygeoif.png
+ :target: https://travis-ci.org/cleder/pygeoif
+
+.. image:: https://coveralls.io/repos/cleder/pygeoif/badge.png?branch=master
+ :target: https://coveralls.io/r/cleder/pygeoif?branch=master
+
+
+
+
+Example
+========
+
+
+ >>> from pygeoif import geometry
+ >>> p = geometry.Point(1,1)
+ >>> p.__geo_interface__
+ {'type': 'Point', 'coordinates': (1.0, 1.0)}
+ >>> print p
+ POINT (1.0 1.0)
+ >>> p1 = geometry.Point(0,0)
+ >>> l = geometry.LineString([p,p1])
+ >>> l.bounds
+ (0.0, 0.0, 1.0, 1.0)
+ >>> dir(l)
+ ['__class__', '__delattr__', '__dict__', '__doc__', '__format__',
+ '__geo_interface__', '__getattribute__', '__hash__', '__init__',
+ '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__',
+ '__setattr__', '__sizeof__', '__str__', '__subclasshook__',
+ '__weakref__', '_coordinates', '_geoms', '_type', 'bounds', 'coords',
+ 'geom_type', 'geoms', 'to_wkt']
+ >>> print l
+ LINESTRING (1.0 1.0, 0.0 0.0)
+
+
+You find more examples in the
+`test_main.py <https://github.com/cleder/pygeoif/blob/master/pygeoif/test_main.py>`_
+file which cover every aspect of pygeoif or in fastkml_.
+
+Classes
+========
+
+All classes implement the attribute:
+
+* __geo_interface__: as dicussed above
+
+All geometry classes implement the attributes:
+
+* geom_type: Returns a string specifying the Geometry Type of the object
+* bounds: Returns a (minx, miny, maxx, maxy) tuple (float values) that bounds the object.
+* wkt: Returns the 'Well Known Text' representation of the object
+
+
+and the method:
+
+* to_wkt which also prints the object
+
+GeoObject
+----------
+Base class for Geometry, Feature, and FeatureCollection
+
+Geometry
+--------
+Base class for geometry objects.
+Inherits from Geoobject.
+
+
+Point
+-----
+A zero dimensional geometry
+
+A point has zero length and zero area.
+
+Attributes
+~~~~~~~~~~~
+x, y, z : float
+ Coordinate values
+
+Example
+~~~~~~~~
+
+ >>> p = Point(1.0, -1.0)
+ >>> print p
+ POINT (1.0000000000000000 -1.0000000000000000)
+ >>> p.y
+ -1.0
+ >>> p.x
+ 1.0
+
+
+
+LineString
+-----------
+
+A one-dimensional figure comprising one or more line segments
+
+A LineString has non-zero length and zero area. It may approximate a curve
+and need not be straight. Unlike a LinearRing, a LineString is not closed.
+
+Attributes
+~~~~~~~~~~~
+geoms : sequence
+ A sequence of Points
+
+
+
+LinearRing
+-----------
+
+A closed one-dimensional geometry comprising one or more line segments
+
+A LinearRing that crosses itself or touches itself at a single point is
+invalid and operations on it may fail.
+
+A Linear Ring is self closing
+
+
+
+Polygon
+--------
+
+A two-dimensional figure bounded by a linear ring
+
+A polygon has a non-zero area. It may have one or more negative-space
+"holes" which are also bounded by linear rings. If any rings cross each
+other, the geometry is invalid and operations on it may fail.
+
+Attributes
+~~~~~~~~~~~
+
+exterior : LinearRing
+ The ring which bounds the positive space of the polygon.
+interiors : sequence
+ A sequence of rings which bound all existing holes.
+
+
+MultiPoint
+----------
+A collection of one or more points
+
+Attributes
+~~~~~~~~~~~
+
+geoms : sequence
+ A sequence of Points
+
+MultiLineString
+----------------
+A collection of one or more line strings
+
+A MultiLineString has non-zero length and zero area.
+
+Attributes
+~~~~~~~~~~~
+
+geoms : sequence
+ A sequence of LineStrings
+
+MultiPolygon
+-------------
+
+A collection of one or more polygons
+
+Attributes
+~~~~~~~~~~~~~
+geoms : sequence
+ A sequence of `Polygon` instances
+
+
+GeometryCollection
+-------------------
+A heterogenous collection of geometries (Points, LineStrings, LinearRings
+and Polygons)
+
+Attributes
+~~~~~~~~~~~
+geoms : sequence
+ A sequence of geometry instances
+
+Please note:
+GEOMETRYCOLLECTION isn't supported by the Shapefile format.
+And this sub-class isn't generally supported by ordinary GIS sw (viewers and so on).
+So it's very rarely used in the real GIS professional world.
+
+Example
+~~~~~~~~
+
+ >>> from pygeoif import geometry
+ >>> p = geometry.Point(1.0, -1.0)
+ >>> p2 = geometry.Point(1.0, -1.0)
+ >>> geoms = [p, p2]
+ >>> c = geometry.GeometryCollection(geoms)
+ >>> c.__geo_interface__
+ {'type': 'GeometryCollection', 'geometries': [{'type': 'Point', 'coordinates': (1.0, -1.0)},/
+ {'type': 'Point', 'coordinates': (1.0, -1.0)}]}
+ >>> [geom for geom in geoms]
+ [Point(1.0, -1.0), Point(1.0, -1.0)]
+
+Feature
+-------
+Aggregates a geometry instance with associated user-defined properties.
+
+Attributes
+~~~~~~~~~~~
+geometry : object
+ A geometry instance
+properties : dict
+ A dictionary linking field keys with values associated with with geometry instance
+
+Example
+~~~~~~~~
+
+ >>> p = Point(1.0, -1.0)
+ >>> props = {'Name': 'Sample Point', 'Other': 'Other Data'}
+ >>> a = Feature(p, props)
+ >>> a.properties
+ {'Name': 'Sample Point', 'Other': 'Other Data'}
+ >>> a.properties['Name']
+ 'Sample Point'
+
+FeatureCollection
+-----------------
+A heterogenous collection of Features
+
+Attributes
+~~~~~~~~~~~
+features: sequence
+ A sequence of feature instances
+
+Example
+~~~~~~~~
+
+ >>> from pygeoif import geometry
+ >>> p = geometry.Point(1.0, -1.0)
+ >>> props = {'Name': 'Sample Point', 'Other': 'Other Data'}
+ >>> a = geometry.Feature(p, props)
+ >>> p2 = geometry.Point(1.0, -1.0)
+ >>> props2 = {'Name': 'Sample Point2', 'Other': 'Other Data2'}
+ >>> b = geometry.Feature(p2, props2)
+ >>> features = [a, b]
+ >>> c = geometry.FeatureCollection(features)
+ >>> c.__geo_interface__
+ {'type': 'FeatureCollection', 'features': [{'geometry': {'type': 'Point', 'coordinates': (1.0, -1.0)},/
+ 'type': 'Feature', 'properties': {'Other': 'Other Data', 'Name': 'Sample Point'}},/
+ {'geometry': {'type': 'Point', 'coordinates': (1.0, -1.0)}, 'type': 'Feature',/
+ 'properties': {'Other': 'Other Data2', 'Name': 'Sample Point2'}}]}
+ >>> [feature for feature in c]
+ [<Feature Instance Point geometry 2 properties>, <Feature Instance Point geometry 2 properties>]
+
+Functions
+=========
+
+as_shape
+--------
+
+Create a pygeoif feature from an object that provides the __geo_interface__
+
+
+ >>> from shapely.geometry import Point
+ >>> from pygeoif import geometry
+ >>> geometry.as_shape(Point(0,0))
+ <pygeoif.geometry.Point object at 0x...>
+
+
+from_wkt
+---------
+
+Create a geometry from its WKT representation
+
+
+ >>> p = geometry.from_wkt('POINT (0 1)')
+ >>> print p
+ POINT (0.0 1.0)
+
+
+signed_area
+------------
+
+Return the signed area enclosed by a ring using the linear time
+algorithm at http://www.cgafaq.info/wiki/Polygon_Area. A value >= 0
+indicates a counter-clockwise oriented ring.
+
+orient
+-------
+
+Returns a copy of the polygon with exterior in counter-clockwise and
+interiors in clockwise orientation for sign=1.0 and the other way round
+for sign=-1.0
+
+
+mapping
+-------
+
+Returns the __geo_interface__ dictionary
+
+
+Development
+===========
+
+Installation
+------------
+
+You can install PyGeoIf from pypi using pip::
+
+ pip install pygeoif
+
+Testing
+-------
+
+In order to provide a Travis-CI like testing of the PyGeoIf package during
+development, you can use tox (``pip install tox``) to evaluate the tests on
+all supported Python interpreters which you have installed on your system.
+
+You can run the tests with ``tox --skip-missin-interpreters`` and are looking
+for output similar to the following::
+
+ ______________________________________________________ summary ______________________________________________________
+ SKIPPED: py26: InterpreterNotFound: python2.6
+ py27: commands succeeded
+ SKIPPED: py32: InterpreterNotFound: python3.2
+ SKIPPED: py33: InterpreterNotFound: python3.3
+ py34: commands succeeded
+ SKIPPED: pypy: InterpreterNotFound: pypy
+ SKIPPED: pypy3: InterpreterNotFound: pypy3
+ congratulations :)
+
+You are primarily looking for the ``congratulations :)`` line at the bottom,
+signifying that the code is working as expected on all configurations
+available.
diff --git a/docs/CONTRIBUTORS.txt b/docs/CONTRIBUTORS.txt
new file mode 100644
index 0000000..c0199ad
--- /dev/null
+++ b/docs/CONTRIBUTORS.txt
@@ -0,0 +1,7 @@
+Contributors
+=============
+
+- Ian Lee <IanLee1521 at gmail.com>
+- Zac Miller (jzmiller1)
+- John Dees (johnpdees)
+- NormWorthington
diff --git a/docs/HISTORY.txt b/docs/HISTORY.txt
new file mode 100644
index 0000000..8b4cf74
--- /dev/null
+++ b/docs/HISTORY.txt
@@ -0,0 +1,58 @@
+Changelog
+=========
+
+0.6 (2015/08/04)
+-----------------
+
+- Add id to feature [jzmiller1]
+
+0.5 (2015/07/13)
+-----------------
+
+- Add __iter__ method to FeatureCollection and GeometryCollection [jzmiller1].
+- add pypy and pypy3 and python 3.4 to travis.
+- Add tox configuration for performing local testing [Ian Lee].
+- Add Travis continuous deployment.
+
+0.4 (2013/10/25)
+-----------------
+
+- after a year in production promote it to `Development Status :: 5 - Production/Stable`
+- MultiPolygons return tuples as the __geo_interface__
+
+0.3.1 (2012/11/15)
+------------------
+
+- specify minor python versions tested with Travis CI
+- fix for signed area
+
+
+0.3 (2012/11/14)
+-------------------
+
+- add GeometryCollection
+- len(Multi*) and len(GeometryCollection) returns the number of contained Geometries
+- add orient function to get clockwise or counterclockwise oriented poygons
+- add signed_area function
+- add _set_orientation method to lineStrings, Polygons and MultiPolygons
+
+
+0.2.1 (2012/08/02)
+-------------------
+
+- as_shape also accepts an object that is neither a dictionary nor has a __geo_interface__ but can be converted into a __geo_interface__ compliant dictionary
+
+
+0.2 (2012/08/01)
+-----------------
+
+- change license to LGPL
+- add wkt as a property
+- as_shape also accepts a __geo_interface__ compliant dictionary
+- test with python3
+
+
+0.1 (2012/07/27)
+-----------------
+
+- initial release
diff --git a/docs/LICENSE.GPL b/docs/LICENSE.GPL
new file mode 100644
index 0000000..aae716b
--- /dev/null
+++ b/docs/LICENSE.GPL
@@ -0,0 +1,504 @@
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
... 3116 lines suppressed ...
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/python-modules/packages/pygeoif.git
More information about the Python-modules-commits
mailing list