Data schema - Latest

The data schema workbook for School Boundaries is included as part of the product delivery file downloaded from PDX. The current data schema workbook and earlier versions can also be downloaded using the following links:

Note: To access earlier versions not listed above, follow this link and use the Version dropdown to select the appropriate release.

The following sections contain additional information about selected tables in School Boundaries.

Objects table

Separate object tables are provided for school points, district boundaries, and school attendance zones. Refer to the Object types and subtypes section of this product guide for object type/subtype information.

Location Attribute table

The Location Attribute table provides primary address and location reference information. The table may be incomplete depending on feature type and available information. Table relationship is 1: many.

Primary Attribute table – school points

Table relationship is 1:1.

Primary Attribute table - school districts

Table relationship is 1:1.

The number of schools in a district and district student enrollment are unaltered NCES data. This information applies to the DIST_SCHS and DIST_ENRL fields, respectively.

Not all districts will have a district website URL. This information applies to the DIST_URL field.

Primary Attribute table - school attendance zones

Table relationship is 1:1

Multi-Attribute Table - school attendance zones

The Multi-Attribute table associates multiple school points with different grade levels within the same SAZ polygon. Table relationship is 1:many.

Change table

The Change table lists all features that have changed since the previous product release. This table reflects all changes, no matter how small the geometry delta may be.

Each release of School Boundaries will have a separate Change table for each object type (points, districts, and SAZs).

Note: The PCT_A_CHNG field may show a value of 0.000000, indicating that a change was smaller than the smallest value that can be represented in this field.

Alternate Identifiers table

The Alternate Identifiers table provides additional linkage across product layers and supports additional use cases. Table relationship is 1:many.

Using the Change table

Improper use of the Change table will result in data corruption. Precisely strongly recommends keep the following considerations in mind when using the Change table:

To prevent data corruption, changes from the Change table must be applied consistently with each new release

Precisely recommends doing a complete refresh of your data at regular intervals – ideally every six months, but no less than once a year