Skip to main content

NeoBase actions cratev crated

Minimalist GeoBases implementation:

  • no dependencies

  • compatible with Python 3.11+, CPython and PyPy

  • one data source: opentraveldata

  • one Python module for easier distribution on clusters (like Hadoop)

  • faster load time (5x)

  • tested with pytest and tox

  • passes static typing checks with ty

>>> from neobase import NeoBase
>>> b = NeoBase()
>>> b.get('ORY', 'city_code_list')
['PAR']
>>> b.get('ORY', 'city_name_list')
['Paris']
>>> b.get('ORY', 'country_code')
'FR'
>>> b.distance('ORY', 'CDG')
34.87...
>>> b.get_location('ORY')
LatLng(lat=48.72..., lng=2.35...)

Installation

Use the Python package:

pip install neobase

Docs

Check out readthedocs for the API.

You can customize the source data when initializing:

with open("file.csv") as f:
    N = NeoBase(f)

Otherwise the loaded file will be the embedded one, unless the OPTD_POR_FILE environment variable is set. In that case, it will load from the path defined in that variable.

You can manually retrieve the latest data source yourself too, but you expose yourself to some breaking changes if they occur in the data.

from io import StringIO
from urllib.request import urlopen

from neobase import NeoBase, OPTD_POR_URL

data = urlopen(OPTD_POR_URL).read().decode('utf8')
N = NeoBase(StringIO(data))
N.get("PAR")

The reference date of validity can be changed as well:

N = NeoBase(date="2000-01-01")
N.get("AIY")  # was decommissioned in 2015

By default, the reference date will be set to today, unless the OPTD_POR_DATE environment variable is set. In that case, it will use that value.

You can customize the behavior regarding duplicates: points sharing the same IATA code, like NCE as airport and NCE as city. By default everything is kept, but you can set it so that only the first point with an IATA code is kept:

N = NeoBase(duplicates=False)
len(N)  # about 10,000 "only"

Note that you can use the OPTD_POR_DUPLICATES environment variable to control this as well: set it to 0 to drop duplicates.

Finally, you can customize fields loaded by subclassing.

class SubNeoBase(NeoBase):
    KEY = 0  # iata_code

    # Those loaded fields are the default ones
    FIELDS = (
        ("name", 6, None),
        ("lat", 8, None),
        ("lng", 9, None),
        ("page_rank", 12, lambda s: float(s) if s else None),
        ("country_code", 16, None),
        ("country_name", 18, None),
        ('continent_name', 19, None),
        ("timezone", 31, None),
        ("city_code_list", 36, lambda s: s.split(",")),
        ('city_name_list', 37, lambda s: s.split('=')),
        ('location_type', 41, None),
        ("currency", 46, None),
    )

N = SubNeoBase()

Command-line interface

You can query the data using:

python -m neobase PAR NCE

Tests

tox

A note about performance

The geographical operations like N.find_near("ORY", 100) or N.find_closest_from("ORY") perform a full scan of the data, and are not optimized (remember that this library has no dependencies, by design).

If you want a more efficient solution, you should use a spatial index like a BallTree, for example using scikit-learn:

import numpy as np
from sklearn.neighbors import BallTree
from neobase import NeoBase

N = NeoBase()

iata_codes = []
coords = []
for key in N:
    lat, lon = N.get_location(key)
    if lat is not None and lon is not None:
        iata_codes.append(N.get(key, "iata_code"))
        coords.append([np.radians(lat), np.radians(lon)])
coords = np.array(coords)

tree = BallTree(coords, metric="haversine")

def find_closest_with_balltree(coord):
    point = np.radians(coord)
    _, idx = tree.query([point], k=1)
    iata_code = iata_codes[idx[0][0]]
    return iata_code

paris = (48.8566, 2.3522)
print(find_closest_with_balltree(paris))  # <0.1ms
print(list(N.find_closest_from_location(paris)))  # ~30ms

Metadata

Release files for NeoBase 0.37.2

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

Source distribution (sdist)

Source distribution for NeoBase 0.37.2
File Size Uploaded Provenance Actions
neobase-0.37.2.tar.gz 4.2 MB With provenance Details for neobase-0.37.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for NeoBase 0.37.2
File Interpreter ABI Platform Actions
neobase-0.37.2-py3-none-any.whl Python 3 none any Details for neobase-0.37.2-py3-none-any.whl

Total release size: 8.4 MB

Release files / neobase-0.37.2.tar.gz

Download URL neobase-0.37.2.tar.gz
Size 4.2 MB
Tags Source
SHA-256 checksum
How to use checksums
022bb83469ee37cbde329ba15e0a0275e1ad0c0a41d80beea0dce1efa02a3b13
BLAKE2b-256 checksum
How to use checksums
7b02690dc27d2632deccea6621d16b7d7620bc64702c8566755c1611faba389c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 8, 2026.

Transparency log

Release files / neobase-0.37.2-py3-none-any.whl

Download URL neobase-0.37.2-py3-none-any.whl
Size 4.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
c43f695a1c3d55a2ab9e0ee32594a3fe6c76f9764bd04ccb9bc334e5b66bc2f3
BLAKE2b-256 checksum
How to use checksums
b92f2a2907f86415fa8fcb557d272f1719e755a98baa7839f4bdb7c794f49758
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 8, 2026.

Transparency log

Security for NeoBase 0.37.2

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for neobase-0.37.2.tar.gz

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 Nov 8, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.37.2 This release

2 release files Full provenance

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