parcelId

The 4-character long numeric string (e.g. 5678) identifies the field parcel number. Concatenated automatically with parcelId to create "Field Number" (e.g. AB1234 5678)

sheetId

The 6-character long alpha-numeric string (e.g. AB1234) identifies the grid reference number of the parcel number. Concatenated automatically with sheetId to create "Field Number" (e.g. AB1234 5678)

description

An unlimited character string that sits as a description of the feature.

name

An unlimited character string that sits as a name of the feature.

laFeatureType

The defining attribute code that styling and attribution run off. For each plan template, this must match the schema exactly. For each plan template, "laFeatureType" is unique. For example, on the Countryside Stewardship template, "laFeatureType" is the CSS code such as "AB15" or "GS2". For Baseline Habitat Assessment or Land Management Plan, the "laFeatureType" is the UKHab Code, such as "g1" or "c1a6".

area

This field is automatically generated and calculated by Land App. If a file with this field is already populated, the Land App will not auto-calculate and errors may arise.

perimeter

This field is automatically generated and calculated by Land App. If a file with this field is already populated, the Land App will not auto-calculate and errors may arise.

laScore

Condition assessments, stored as a categorical value, either: "Good", "Fairly Good", "Moderate", "Fairly Poor" or "Poor".

laSecCodes

Secondary Codes, stored as nested values, using just the numeric value for each unique Secondary code, started with {0}, e.g.

for 3 Secondary codes, you need 3 attributes called:
​laSecCodes{0} = "60"

laSecCodes{1} = "120"

laSecCodes{2} = "121"

etc. (making a new attribute for each secondary code)