Subdivisions

Current and historic subdivisions

Subdivisions
Boundaries
Developments
Cadastral

Usage

The data in this layer does not represent a survey. No accuracy is assumed for the data delineated herein, either expressed or implied by Kendall County or its employees.

These data are compiled from official records, including plats, surveys, recorded deeds, contracts, and only contains information required for local government purposes. See the recorded documents for more detailed legal information.

Layer Information

This layer is a snapshot of Kendall County’s official subdivisions layer, as maintained by the GIS Department.

Fields

Field Description
name The name of the subdivision.
created_doc The ID number of the document responsible for creating / modifying the subdivision.
retired_doc The ID number of the document responsible for retiring / modifying the subdivision.
create_date The date the subdivision was legally created, i.e., the date the associated document was recorded.
retired_date The date the subdivision was legally retired, i.e., the date the associated document was recorded.
reccode The shorthand code assigned by the Recorder’s Office
slot_num The slot number(s) of the corresponding subdivision plat

Retiring / Modifying

In a legal sense, subdivisions never get retired. An area can be re-subdivided later, and the subdivisions simply “stack”. For the sake of having clear, easy-to-understand maps, we treat subdivisions as if they do not overlap. When a resubdivision overlaps an existing subdivision, we store the original shape of the existing area, but retire it. The new, non-overlapping portion is left behind as active.

Working with Historic Data

Because this layer includes both current and historic features, it may be necessary to filter the data to get what you’re looking for.

Document Date / Number

Document information began to be tracked on our features in 2020. Features created before 2020 may not have any information for the document which created it.

Similarly, features retired before 2020 may not be in the data at all.

We are working to add historic subdivision and document information to the map. As those changes are made, the information will be reflected in this layer.

Filtering Data

Here are some common scenarios for filtering the information and how you might do it. Assuming your software as a SQL-like expression builder, here is the SQL you might paste in to filter it.2

Any feature that has no retired_doc information can be assumed to be current. Because of how the underlying data model works, missing information is sometimes equal to an empty string (''), not NULL.

retired_doc = '' or retired_doc is null

The inverse of the preceding filter. Any feature which does have retired_doc information can be assumed to be retired.

retired_doc != '' or retired_doc is not null

To see features year by year, you can filter on both the created and retired dates. The query is more specific, because for a given year, we want subdivisions which are:

  • Still current
  • Are retired, but were current in a certain year

For example, to get the active subdivisions for 2022, you would filter as follows:

(retired_date > '2022-12-31' or retired_doc = '' or retired_doc is null) and
(create_date < '2023-01-01' or created_doc = '' or created_doc is null)

Footnotes

  1. Field names are limited to 10 characters, and dates are stored with less precision, among other things.↩︎

  2. If you’re using the shapefile, adjust the field names accordingly.↩︎