tap-geo
tap-geo is a Singer tap for Geospatial datasets.
Built with the Meltano Tap SDK for Singer Taps.
Capabilities
catalogstatediscoveractivate-versionaboutstream-mapsschema-flatteningbatch
Supported Python Versions
- 3.10
- 3.11
- 3.12
- 3.13
- 3.14
Settings
| Setting | Required | Default | Description |
|---|---|---|---|
| files | True | None | List of file configs to parse |
| stream_maps | False | None | Config object for stream maps capability. For more information check out Stream Maps. |
| stream_maps.else | False | None | Currently, only setting this to __NULL__ is supported. This will remove all other streams. |
| stream_map_config | False | None | User-defined config values to be used within map expressions. |
| faker_config | False | None | Config for the Faker instance variable fake used within map expressions. Only applicable if the plugin specifies faker as an additional dependency (through the singer-sdk faker extra or directly). |
| faker_config.seed | False | None | Value to seed the Faker generator for deterministic output: https://faker.readthedocs.io/en/master/#seeding-the-generator |
| faker_config.locale | False | None | One or more LCID locale strings to produce localized output for: https://faker.readthedocs.io/en/master/#localization |
| flattening_enabled | False | None | 'True' to enable schema flattening and automatically expand nested properties. |
| flattening_max_depth | False | None | The max depth to flatten schemas. |
| batch_config | False | None | Configuration for BATCH message capabilities. |
| batch_config.encoding | False | None | Specifies the format and compression of the batch files. |
| batch_config.encoding.format | False | None | Format to use for batch files. |
| batch_config.encoding.compression | False | None | Compression format to use for batch files. |
| batch_config.storage | False | None | Defines the storage layer to use when writing batch files |
| batch_config.storage.root | False | None | Root path to use when writing batch files. |
| batch_config.storage.prefix | False | None | Prefix to use when writing batch files. |
A full list of supported settings and capabilities is available by running: tap-geo --about
Installation
Install from GitHub:
uv tool install git+https://github.com/celine-eu/tap-geo.git@main
Configuration
Accepted Config Options
See also meltano.yml for a working configuration
Provide a list of files with those fields
paths list of files in glob format, required
table_name name of the destination table, default to filename
primary_keys list of columns to use as primary keys
geometry_format store geospatial information in "wkt" (default) or "geojson"
bbox optional bounding box filter [west, south, east, north]
Example config
config:
files:
- paths:
- "data/osm/*.osm"
- "data/osm/**/*.pbf"
table_name: osm_data
primary_keys: ["id"]
geometry_format: "wkt"
- paths:
- "data/shapes/**/*.shp"
table_name: shapes
skip_fields: ["temp_field"]
expose_fields: ["col_name", "col_2"]
geometry_format: "geojson"
- paths:
- "data/buildings.geojson"
table_name: buildings
primary_keys: ["building_id"]
# e.g. use docker compose up to test locally
- paths:
- "s3://local-data/buildings.geojson"
table_name: buildings
primary_keys: ["building_id"]
# GeoParquet with bbox filter (e.g. Overture Maps buildings)
- paths:
- "s3://overturemaps-us-west-2/release/2026-05-20.0/theme=buildings/type=building/*"
table_name: overture_buildings
bbox: [-117.06, 32.58, -117.04, 32.59]
geometry_format: wkt
Supported Formats
| Format | Extensions | Bbox Behavior |
|---|---|---|
| Shapefile | .shp |
Post-parse spatial filter |
| GeoJSON | .geojson, .json |
Post-parse spatial filter |
| GPX | .gpx |
Post-parse spatial filter |
| OSM/PBF | .osm, .pbf |
Post-parse spatial filter |
| GeoPackage | .gpkg |
Post-parse spatial filter |
| GeoParquet | .parquet, .geoparquet |
Predicate pushdown (row-group pruning) |
Bounding Box Filter
The bbox parameter accepts [west, south, east, north] coordinates. For GeoParquet files, the filter is applied as predicate pushdown — only row groups intersecting the bbox are downloaded. For all other formats, records are filtered post-parse via geometry intersection.
S3 Storage
To use an S3-based storage, provide these environment variables:
S3_ACCESS_KEY_ID,S3_SECRET_ACCESS_KEYaccess key/secret pairS3_ENDPOINT_URLCustom S3 endpoint such as minio or compatible interface
For public S3 buckets (e.g. Overture Maps), no credentials are needed — anonymous access is used automatically when the environment variables above are not set.
Example:
S3_ACCESS_KEY_ID=minioadmin S3_SECRET_ACCESS_KEY=minioadmin S3_ENDPOINT_URL=http://localhost:19000 meltano run tap-geo target-jsonl
Configure using environment variables
This Singer tap will automatically import any environment variables within the working directory's
.env if the --config=ENV is provided, such that config values will be considered if a matching
environment variable is set either in the terminal context or in the .env file.
Source Authentication and Authorization
Usage
You can easily run tap-geo by itself or in a pipeline using Meltano.
Executing the Tap Directly
tap-geo --version
tap-geo --help
tap-geo --config CONFIG --discover > ./catalog.json
Developer Resources
Follow these instructions to contribute to this project.
Initialize your Development Environment
Prerequisites:
- Python 3.10+
- uv
uv sync
Create and Run Tests
Create tests within the tests subfolder and
then run:
uv run pytest
You can also test the tap-geo CLI interface directly using uv run:
uv run tap-geo --help
Testing with Meltano
Note: This tap will work in any Singer environment and does not require Meltano. Examples here are for convenience and to streamline end-to-end orchestration scenarios.
Next, install Meltano (if you haven't already) and any needed plugins:
# Install meltano
uv tool install meltano
# Initialize meltano within this directory
cd tap-geo
meltano install
Now you can test and orchestrate using Meltano:
# Test invocation:
meltano invoke tap-geo --version
# OR run a test ELT pipeline:
meltano run tap-geo target-jsonl
SDK Dev Guide
See the dev guide for more instructions on how to use the SDK to develop your own taps and targets.
Metadata
Release files for tap-geo 0.3.1
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 | |
|---|---|---|---|---|
| tap_geo-0.3.1.tar.gz | 272.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tap_geo-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 294.2 kB
Release files / tap_geo-0.3.1.tar.gz
| Download URL | tap_geo-0.3.1.tar.gz |
|---|---|
| Size | 272.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2717eebb72f2bd25d84cac0b73755bcc3d894972c3baddf96b3d0ce37ea64f58
|
|
BLAKE2b-256 checksum How to use checksums |
ff2ba904d77b67ddf676b03be0d450e3444be45b252f278a16163dc4ba79d869
|
| 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 Aug 7, 2026.
Transparency logRelease files / tap_geo-0.3.1-py3-none-any.whl
| Download URL | tap_geo-0.3.1-py3-none-any.whl |
|---|---|
| Size | 22.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c63c7a586594196e7cd2cc39b0fd7cb8f2d6e07a7537fdcc93c806ed98864c17
|
|
BLAKE2b-256 checksum How to use checksums |
98ed457af60081d5aac23f060e54ec38512bb41841a941e1bad76164d43d46b1
|
| 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 Aug 7, 2026.
Transparency logSecurity for tap-geo 0.3.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for tap_geo-0.3.1.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 Aug 7, 2026.
Transparency logA 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.