Data schema - Latest

The data schema workbook for Neighborhood 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.

Additional information about selected tables is provided in the following sections.

Names table

Table relationship is 1:many.

Parents table

The Parents table provides an ID reference to the overlying parent object. Table relationship is 1:many.

Classification table

The Classification table lists residential exception classifications. Table relationship is 1:many.

Exception codes identify polygons whose geometric or attribute references differ from standard representation:

Exception Code	Exception Description
00	Default; no additional classification currently assigned
10	Non-neighborhood areas of interest (colleges, airports, etc.)
11	Neighborhoods roughly based on Census Place/MCD source
12	Geometry overlap validated by resource
13	Valid multipart polygon (such as a neighborhood with islands)
14	Name has been validated and is similar to another name within the metro
15	Valid multipart polygon and also a neighborhood based roughly on Census Place/MCD source
16	Geometry overlap validated by resource. Name validated and is similar to another name within the metro.
17	Valid multipart polygon. Neighborhood name has been validated and is similar to another name within the metro.

ZIP Correlation Attributes table (US only)

The ZIP Correlation Attribute table defines relationships between neighborhoods and ZIP Codes. Any ZIP Code that overlaps by less than 5% is not included in this table. Table relationship is 1:many.

Change table

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

Note: This table reflects all change, no matter how small the geometry 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 the value that 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

Object types and subtypes

OBJ_TYPE	OBJ_SUBTYP	OBJ_SUBTCD
Neighborhood	Macro Neighborhood	M
Neighborhood	Neighborhood	N
Neighborhood	Sub Neighborhood	S