Skip to main content

How to Import Guidance Lines into FieldBee using GeoJSON

This document explains how to properly format a GeoJSON file to import Guidance Lines (AB Lines) into the FieldBee application. Follow these specifications and examples to ensure your navigation lines import correctly.

1. General File Structure

Your GeoJSON file must be structured as a FeatureCollection containing one or more features of type LineString.

  • Coordinate System: WGS 84 (EPSG:4326).

  • File Extension: .geojson 

2. Geometry Specifications

Each line must be represented as a LineString:

  • Straight AB Lines: Must contain exactly 2 coordinate pairs (Start Point A and End Point B).

JSON


"geometry": {
  "type": "LineString",
  "coordinates": [
    [Longitude_A, Latitude_A],
    [Longitude_B, Latitude_B]
  ]
}

3. Valid GeoJSON Example

JSON

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "LineString",
        "coordinates": [
          [-3.714038, 37.009733],
          [-3.713807, 37.007695]
        ]
      },
      "properties": {
        "fid": 1,
        "Name": "20260922_LONGITUDINAL"
      }
    }
  ]
}

Common Checklist & Errors to Avoid

Test Your File First: Use geojson.io to quickly test and inspect your GeoJSON file before importing it. Import your GeoJSON   — if your guidance lines draw in the correct field location on the map without errors, your file is valid!

  1. Line Name Required: Ensure the "Name" field is present and set to a text string. Do NOT set "Name": null, as FieldBee requires a valid string to identify the line in the app.

  2. Do Not Swap Coordinates: Ensure Longitude comes first and Latitude second ([Longitude, Latitude]). If swapped, your guidance lines will appear in Antarctica or the wrong hemisphere.

  3. Use LineString Only: Do NOT use MultiLineString or Polygon.

  4. Check Trailing Commas: Ensure JSON syntax is valid without trailing commas after the last attribute or array item.


Back to top