Cadastral Framework Project
Validation and Processing Rules
FW1. If a feature is added then accept.
FW2. If a feature is updated then the new feature takes the framework id of the old feature, the old feature framework id is assigned to the framework lineage id, assigned a new framework id, and a retirement date.
FW3. If the steward cannot resolve a data conflict, then the new feature is rejected and the current feature is flagged as in dispute.
CP1. If the distance between the old corner point and the new corner point is within the accuracy level of the old corner point and the old corner point is within the accuracy level of the new corner point and the accuracy of the new corner point is better than the old accuracy then accept. Else refer to the steward. If the steward verifies then accept.
Center: If the new point with better accuracy is not within the accuracy of the old point then there are probably two different corner points.
Right: CP1. The new point is a probably a better defined representation of the old point.
CP2. If the corner update has an additional class then add the new class. Example: The corner is a section corner. The update for the same corner identifier lists the corner as a subdivision corner. Add the subdivision corner to the corner class.
CP3. If a corner point is updated then the associated boundaries and legal description areas must also be updated within the same geographic transaction.
If an old boundary is divided into new boundaries then supercede the old boundaries,
replace any references to the old boundary with all of the new ones.
If a boundary line is subdivided into new boundary lines then each of the new lines should refer to the original boundary line as the parent by the parent identifier. There is no need to change the business relationships that the original boundary line has. The business relationships of the new boundary lines need to be established.
BL3. If the new boundary has a different type than the old boundary then add the new type.
BL4. If a boundary line is updated without changes in the corner points then the associated legal description areas must also be updated within the same geographic transaction.
Legal Description Area
LDA1. If the description area is new then accept. New subdivisions are additions to the database. By default the descriptions in the database are township and section. There is a need to include government lots and 1/16 section subdivisions as default legal descriptions. Other legal descriptions, such as E2, W2SE, SWSWSW, and Marysville 2nd Addition Block 3 Lot 29 would be added as needed to describe specific parcels.
If an old description is subdivided into new description areas then supercede the old
description, replace any references to the old description with all of the new ones.
If a description area is subdivided into new description areas then each of the new subdivisions should refer to the original description area as the parent by the parent identifier. There is no need to change the business relationships that the original description area has. The business relationships of the new subdivisions need to be established.
Example: the descriptions for this section would include
NE, NW, SW, SE
NENE, NWNE, SWNE, SENE, E2SE, NWSE, SWSE
Each of the subdivisions would reference the aliquot part which was subdivided in order to create it.
PA1. If the parcel is included in or excluded from a specific legal description area then accept.
PA2. If the parcel is nominally located in a legal description then reject.
PA3. If the parcel is subdivided into new parcels by a county then accept. Else refer to the steward (county) for verification. If the county verifies then accept.