Pydantic GeoJSON Models

2.1.1 · active · verified Sun Apr 12

geojson-pydantic provides a suite of Pydantic models that strictly adhere to the GeoJSON specification (RFC 7946). These models are invaluable for creating, validating, and working with GeoJSON data in a type-safe manner. The library is actively maintained, supporting Python 3.9 and above, with a consistent release cadence that includes performance improvements and Pydantic V2 compatibility.

Warnings

breaking Migration to Pydantic V2.0: geojson-pydantic versions 1.0 and above require Pydantic V2.0+. This involves significant breaking changes from Pydantic V1, including method renames like `dict()` to `model_dump()`, `json()` to `model_dump_json()`, and `parse_obj()` to `model_validate()`. Older geojson-pydantic versions (e.g., <=0.6.3) are incompatible with Pydantic V2.
Fix: Upgrade Pydantic to V2 and update your code to use the new `model_` prefixed methods. For instance, `my_model.json()` becomes `my_model.model_dump_json()`. Review Pydantic's official migration guide for V1 to V2 changes.
breaking Removed custom iteration, length, and item access for `GeometryCollection` and `FeatureCollection`: Version 2.0.0 removed custom `__iter__`, `__getitem__`, and `__len__` methods. Direct iteration or `len()` calls on these objects will now fail.
Fix: For iteration, use the `.iter()` method (e.g., `for geom in collection.iter()`). For length, use the `.length` property (e.g., `collection.length`). For item access, access the underlying lists directly (e.g., `collection.geometries[0]` or `collection.features[0]`).
breaking Changed generic typing for `FeatureCollection`: From version 1.0, the generic `FeatureCollection` model now expects a generic `Feature` model. The type hint has changed from `FeatureCollection[Geometry, Properties]` to `FeatureCollection[Feature[Geometry, Properties]]`.
Fix: Update generic type hints for `FeatureCollection` to nest the `Feature` type. For example, if you had `MyFc = FeatureCollection[Polygon, CustomProperties]`, it should now be `MyFc = FeatureCollection[Feature[Polygon, CustomProperties]]`.
gotcha Missing 'type' attribute when creating GeoJSON objects: All GeoJSON objects require a 'type' attribute (e.g., 'Point', 'Feature', 'Polygon') as part of their data structure, which is then validated by geojson-pydantic. Omitting this will lead to validation errors.
Fix: Always include the mandatory 'type' field with the correct GeoJSON object type string when constructing data for geojson-pydantic models. For example: `Point(type="Point", coordinates=[...])`.

Install

pip install geojson-pydantic Install stable version

Imports

Point
```
from geojson_pydantic import Point
```
Feature
```
from geojson_pydantic import Feature
```

FeatureCollection

from geojson_pydantic import FeatureCollection

GeometryCollection

from geojson_pydantic import GeometryCollection

Quickstart

Demonstrates how to create a simple GeoJSON Point and Feature object using geojson-pydantic, validating and serializing them to JSON. Note the use of `model_dump_json()` for serialization with Pydantic V2.

from geojson_pydantic import Feature, Point

# Define a GeoJSON Point object data
geoj_point_data = {
    "type": "Point",
    "coordinates": [-105.01621, 39.57422]
}

# Create a Pydantic Point model instance
point_obj = Point(**geoj_point_data)
print(f"Point Object: {point_obj.model_dump_json()}")

# Define a GeoJSON Feature object data
geoj_feature_data = {
    "type": "Feature",
    "geometry": geoj_point_data, # Use the previously defined point data
    "properties": {"name": "Example Feature", "value": 123}
}

# Create a Pydantic Feature model instance
feature_obj = Feature(**geoj_feature_data)
print(f"Feature Object: {feature_obj.model_dump_json()}")

view raw JSON →