Scope, architecture, and validation¶

Package structure¶

The distribution is pystac-ext-ogc-record. Import the record adapter from pystac.extensions.ogc_record. The wheel excludes the shared namespace initializer owned by PySTAC.

OGC Records and STAC¶

OGCRecord subclasses pystac.Item to reuse links, assets, and compatible extension wrappers. It initializes STACObject directly to allow records without a STAC datetime. This dependency on PySTAC's object internals warrants testing when upgrading PySTAC.

Default serialization produces a Record GeoJSON Feature. STAC declarations and assets are preserved as foreign members when supplied. Use OGCRecord.from_dict() explicitly: ordinary PySTAC dispatch does not distinguish arbitrary records from STAC Items. to_stac_item() is an explicit conversion requiring a STAC instant or both interval endpoints. OGC time is independent and is never converted automatically.

Validation boundaries¶

Metadata setters and serialization do not run JSON Schema validation. Assigning None to a common metadata accessor removes that property. Setters do not create related links.

For STAC validation, install pystac[validation] and call the STAC object's validate(). Schema retrieval may require network access or an application-configured schema cache.

OGCRecord.from_dict() checks basic Feature structure, not full OGC conformance. The metadata accessors expose dictionaries and do not validate nested schemas. record.validate(validator) requires an explicit object exposing validate(document), configured for the OGC schema and references. Calling it without a validator raises ValueError. For STAC validation use record.to_stac_item().validate().

The adapter is an in-memory document interface, not an OGC API server, search client, or conformance certification. See OGC Record reference.