Traditional farm maps serve many purposes on the farm, from getting the team synced up at the morning meeting, to communicating information to new workers, to providing needed documentation for certifiers. They are a central part of managing a farm.
By moving farm maps from paper or the dry erase board into a digital format, we add even more utility for our users. Users will be able to do the following in their digital farm maps:
...
Navigate around their farm by dragging on the map
...
View existing areas and structures
...
Add new areas and structures
...
Filter what displays on their map
...
Farm maps in LiteFarm allow users to add three types of drawings to their farm maps: areas, lines, and structures.
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, domiciles, barns, greenhouses, etc.
Lines are drawn, multi-point segments that don’t form a polygon. In general, lines don’t have a meaningful area or their area is relatively uniform and doesn’t impact their utility. Examples of lines are: fences, creeks, roads, and footpaths
Structures on the other hand are points 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 pumps and gates
For our Spring 2021 release, the following areas will be supported:
Area type | Attributes | Other notes |
|---|---|---|
Farm boundary |
| Can only be 1 per farm |
Field |
| 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. |
Natural area |
| Total area and perimeter should be pre-populated by the maps API, but modifiable by the user. |
Greenhouse |
| 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. |
Water source |
| Total area and perimeter should be pre-populated by the maps API, but modifiable by the user. |
Domicile |
| Total area and perimeter should be pre-populated by the maps API, but modifiable by the user. |
Ceremonial area |
| 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 |
| Length should be pre-populated by the maps API, but modifiable by the user. |
Creek |
| Length should be pre-populated by the maps API, but modifiable by the user. |
Road |
| Length should be pre-populated by the maps API, but modifiable by the user. Type: {“Earthen” (default), “Gravel”, “Paved”} |
Footpath |
| 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 structures will be supported:
Structure type | Attributes | Other notes |
|---|---|---|
Pump |
| 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 |
|