v1.18.0

What's Changed

Below is a list of changes to the schema since the last release.

Schema-Wide Changes

• Added optional provider, resource, and version fields to the sources object for data provenance tracking (first step toward deprecating dataset, targeted for a breaking change in September). (#535)

Theme-Specific Schema Changes

Addresses (Status: Alpha)

🏗 The addresses theme is in alpha status. Schema changes with potential backward-incompatibility are likely from month to month until the addresses schema increases in maturity. When these changes occur, we will try to provide some notice and a "bridge" period where the old schema is also supported.

No changes.

Base (Status: GA)

🟢 The base theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

No changes.

Buildings (Status: GA)

🟢 The buildings theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

No changes.

Divisions (Status: GA)

🟢 The divisions theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

• Fixed DivisionArea/DivisionBoundary schema to allow is_land and is_territorial to both be true simultaneously (previously mutually exclusive). (#546)

Places (Status: GA)

🟢 The places theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

No changes.

Transportation (Status: GA)

🟢 The transportation theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

No changes.

Full Changelog: v1.17.0...v1.18.0