Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Farm maps in LiteFarm allow users to add three types of drawings to their farm maps: areas, lines, and structures.

  1. Areas are drawn polygons that have area. In general, the utility of the polygon is tied to its size. Examples of areas include fields, natural areas, residences, barns, greenhouses, etc.

  2. Lines are drawn, multi-point segments that don’t form a closed polygon. In general, lines don’t have an area (such as with fences) or their area is relatively uniform and based on the direction of the line (such as with creeks or buffer areas). Examples of lines are: fences, creeks, roads, and footpaths

  3. Points on the other hand are coordinates that are dropped on the map. For all intents and purposes, they don’t have an “area” per se, but rather provide a service based on their location. Examples of structures include water valves and gates

For our Spring 2021 release, the following areas will be supported:

Area type

Attributes

Other notes

Farm site boundary

  • Name: String (optional)

  • Total area: Decimal

  • Perimeter: Decimal

  • Notes (optional)

Field

  • Name: String

  • Total area: Decimal

  • Perimeter: Decimal

  • Organic status: Enum

    • Transition Date: Date

  • Notes (optional)

Total area and perimeter should be pre-populated by the maps API, but modifiable by the user.

Organic status: {“Non-organic” (default), “Transitional”, “Organic”)

Transition date only shown if transitional or organic are chosen.

Barn

  • Name: String

  • Total area: Decimal

  • Has wash and pack station: Enum (option)

  • Has cold storage: Enum (option)

  • Notes (optional)

Total area should be pre-populated by the maps API, but modifiable by the user.

Both enums have the following values: {““, “No”, “Yes”}

Greenhouse

  • Name: String

  • Total area: Decimal

  • Organic status: Enum

    • Transition Date: Date

  • Notes (optional)

Total area should be pre-populated by the maps API, but modifiable by the user.

Organic status: {“Non-organic” (default), “Transitional”, “Organic”)

Transition date only shown if transitional or organic are chosen.

Natural area

  • Name: String

  • Total area: Decimal

  • Perimeter: Decimal

  • Notes (optional)

Total area and perimeter should be pre-populated by the maps API, but modifiable by the user.

Groundwater

  • Name: String

  • Total area: Decimal

  • Perimeter: Decimal

  • Used for irrigation: Enum (optional)

  • Notes (optional)

Total area and perimeter should be pre-populated by the maps API, but modifiable by the user.

  • Used for irrigation: {““, “No”, “Yes”}

Residence

  • Name: String

  • Total area: Decimal

  • Notes (optional)

Total area should be pre-populated by the maps API, but modifiable by the user.

Ceremonial area

  • Name: String

  • Total area: Decimal

  • Perimeter: Decimal

  • Notes (optional)

Total area and perimeter should be pre-populated by the maps API, but modifiable by the user.

For our Spring 2021 release, the following lines will be supported:

Line type

Attributes

Other notes

Fence

  • Name: String (optional)

  • Length: Decimal

  • Pressure treated: Enum (Organic required)

  • Notes (optional)

Length should be pre-populated by the maps API, but modifiable by the user.

Fences that are pressure treated need to be declared for organic certifications. Only shown for organic certification. Options: {““, “Yes”, “No”}

Creek

  • Name: String (optional)

  • Length: Decimal

  • Used for irrigation: Enum (optional)

  • Includes riparian buffer: Enum (optional)

    • Buffer width: Decimal (optional)

  • Notes (optional)

Length should be pre-populated by the maps API, but modifiable by the user.

Used for irrigation: {““, “Yes”, “No”}

Includes riparian buffer: {““, “Yes”, “No”}

Buffer zone

  • Name: String (optional)

  • Width: Decimal

  • Notes (optional)

Total area and perimeter should be pre-populated by the maps API, but modifiable by the user.

Width is required. Standard is 8 meters for separation of organic and non-organic areas - though there are many reasons it can be less. Must be modifiable.

Road

  • Name: String (optional)

  • Length: Decimal

  • Type: Enum (optional)

  • Notes (optional)

Length should be pre-populated by the maps API, but modifiable by the user.

Type: {“Earthen” (default), “Gravel”, “Paved”}

Footpath

  • Name: String (optional)

  • Length: Decimal

  • Type: Enum (optional)

  • Notes (optional)

Length should be pre-populated by the maps API, but modifiable by the user.

Type: {“Earthen” (default), “Gravel”, “Paved”}

For our Spring 2021 release, the following points will be supported:

Point type

Attributes

Other notes

Water valve

  • Name: String (optional)

  • Source: Enum (optional)

  • Flow rate: Decimal (optional)

  • Flow rate unit: Enum (optional)

  • Notes (optional)

Source: {“Surface water” (default), “Groundwater”, “Rainwater”}

Flow rate unit is based on the users measurement preference. For metric: l/min (default), l/hour

For imperial: g/min (default), g/hour

Gate

  • Name: String (optional)

  • Notes (optional)

Transitioning from legacy fields to areas, lines, and points

For Winter 2021 and all previous versions of LiteFarm, fields were an entity that lived just below a farm. Moving forward, we’ll have three categories of of geospatial entities that live below a farm:

  • Areas

  • Lines

  • Points

For this transition, fields will become an area of type Field. The endpoint that populated fields and displayed them on google maps will need to be augmented to display all categories of geospatial entities.

  • No labels