Data schema - Latest

School Ground Boundaries Product Guide

Product type
Data
Portfolio
Enrich
Product family
Enrich Boundaries > Community Boundaries
Product
Schools > School Ground Boundaries
Version
Latest
ft:locale
en-US
Product name
School Ground Boundaries
ft:title
School Ground Boundaries Product Guide
Copyright
2025
First publish date
2010
ft:lastEdition
2025-09-26
ft:lastPublication
2025-09-26T10:33:52.679000

The data schema workbook for School Ground 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:

School Ground Boundaries Data Schema 2025.06 - Latest

School Ground Boundaries Data Schema 2024.12 - 2025.06

School Ground Boundaries Data Schema 2024.09 - 2024.12

School Ground Boundaries Data Schema 2023.12 - 2024.09

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

Additional information about selected tables appears in the following sections

Names table

Table relationship is 1:many.

Location Attribute table

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

Grade Attribute table

Table relationship is 1:many.

Alternate Identifiers table

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

Change table

The Change table provides a direct listing of all features that have undergone change since the previous product release.

Note: This table reflects all change, not matter how small the geometry change may be. The PCT_A_CHNG field may show a value of 0.000000, which indicates that a change has been made that is smaller than can be represented in that field.

Using the Change table

Improper use of the Change table will result in data corruption. Precisely strongly recommends keeping 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.