vibeSpatial
vibeSpatial is an early GPU-first spatial analytics library for Python. It keeps GeoPandas-style workflows on CUDA where native paths exist, and makes CPU compatibility fallback explicit when they do not.
The strongest paths today are bulk I/O, CRS transforms, device-backed geometry buffers, predicates, selected constructive/overlay/dissolve workloads, and Arrow/Parquet export. Performance is workload-dependent: some public workflows are already faster than GeoPandas, while others are still limited by compatibility boundaries, composition overhead, or missing physical operators.
[!WARNING] vibeSpatial is still under active development. Public API compatibility and GPU residency are improving quickly, but GPU coverage is not the same thing as end-to-end speed on every GeoPandas workload.
Fallbacks should be observable. If a workflow silently leaves the GPU path, produces a correctness mismatch, or loses badly where the shape should be accelerated, please file an issue.
Install
pip install vibespatial # CPU-only GeoPandas-compatible API
pip install vibespatial[cu12] # CUDA 12 GPU acceleration
pip install vibespatial[cu13] # CUDA 13 GPU acceleration
Quick Start
import vibespatial as gpd
gdf = gpd.read_file("my_data.gpkg")
buffered = gdf.buffer(100)
joined = gpd.sjoin(gdf, buffered)
gdf.to_parquet("out.parquet")
Example: 7.2 Million Buildings
Load every building footprint in Florida, reproject to UTM, find all buildings
within 1 km of a random pick, and export to GeoParquet. The full script is
at examples/nearby_buildings.py.
import vibespatial as gpd
import random
# Read 7.2M buildings from Microsoft US Building Footprints
gdf = gpd.read_file("Florida.geojson")
# Reproject to UTM for metric distances
gdf_utm = gdf.to_crs(gdf.geometry.estimate_utm_crs())
# Pick a random building and find everything within 1 km
seed = gdf_utm.geometry.iloc[random.randrange(len(gdf_utm))]
nearby = gdf_utm[gdf_utm.geometry.dwithin(seed.centroid, 1_000)]
# Export to GeoParquet
nearby.to_crs(epsg=4326).to_parquet("nearby_buildings.parquet")
For compatible workflows, code can often stay close to GeoPandas:
-import geopandas as gpd
+import vibespatial as gpd
gdf = gpd.read_file("Florida.geojson")
gdf_utm = gdf.to_crs(gdf.geometry.estimate_utm_crs())
seed = gdf_utm.geometry.iloc[random.randrange(len(gdf_utm))]
nearby = gdf_utm[gdf_utm.geometry.dwithin(seed.centroid, 1_000)]
nearby.to_crs(epsg=4326).to_parquet("nearby_buildings.parquet")
This public example is currently I/O and reprojection dominated, which is where vibeSpatial is strongest. On a local RTX 4090 / i9-13900K run:
| Step | GeoPandas | vibeSpatial | Speedup |
|---|---|---|---|
| Read GeoJSON | 57.7 s | 6.7 s | 8.6x |
| Reproject to UTM | 8.2 s | 0.1 s | 82x |
| Select within 1 km | 0.2 s | 0.2 s | 1.0x |
| End-to-end including GeoParquet export | 66.3 s | 8.0 s | 8.3x |
This is one representative public path, not a blanket performance claim. The
maintained shootout workflows in benchmarks/shootout/
are used to track where performance generalizes and where more physical-plan
work is still needed.
Current Focus
- Keep geometry device-resident across public workflows instead of repeatedly materializing pandas/Shapely intermediates.
- Expand reusable physical shapes such as semijoins, anti-semijoins, many-few overlay, mask clip, and grouped geometry reduction.
- Preserve GeoPandas compatibility while making CPU fallback and host/device transfers visible.
- Use vendored GeoPandas tests and public workflow shootouts as the correctness and performance contract.
Tech Stack
| Layer | Technology |
|---|---|
| GPU kernels | NVRTC (runtime-compiled CUDA C via cuda-python) |
| GPU primitives | CCCL (cccl — scan, sort, reduce, select) |
| GPU arrays | CuPy (device memory, element-wise ops, prefix sums) |
| GPU JSON parse | Custom byte-classification kernels (ADR-0038) |
| GPU projection | vibeProj |
| GPU Parquet/Arrow | pylibcudf (WKB decode, GeoArrow codec) |
| CPU compatibility | GeoPandas API (vendored upstream test suite) |
| JSON parsing | orjson (property extraction) |
| File I/O | Native GPU/hybrid routes for GeoJSON, Shapefile, FlatGeobuf, GeoJSONSeq, and OSM PBF; pyogrio for GDAL compatibility |
| Packaging | uv, hatchling |
GPU kernels are shipped as Python source strings and compiled at runtime with
NVRTC. Compiled CUBINs are cached on disk, so the JIT cost is paid once per
install. No compiled extensions or nvcc build step are required.
| Package | Wheel size |
|---|---|
| vibespatial | 612 KB |
| vibeproj | 57 KB |
| vibespatial-raster | 51 KB |
| Total | 720 KB |
Pre-compilation
The first time a GPU operation runs, CUDA kernels are JIT-compiled in the background (~2-3 s wall time on 8 threads). Compiled CUBINs are cached on disk so subsequent process starts are near-instant. To pre-populate the caches (e.g. in CI or after install):
from vibespatial.cccl_precompile import precompile_all
precompile_all() # compiles all 21 CCCL specs + 61 NVRTC kernels, blocks until done
Or from the command line:
uv run python -c "from vibespatial.cccl_precompile import precompile_all; precompile_all()"
See GPU Kernel Caching for the full design and environment variables.
Documentation
See the documentation for the full API reference, GPU acceleration guide, and I/O format support matrix.
Contributing
uv sync --group dev
uv run python scripts/check_docs.py --refresh
uv run python scripts/vendor_geopandas_tests.py
uv run pytest tests/upstream/geopandas/tests/test_config.py
Dependency groups
dev: local development and pytest toolingupstream-optional: heavier I/O and visualization extras for broader coveragegpu-optional: CUDA runtime, CuPy, pylibcudf
Layout
src/vibespatial/: package codesrc/geopandas/: GeoPandas compatibility shimtests/: repo-owned teststests/upstream/geopandas/: vendored upstream GeoPandas test suitedocs/: architecture docs and ADRsexamples/: benchmarks and usage examples
Metadata
Release files for vibespatial 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vibespatial-0.5.3.tar.gz | 8.8 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vibespatial-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.1 MB
Release files / vibespatial-0.5.3.tar.gz
| Download URL | vibespatial-0.5.3.tar.gz |
|---|---|
| Size | 8.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a25e772b1ae9f148ee72b967371a6634437941e608cf22b8b5079981d4ceafa
|
|
BLAKE2b-256 checksum How to use checksums |
11a0da511ea0ac87f5630248467a3adb325f09fd478b6a525f0f23891b20a587
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency logRelease files / vibespatial-0.5.3-py3-none-any.whl
| Download URL | vibespatial-0.5.3-py3-none-any.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
992847501adc1e26624e24262e8a2797319a01a5b6f6cc8b26e3cbefa6c884cf
|
|
BLAKE2b-256 checksum How to use checksums |
2edfcf4e741bc4d3141b582dc9400c9baaaf75253beb5d9d12302ff5d80a6ba1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency log