Skip to main content
All CollectionsFAQs
Technical Guide: Importing data into the Land App
Technical Guide: Importing data into the Land App

Technical information on Land App imports

Simla Rees-Moorlah avatar
Written by Simla Rees-Moorlah
Updated over a week ago

The Land App has a consistent format across all its Plan Templates that must be adhered to if styling or attribution is to be prepopulated from imported data.

The below table shows our schema for data to help you with this (please note all "Land App Attributes" are case sensitive).

General Structure (all templates):

Land App Attribute

Description

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.

UKHab Specific (Baseline Habitat Assessment or Land Management Plan)
The above plus:

Land App Attribute

Description

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)

Please note:

  • File Type: If using ESRI Shapefiles (.shp), the maximum character count for attributes is 10, therefore some Land App Attributes (e.g β€œlaFeatureType”) will get truncated, thus no styling will be assigned. To resolve this, please use the GeoJSON format and assign the full Land App Attribute before importing it to the Land App.

  • Projection: The Land App runs off British National Grid, BNG (EPSG:27700)

  • Process to import: Please see this guidance.

Did this answer your question?