...
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, domicilesresidences, barns, greenhouses, etc.
Lines are drawn, multi-point segments that don’t form a closed polygon. In general, lines don’t have a meaningful area an area (such as with fences) or their area is relatively uniform and doesn’t impact their utilitybased on the direction of the line (such as with creeks or buffer areas). Examples of lines are: fences, creeks, roads, and footpaths
Structures Points on the other hand are points 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 pumps water valves and gates
For our Spring 2021 release, the following areas will be supported:
...
For our Spring 2021 release, the following structures points will be supported:
Structure Point type | Attributes | Other notes |
---|---|---|
Water valve |
| 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 |
|
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.