Add BBox to Geometries.

[eseglem]

What I am changing

• Add BBox to Geometries.

How I did it

• Add optional bbox to _GeometryBase and GeometryCollection

How you can test it

• Only one minor tweak to a test. Don't think anything new is needed for the optional field.

Related Issues

• n/a

I was looking over some CQL2 stuff and got confused when I saw an optional BBox on their Geometries, but technically that is correct.

A GeoJSON object MAY have a member named "bbox" to include information on the coordinate range for its Geometries, Features, or FeatureCollections.

[geospatial-jeff]

LGTM

[vincentsarago]

can I ask you to add a line in the change log before we merge @eseglem 🙏

[marquesine]

Hi, I'm currently using the geojson_pydantic library (v. 0.6.1) with FastAPI. I appreciate the ready-made Pydantic models for GeoJSON. Thank you for your work on this.

I noticed that when I call some_polygon.dict(), the output includes a bbox attribute even though bounding boxes are optional in the GeoJSON specification. This happens even if the bounding box has not been calculated or set.

For instance:

>>> polygon = geojson_pydantic.Polygon(type="Polygon", coordinates=[[(0, 0), (0, 1), (1, 0), (0, 0)]])
>>> polygon.dict()
{'type': 'Polygon', 'coordinates': [[(0.0, 0.0), (0.0, 1.0), (1.0, 0.0), (0.0, 0.0)]], 'bbox': None}