Compare boundary releases
Compare two releases of one geography and see which codes are shared, added or absent. Where published same-code evidence exists, it also reports whether an area's boundary stayed continuous, changed or remains indeterminate.
/boundary-releases:compareGood to know
- Code changes alone do not prove that a boundary changed. The response keeps code-set differences separate from measured continuity evidence.
- Use
limitto cap the examples returned for each finding; it does not change the release-level totals.
geographystringrequiredThe shared geography family of both releases.
fromstringrequiredThe earlier or source release id.
tostringrequiredThe later or target release id.
limitinteger 1–100optionalMaximum sample identifiers or continuity findings in each bounded list.
Default25
Returns
objectRelease-level code, continuity and crosswalk evidence.
- 400A query parameter is malformed or its cursor is not valid for this result set.
- 404No resource matches that identity.
- 503The referenced build artifact has not been built yet.
Every error has the same shape. See Errors for how to handle them.
Show the precise behaviourHide the precise behaviour
Compares the two compiled code sets, with identifiers present in only one release kept distinct from a claim that an area was added or removed. Shared codes are called continuous only where a published extent-continuity crosswalk measured their geometry. A code only one release holds is listed under continuity.recoded where that crosswalk found the same extent under a new code in the other. Its changed, indeterminate and unmeasured findings remain review evidence, not conversion claims. Other published crosswalks between the releases are named separately with their directional code cardinality and bounded split/merge-shaped examples. These describe published records, not a legal boundary-change finding, and need no runtime polygon comparison.