We are simplifying the parcel schema. The per-row lrversion column is being retired from the Land Records nationwide parcel dataset and from the web API. It is a housekeeping change driven by our move to a more frequent release cadence, and it affects no other attribute — nothing is renamed and no data is lost.

Why we are removing it

lrversion stamped every parcel row with the label of the release it shipped in — a useful marker back when the dataset refreshed on a slow, quarterly rhythm. That rhythm has changed. Our hosted services and web API now refresh weekly, and bulk releases ship more often than they once did. A single version string baked onto all 150+ million rows no longer describes anything meaningful: the same result set can span records refreshed at different times, and the stamp costs a column on every row while duplicating information the release already carries.

Reproducibility hasn’t changed

Versioned bulk downloads aren’t going anywhere. Every download is still a point-in-time snapshot tied to a specific release, and earlier this year we noted that those downloads carried an lrversion stamp. With releases now landing more often, we are simply moving that version information out of the individual rows and onto the release itself — where it belongs. If you need a stable, citable baseline, pull a versioned release and keep the file; the version is recorded with the download rather than repeated inside every record.

What changes for you

• The lrversion field is removed from parcel records returned by the API.
• The lrversion column is removed from the parcel schema and from future bulk exports.
• No other columns are affected, and no columns are renamed.

If your integration reads lrversion, you can safely drop the field: rely on the API’s weekly freshness for currency, or on the versioned release you downloaded for a fixed, reproducible baseline. As always, schema changes are announced here and arrive with a release rather than mid-stream.

Questions about the change? Email hello@landrecords.us, or query the current dataset from your browser at /explore.