Welcome to geotext’s documentation!¶
Contents:
geotext¶
Geotext extracts country and city mentions from text
- Free software: MIT license
- Documentation: https://geotext.readthedocs.org.
Usage¶
from geotext import GeoText
places = GeoText("London is a great city")
places.cities
# "London"
GeoText('New York, Texas, and also China').country_mentions
# OrderedDict([(u'US', 2), (u'CN', 1)])
Features¶
- No external dependencies
- Fast
- Data from http://www.geonames.org licensed under the Creative Commons Attribution 3.0 License.
Similar projects¶
geography: geography is more advanced and bigger in scope compared to geotext and can do everything geotext does. On the other hand geotext is leaner: has no external dependencies, is faster (re vs nltk) and also depends on libraries and data covered with more permissive licenses.
Installation¶
At the command line:
$ easy_install geotext
Or, if you have virtualenvwrapper installed:
$ mkvirtualenv geotext
$ pip install geotext
Usage¶
To use geotext in a project:
from geotext import GeoText
places = GeoText("London is a great city")
places.cities
# "London"
GeoText('New York, Texas, and also China').country_mentions
# OrderedDict([(u'US', 2), (u'CN', 1)])
Contributing¶
Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report Bugs¶
Report bugs at https://github.com/elyase/geotext/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Fix Bugs¶
Look through the GitHub issues for bugs. Anything tagged with “bug” is open to whoever wants to implement it.
Implement Features¶
Look through the GitHub issues for features. Anything tagged with “feature” is open to whoever wants to implement it.
Write Documentation¶
geotext could always use more documentation, whether as part of the official geotext docs, in docstrings, or even on the web in blog posts, articles, and such.
Submit Feedback¶
The best way to send feedback is to file an issue at https://github.com/elyase/geotext/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Get Started!¶
Ready to contribute? Here’s how to set up geotext for local development.
Fork the geotext repo on GitHub.
Clone your fork locally:
$ git clone git@github.com:your_name_here/geotext.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ mkvirtualenv geotext $ cd geotext/ $ python setup.py develop
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:
$ flake8 geotext tests $ python setup.py test $ tox
To get flake8 and tox, just pip install them into your virtualenv.
Commit your changes and push your branch to GitHub:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests.
- If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
- The pull request should work for Python 2.6, 2.7, 3.3, and 3.4, and for PyPy. Check https://travis-ci.org/elyase/geotext/pull_requests and make sure that the tests pass for all supported Python versions.
Credits¶
Development Lead¶
- Yaser Martinez Palenzuela <yaser.martinez@gmail.com>
Contributors¶
None yet. Why not be the first?
History¶
0.1.0 (2014-01-11)¶
- First release on PyPI.