Skip to main content

natural-language-geocoding

Natural Language Geocoding can geocode natural language descriptions of places on the Earth into the geometry.

Try it out: element84.com/natural-language-geocoding/

Installing and Using

pip install natural-language-geocoding
natural-language-geocoding init

See documentation on how to configure and populate the OpenSearch cluster in Sources.

Running the demo

There's a streamlit demo in src/natural_language_geocoding_demo. It can be run by following these steps.

  1. Set up AWS credentials. The demo uses AWS Bedrock Anthropic Claude as the LLM. Valid AWS access keys to an account need to be present.
  2. Follow steps for local development
  3. Create and populate an OpenSearch cluster following the instructions in Sources.
  4. Run scripts/run_demo.sh
  5. It will open in your browser

Developing

  1. Install python and uv
  2. Checkout the code
  3. Run scripts/recreate_venv.sh
  4. Run PYTHONPATH=src python src/natural_language_geocoding/main.py init
  5. Run pre-commit install to install the pre commit checks
  6. Make changes
  7. Verify linting passes scripts/lint.sh
  8. Commit and push your changes

Contributions

We are happy to take contributions! It is best to get in touch with the maintainers about larger features or design changes before starting the work, as it will make the process of accepting changes smoother.

Contributor License Agreement (CLA)

Everyone who contributes code to natural language geocoding will be asked to sign a CLA, which is based off of the Apache CLA.

  • Download a copy of one of the following from the docs/cla directory in this repository:

    • Individual Contributor (You're using your time): 2024_1_24-Natural-Language-Geocoding-Open-Source-Contributor-Agreement-Individual.pdf
    • Corporate Contributor (You're using company time): 2024_1_24-Natural-Language-Geocoding-Open-Source-Contributor-Agreement-Corporate.pdf
  • Sign the CLA -- either physically on a printout or digitally using appropriate PDF software.

  • Send the signed CLAs to Element 84 via one of the following methods:

    • Emailing the document to contracts@element84.com
    • Mailing a hardcopy to: Element 84, 210 N. Lee Street Suite 203 Alexandria, VA 22314, USA.

Attribution

See Sources for attribution and licensing information.

Metadata

Release files for natural-language-geocoding 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for natural-language-geocoding 0.1.3
File Size Uploaded
natural_language_geocoding-0.1.3.tar.gz 409.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for natural-language-geocoding 0.1.3
File Interpreter ABI Platform
natural_language_geocoding-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 504.1 kB

Release files / natural_language_geocoding-0.1.3.tar.gz

Download URL natural_language_geocoding-0.1.3.tar.gz
Size 409.2 kB
Tags Source
SHA-256 checksum
How to use checksums
12711ee79397035a2a656bf4131b3b7dc529824fece8241fa02c2b8be9fd4ca0
BLAKE2b-256 checksum
How to use checksums
714eb04be5f257e743f1325702aec6769b79609713a2b985bae92a4b475fe609
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 18, 2026.

Transparency log

Release files / natural_language_geocoding-0.1.3-py3-none-any.whl

Download URL natural_language_geocoding-0.1.3-py3-none-any.whl
Size 94.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f83be0cbe5fdfc7b34620f9137724c51a293619c92e1f11f5a3b96e02777fdd2
BLAKE2b-256 checksum
How to use checksums
87162f3157f6bfbc4e4c3b65faf06dd81af7d352ebd74e80ef8075fa0bdb0dc6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 18, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.3 This release

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

0.0.3

2 release files

0.0.2

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page