Repository navigation
Keeps okfgen faithful to the latest OKF v0.2 spec.
Google revised the OKF v0.2 specification in place (same version number) to require that every timestamp-valued key be an ISO 8601 datetime with an explicit UTC offset, not a bare YYYY-MM-DD date. okfgen's built-in spec-drift watcher caught it, and this release brings the output in line.
What changed
last_modifiedinsourcesis now emitted as a full ISO 8601 UTC datetime (e.g.2026-04-15T00:00:00Z) instead of a date.- The Socrata and git/local producers pass full timestamps through.
generated.atalready carried a UTC offset — unchanged.
Conformance rules are unchanged, so existing bundles still validate; this just makes okfgen's provenance timestamps match the revised spec exactly.
Install / upgrade
pip install -U okfgenFull Changelog: v0.1.2...v0.1.3