Skip to main content

Import fields via geoJSON in Farmable (Web Portal)

Learn how to import field boundaries into Farmable’s Web Portal using a geoJSON file, edit mandatory details, and finalize your map.

Written by Enja Matthee

TL;DR

  • Only geoJSON files are supported for import right now.

  • Convert other formats (SHP, KML) to geoJSON using an online converter.

Web Portal → Fields import → upload file → edit mandatory details (Field name, Crop category, Variety, Plant date) → review & finish.

What files can I import?

Currently, Farmable supports geoJSON for field imports. If your data is in another format (e.g., Shapefile, KML), convert it to geoJSON first using any trusted online converter or desktop GIS too for example MyGeodata Converter.

Step-by-step: import your fields (Web Portal)

  1. Go to Fields import
    Open the Farmable Web Portal and navigate to Fields import.

  2. Upload your geoJSON
    Click Upload, select your .geojson file, and wait for the fields to appear on the map.

  3. Edit mandatory details
    Click each field on the map and add:

    • Field name

    • Crop category

    • Variety

    • Plant date

  4. Review & finish
    Confirm boundaries and details → click Finish to complete the import.

Tip: Keep naming consistent (e.g., “North Block 03”) to make searching and reporting easier later.

FAQs

Can I import SHP or KML directly?
Not yet. Convert to geoJSON first, then upload.

My geoJSON uploaded but some fields are missing—why?
Check that the file contains valid polygons for all fields and isn’t filtered by properties. Multi-polygons should be supported; if needed, split large datasets.

Do I have to fill in every detail now?
You must add the mandatory details during import. You can refine other details later in Fields.

Can I edit boundaries after importing?
Yes. Open a field and adjust the boundary points, then save.

What if my file uses different attribute names?
No problem—Farmable asks you to fill in the required details per field after upload, so mismatched column names won’t block you.

Did this answer your question?