python-geosupport
Geocode NYC addresses locally using Python bindings for NYC Planning's Geosupport Desktop Edition.
Documentation
Check out documentation for installing and usage here.
Features
- Pythonic interface to all Geosupport functions
- Support for both Windows and Linux platforms
- Secure and fast using local geocoding - no API calls required
- Built-in error handling for Geosupport return codes
- Interactive help menu
Compatibility
- Python 3.8+
- Tested on Geosupport Desktop Edition 25a
- Windows (64-bit & 32-bit) and Linux operating systems
Quickstart
pip install python-geosupport
# Import the library and create a `Geosupport` object.
from geosupport import Geosupport
g = Geosupport()
# Call the address processing function by name
result = g.address(house_number=125, street_name='Worth St', borough_code='Mn')
result is a dictionary with the output from Geosupport. For example:
{
'2010 Census Block': '1012',
'2010 Census Tract': '31',
'Assembly District': '65',
'Atomic Polygon': '112',
'B10SC - First Borough and Street Code': '14549001010',
'BOE Preferred B7SC': '14549001',
'BOE Preferred Street Name': 'WORTH STREET',
'BOROUGH BLOCK LOT (BBL)': {
'BOROUGH BLOCK LOT (BBL)': '1001680032',
'Borough Code': '1',
'Tax Block': '00168',
'Tax Lot': '0032'
},
'Blockface ID': '0212261942',
...
}
Examples
See the examples directory and accompanying readme.md.
Contributing
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Run tests (
python -m unittest discover) - Run Black formatting (
black .) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
License
This project is licensed under the MIT License - see the license.txt file for details
Metadata
Release files for python-geosupport 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| python_geosupport-1.1.0.tar.gz | 37.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_geosupport-1.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 90.0 kB
Release files / python_geosupport-1.1.0.tar.gz
| Download URL | python_geosupport-1.1.0.tar.gz |
|---|---|
| Size | 37.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7798714c725f6e65a4f52808e01965ea107760dec19be2cad60ade3ec12647ff
|
|
BLAKE2b-256 checksum How to use checksums |
31ac0ad95fcd87727835448b43f5ad353423f87e458c5f83f9a9c5ee2a913a01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / python_geosupport-1.1.0-py2.py3-none-any.whl
| Download URL | python_geosupport-1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 53.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
917a2c5bef54e4711e6688dd3bf440df59c79cbb0efa891212aff0b8eaa74d1a
|
|
BLAKE2b-256 checksum How to use checksums |
b62d162ec539f06f3cc32215ce90f968d55c8fb80b0d9a03ae992973f372c9f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for python-geosupport 1.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.